Skip to main content

System architecture

System architecture describes the platform a package is built for. Understand why processor type and OS version must both match before installation.

topic 2 min readLast reviewed:
Processor platform

Branch 1

OS build

Supported release

Branch 2

Package

Must support both and device

Example: x64 or Arm64

Concept diagram: System architecture: Processor platform (Example: x64 or Arm64) → OS build (Supported release) → Package (Must support both and device).. Simplified; not a screenshot.

What does system architecture mean?

System architecture is the processor and operating-system platform a software component is designed to run on. On Windows devices, x64 and Arm64 are examples of architecture labels. A driver package's architecture must be supported by the installed system; the same product name can have separate packages for different platforms.

Architecture is not the only requirement. OS release, driver model, device identifier, and manufacturer support can matter too. Some ordinary applications can run through compatibility features, but that does not mean a low-level driver built for another architecture can be installed. Check the package's published system requirements rather than inferring support from an application's behavior.

Example in context

A user finds two similarly named printer downloads, one for x64 Windows and one for Arm64 Windows. The computer's OS architecture, not the printer's marketing name, determines which platform-specific package could be installed. The exact printer model and Windows release still need checking after the architecture matches.

A common misunderstanding

Architecture does not simply mean 'new computer versus old computer,' and a 64-bit OS label alone does not distinguish x64 from Arm64. Likewise, a ZIP archive containing several folders is not automatically compatible with all of them. Installation might fail or offer only partial functions if the wrong component is selected.

How to use this term

Check architecture on the machine where the package will run, not on the web page or another computer used to download it. This matters especially when preparing offline recovery for a network adapter: a package built for the wrong platform will not be a useful fallback. Architecture support is necessary but not sufficient; also verify the device revision and the installed Windows release from the official listing. If the maker provides different downloads for Arm64 and x64, keep their labels clearly distinct when saving packages.

See [operating system](/glossary/operating-system) and [compatibility](/glossary/compatibility). The [system and architecture guide](/driver-compatibility-and-recovery/match-operating-system-and-architecture) gives the practical comparison; [choosing a package](/how-to-update-device-drivers/choose-a-compatible-driver-package) covers device support too.