If you’ve ever opened File Explorer on a 64-bit Windows PC and spotted both Program Files and Program Files (x86) sitting side by side, you’re not looking at a glitch or leftover junk. Windows put them both there intentionally. The short answer: one folder holds 64-bit apps, the other holds 32-bit apps, and keeping them separate is what stops them from breaking each other.
The 32-bit vs. 64-bit Difference, Quickly Explained
The core difference between 32-bit and 64-bit Windows comes down to how much memory the operating system can track and use. A 32-bit OS can address a maximum of 4 GB of RAM, and that ceiling is baked into the architecture. A 64-bit OS blows past that: Windows 11 Home supports up to 128 GB of RAM, and Windows 11 Pro supports up to 2 TB, with the theoretical ceiling astronomically higher still.
But the jump from 32-bit to 64-bit isn’t just about RAM. It’s a fundamentally different way of processing data. That’s why a 32-bit application can’t simply drop into a 64-bit environment without some help, as the instruction sets, memory pointers, and system calls all work differently. Hardware drivers need to be rebuilt entirely for 64-bit, which is why you’ll sometimes find that an old peripheral stops working after a Windows upgrade.
To confirm which version of Windows you’re running, press Windows + R, type msinfo32, and press Enter. Look for System Type, it’ll say either x64-based PC or ARM64-based PC on a 64-bit system.
Alternatively: Settings > System > About > Device specifications > System type.
Why Two Program Files Folders Exist
When 64-bit Windows needs to run a 32-bit application, it uses a compatibility layer called WoW64, short for Windows 32-bit on Windows 64-bit. WoW64 intercepts the 32-bit app’s calls to the operating system and translates them so they work correctly in a 64-bit environment.
Part of that translation involves file system redirection. When a 32-bit app tries to install itself into C:\Program Files, WoW64 silently redirects it to C:\Program Files (x86) instead. The app never knows the difference. It thinks it’s installing to the standard location, but Windows keeps it separated from the 64-bit apps.
Here’s why that separation matters: 64-bit and 32-bit apps use different DLL files (the shared code libraries that programs rely on). If both types of apps dumped their DLLs into the same folder, you’d get constant version conflicts, with a 32-bit DLL overwriting a 64-bit one, or vice versa, breaking whichever app installed last. Two folders eliminates that entire class of problem.
In summary:
- C:\Program Files, 64-bit applications only
- C:\Program Files (x86), 32-bit applications, redirected here automatically by WoW64
The x86 in the folder name refers to the x86 processor architecture, the lineage of 32-bit chips that runs from the Intel 386 and 486 through the Pentium series. It’s a legacy label that stuck.
How to Tell Whether an App Is 32-bit or 64-bit
The quickest method is Task Manager. Press Ctrl + Shift + Esc, click the Details tab, right-click any column header, choose Select columns, and add Platform. You’ll see each running process labeled as either 32-bit or 64-bit.
You can also check which folder an app installed into, anything under C:\Program Files (x86) is a 32-bit app. That’s the fastest visual audit.
Where Things Stand in 2026
The dual-folder architecture hasn’t changed since 64-bit Windows arrived with Windows XP Professional x64 Edition (and carried forward through Vista and every release since), and it’s still present in Windows 11 24H2. But the landscape around it has shifted considerably since 2010.
| App Type | Where It Installs | Architecture |
|---|---|---|
| Traditional Win32 (64-bit) | C:\Program Files | 64-bit |
| Traditional Win32 (32-bit) | C:\Program Files (x86) | 32-bit via WoW64 |
| Microsoft Store / MSIX apps | %LocalAppData%\Packages | 64-bit or ARM64 native |
| PWAs (web apps) | Browser sandbox | N/A |
Many built-in Windows apps — Photos, Calculator, the Xbox app, and other Microsoft Store/MSIX-packaged apps — bypass Program Files entirely and install to %LocalAppData%\Packages. (Microsoft Edge and Microsoft 365 are notable exceptions: both still install to Program Files (x86) by default, not as MSIX packages.) That means the Program Files folders are gradually becoming less central to day-to-day app management for a growing slice of software, even as the underlying architecture stays the same.
On ARM-based PCs (like those running Snapdragon X Elite chips), the picture is slightly different. These machines use a translation layer called Prism instead of WoW64 to run x86 32-bit apps, but the folder structure behaves identically. Native ARM64 apps install to C:\Program Files just like native x86-64 (64-bit) apps do.
As for how many 32-bit apps are left: the Steam Hardware Survey confirms over 95% of Windows gaming systems now run 64-bit Windows, though it doesn’t track app-level architecture. Anecdotally, most actively maintained desktop software has moved to 64-bit, but plenty of older, unmaintained utilities and internal business tools remain 32-bit. The transition is nearly complete, but “nearly” still means plenty of legacy apps in active use.
Common Questions
| Question | Answer |
|---|---|
| Is having two Program Files folders a sign of malware? | No, it’s standard on every 64-bit Windows install. If you’re concerned, run sfc /scannow in an elevated Command Prompt to check for corrupted system files. |
| Can I delete Program Files (x86) to save space? | No. Deleting it will break every 32-bit app installed on your system. Uninstall apps you don’t need through Settings > Apps > Installed apps instead. |
| Why did a 64-bit app install into Program Files (x86)? | That’s usually an installer bug, where the developer compiled a 64-bit binary but didn’t update their installer script. The app will typically still work, but you can reinstall it to get it into the right folder. |
| I’m on an ARM PC and don’t see Program Files (x86), is that normal? | It may not appear until you install your first 32-bit app. Once you do, Windows creates it automatically. |
The Bottom Line
The two Program Files folders are Windows’ practical solution to a real compatibility problem. Keeping 32-bit and 64-bit apps separated prevents DLL conflicts that would otherwise break software silently and unpredictably. The system has worked reliably since 64-bit Windows arrived and continues to work the same way in Windows 11 24H2. With 32-bit apps now a shrinking minority and Store/MSIX apps bypassing Program Files altogether, the Program Files (x86) folder will likely become less and less populated over the next few years, but it’s not going anywhere soon, and you shouldn’t touch it manually. If you’re running Microsoft 365 and want to ensure you’re getting the best performance, consider whether you should install the 64-bit version of Office via Office 365.