Check whether Windows is 32-bit or 64-bit, understand x64-based processor results, and choose the correct FSX add-ons and drivers.
To check whether Windows is 32-bit or 64-bit, press Windows + I, open System > About, and read System type under Device specifications. Use the operating-system value—not merely “x64-based processor”—when choosing drivers. Microsoft Flight Simulator X (FSX) and FSX: Steam Edition are 32-bit applications even on 64-bit Windows.
How do I know if I have Win32 or Win64?
Use the Windows System type field rather than an application name, folder or processor label.
Windows 10 and Windows 11
Windows 10 and Windows 11 display the installed operating-system architecture in Settings.
- Open Settings. Press
Windows + I, or search the Start menu forAbout your PC. - Open the About page. Select System, then About.
- Read System type. Find it under Device specifications. It will identify Windows as a 32-bit or 64-bit operating system and then identify the processor type.
Windows 11 has no 32-bit edition. If a Windows 11 PC appears to be labelled 32-bit, you are probably looking at the architecture of FSX or another application rather than Windows itself.
The terms Win32 and Win64 can also describe software targets or Windows programming interfaces. Seeing “Win32” in an installer, file name or Task Manager does not prove that the operating system is 32-bit.
A second built-in 64-bit checker
PowerShell can report the operating-system architecture independently of the Settings page. Open PowerShell and run:
(Get-CimInstance Win32_OperatingSystem).OSArchitecture
The result will be 64-bit or 32-bit. Administrator permission is not required.
Windows 7 and Windows 8
Control Panel provides the same definitive answer on older Windows versions.
- Open Control Panel.
- Select System. Depending on the view, this may be under System and Security.
- Read System type. It states whether the installed operating system is 32-bit or 64-bit.
What does “32-bit operating system, x64-based processor” mean?
The words before the comma identify the installed copy of Windows; the words after it identify the processor family or capability.
| System type shown | What it means | What to use |
|---|---|---|
| 64-bit operating system, x64-based processor | Both Windows and the Intel or AMD processor use the x64 architecture. | x64 Windows drivers; x86 or Win32 modules loaded directly by FSX. |
| 32-bit operating system, x64-based processor | The processor supports 64-bit computing, but the installed Windows edition is 32-bit. | 32-bit Windows drivers and utilities; x86 FSX modules. |
| 32-bit operating system, x86-based processor | Windows and the processor are both 32-bit. | 32-bit drivers, applications and FSX modules. |
| 64-bit operating system, ARM-based processor | Windows is 64-bit ARM, not x64. | ARM-compatible device drivers; verify FSX, add-on and peripheral compatibility separately. |
The mistake we see most often is reading only x64-based processor and downloading a 64-bit driver even though the same line says 32-bit operating system. Drivers must match the installed operating system, not merely what the processor could run.
A 32-bit installation cannot be changed to 64-bit with a switch in Settings. Moving to 64-bit Windows requires a clean Windows installation, so back up personal files and confirm that suitable device drivers are available first.
Can the FSX installation folder tell me whether Windows is 32-bit or 64-bit?
The FSX installation folder is only a clue, not the definitive architecture check.
On 64-bit x64 Windows, a default FSX installation commonly appears under Program Files (x86) because FSX is a 32-bit application. On 32-bit Windows it normally appears under Program Files. Custom folders and Steam libraries can be placed elsewhere, so use System type for the final answer; our guide to finding the actual FSX installation folder covers the boxed and Steam locations.
Folder names can also be counter-intuitive. On x64 Windows, System32 contains the native 64-bit system components, while SysWOW64 supports 32-bit components. Do not copy FSX files into either folder merely to solve an architecture error.
Likewise, Task Manager may mark fsx.exe as a 32-bit process. That identifies FSX, not Windows.
Does 64-bit Windows make FSX 64-bit?
No. Boxed Microsoft Flight Simulator X and FSX: Steam Edition remain 32-bit programs on 64-bit Windows, and there is no setting that converts them to 64-bit.
A 64-bit operating system can give Windows, drivers and background applications access to more memory, leaving a better overall environment for the simulator. It does not remove FSX’s own 32-bit process limit; our explanation of FSX memory use and the 4 GB boundary on 64-bit Windows covers the practical consequences.
Should FSX add-ons and drivers be 32-bit or 64-bit?
Match each component to the software that loads it: Windows-level drivers follow Windows architecture, while code loaded inside FSX must be compatible with FSX’s 32-bit process.
- Joystick, throttle and graphics drivers: use x64 drivers on x64 Windows and 32-bit drivers on 32-bit Windows. The processor line alone is not enough.
- Compiled gauges and DLL modules: choose the x86 or Win32 build when it loads directly inside FSX. A 64-bit DLL cannot load into the 32-bit
fsx.exeprocess. - Aircraft, scenery and sound files: ordinary content files do not usually have a Windows architecture. Follow the simulator-version requirement rather than looking for a 32-bit or 64-bit edition.
- Texture files: “32-bit texture” refers to image colour and alpha data, not the architecture of Windows or FSX. Our comparison of DXT3 and 32-bit simulator textures explains that separate choice.
- Standalone companion applications: a 32-bit utility will normally run on x64 Windows as a separate process. A 64-bit utility cannot run on 32-bit Windows.
- Old installers: a 32-bit installer is normal on 64-bit Windows, but a much older 16-bit setup launcher will not run there. Use an updated installer or documented manual-installation method rather than changing system folders.
- Installers that report FSX is missing: the installer may be looking in the wrong 32-bit registry view or for the wrong boxed or Steam entry. Follow our FSX registry detection and repair procedure instead of copying an unverified registry path.