Install 32 Bit Software on 64 Bit Windows

Most modern Windows PCs run a 64-bit version of the operating system, but plenty of older or specialized programs are still 32-bit. This guide walks you through the standard ways to install and run 32-bit software on 64-bit Windows, including automatic compatibility, manual workarounds, and what to do when an installer simply refuses to cooperate.

What You’ll Need

A 64-bit version of Windows 10 or Windows 11 (check in Settings > System > About under “System type”).
The 32-bit installer file (usually a .exe or .msi) downloaded from a trusted source.
Administrator access to the PC (you’ll need to approve User Account Control prompts).
Optional: a separate folder for manual installation, and a tool like 7-Zip if the installer is an archive.

Step-by-Step

Confirm your Windows version is 64-bit. Open Settings > System > About and look at “System type.” It should say “64-bit operating system, x64-based processor.” If it says 32-bit, this guide doesn’t apply—you’re already on 32-bit.
Run the installer normally. Double-click the .exe or .msi file. Windows 64-bit includes WoW64 (Windows-on-Windows 64-bit), a compatibility layer that lets 32-bit programs run without any extra steps. Most installers will just work.
If you get a “wrong architecture” error, try compatibility mode. Right-click the installer file, select Properties, go to the Compatibility tab, and check “Run this program in compatibility mode for:” then choose an older Windows version like Windows 7 or Windows XP SP3. Click Apply and run it again.
If the installer is a ZIP or MSI archive, extract it manually. Right-click the file and choose Extract All (or use 7-Zip). Look for a folder named something like “Win32” or “x86.” Inside, you’ll often find a portable .exe that runs directly without installation.
Manually copy the program files. If extraction reveals a folder with the program’s .exe and DLL files, copy that whole folder to C:\Program Files (x86)\ (the standard location for 32-bit apps). Right-click the main .exe and select Send to > Desktop (create shortcut) for easy access.
Install missing 32-bit runtime libraries. Some programs need older Visual C++ Redistributables or .NET Framework versions. Download the 32-bit (x86) versions from Microsoft’s official site and install them. The program’s documentation or error message usually tells you which one is missing.
Use the “Program Files (x86)” folder for new installs. When an installer asks for a destination folder, it should default to C:\Program Files (x86)\. If it doesn’t, change it to that path manually—it keeps 32-bit and 64-bit apps separate and avoids permission issues.
If the installer is a 16-bit setup (very old), use a virtual machine. Windows 64-bit cannot run 16-bit installers directly. Install a free VM like VirtualBox, create a Windows 32-bit guest (or even DOS), and run the installer there. This is the only reliable way for truly ancient software.

Common Mistakes

Downloading the wrong version. Some programs offer both “64-bit” and “32-bit” downloads. Make sure you actually have the 32-bit one—if you grabbed the 64-bit by accident, you’re not testing the 32-bit path.
Ignoring the “x86” label. In the tech world, “x86” means 32-bit, and “x64” means 64-bit. If a download page says “x86,” that’s the 32-bit version you want.
Forcing a 64-bit installer to run on 32-bit. That’s the reverse problem—this guide is for 32-bit software on 64-bit Windows, not the other way around.
Skipping the compatibility tab. Many users try to run an old installer, get an error, and give up. The compatibility mode often fixes it in seconds.
Installing to “Program Files” instead of “Program Files (x86).” Windows treats the two folders differently. 32-bit apps belong in the (x86) folder; putting them elsewhere can cause permission errors.

Tips

Check the program’s website first. Many developers still offer 32-bit versions alongside 64-bit ones. Downloading the official 32-bit installer is always the cleanest route.
Use “Run as administrator” for the installer. Right-click the installer and choose Run as administrator to avoid UAC-related permission failures, especially if the program writes to its own folder.
Keep the 32-bit program in its own folder. If you manually copy files, don’t scatter them across your drive. Keep everything in one folder so uninstalling later is just deleting that folder (plus removing any registry entries if present).
Look for a portable version. Some programs offer “portable” editions that don’t need installation at all—just unzip and run. These are ideal for 32-bit apps on 64-bit Windows.
Use the Windows “Programs and Features” panel to uninstall. If the installer did run, it should appear there. Don’t just delete the folder—that leaves registry entries behind.

Troubleshooting

“This app can’t run on your PC” error. This usually means the file is 64-bit and your system is 32-bit, or the file is corrupted. Re-download the 32-bit version and try again. If it still fails, check the file size—a very small file might be a download error.
Installer starts but crashes mid-way. Common cause: missing Visual C++ Redistributables. Install the 32-bit (x86) versions of VC++ 2015-2022, 2013, 2012, and 2010 from Microsoft’s site. Also make sure your Windows is fully updated.
Program installs but won’t launch. Right-click the program’s shortcut, go to Properties > Compatibility, and try “Run this program as an administrator” or “Run in compatibility mode for Windows 7.” Also check if the program needs a specific 32-bit DLL that’s missing—use a tool like Dependency Walker to see what’s missing (though it’s not updated for newer Windows).
Error about missing .NET Framework. Many 32-bit apps rely on .NET. Download the .NET Framework 3.5 (includes 2.0 and 3.0) from Windows Features (Control Panel > Programs > Turn Windows features on or off). Also install .NET 4.8 if needed.
The installer says “not a valid Win32 application.” This often means the file is actually 64-bit or the download is corrupt. Re-check the download source and try a different browser. If the file is a 16-bit installer, you’ll need a virtual machine as described in Step 8.
Program works but is slow. 32-bit apps run under WoW64, which adds a small overhead. That’s normal. If it’s extremely slow, close other programs and check if the app has a 64-bit version you could switch to.

Frequently Asked Questions

Can 64-bit Windows run 32-bit programs at all?

Yes. Windows 64-bit includes WoW64, a built-in compatibility layer that translates 32-bit system calls to 64-bit. Most 32-bit programs run without any special steps.

Where do 32-bit programs get installed?

By default, 32-bit installers use C:\Program Files (x86)\. That’s the standard location. If an installer lets you choose, use that folder to keep things organized.

Why does my 32-bit installer say “wrong architecture”?

That error usually means the installer itself is 64-bit, not 32-bit. Double-check the file you downloaded—look for “x86” or “32-bit” in the filename. If it’s genuinely 32-bit, try compatibility mode.

Can I install a 32-bit driver on 64-bit Windows?

No. Drivers are low-level and must match the OS architecture. A 32-bit driver will not work on 64-bit Windows. You need a 64-bit driver from the hardware maker.

Is it safe to manually copy a 32-bit program from another PC?

It can work if the program doesn’t rely on registry entries or system services. Many portable apps work this way. But if the program needs to register DLLs or write to the registry, manual copying won’t be enough—you’ll need to run the installer.

Will 32-bit software run faster on 64-bit Windows?

No. The 32-bit code runs under emulation, which adds a small overhead. Performance is usually similar to running on 32-bit Windows, but not faster. If speed matters, look for a 64-bit version of the program.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →