With over 120 million monthly active users as of 2019, Steam is by far the most popular digital distribution platform for PC gaming. It provides access to over 30,000 games, social features like chat and groups, achievements, workshops and much more.
Ever since its launch back in 2003 however, Steam has defaulted to installing games and applications in the Program Files (x86) directory. This persists even today, in an era where 64-bit computing is standard.
In this comprehensive guide, we‘ll dive deep into the reasons behind this default Steam behavior. We‘ll cover:
- A brief history of 32-bit x86 computing
- Program Files vs. Program Files (x86) folders
- Why Steam remains a 32-bit program
- Downsides of installing Steam games to Program Files
- How to install Steam to another location
- Fixing common errors like "Untrusted system file"
- SSD vs. HDD – which is better for Steam?
- And much more…
Let‘s get started!
A Brief History of 32-bit x86 Computing
To understand why Steam uses the x86 directory, we first need to understand a little history behind 32-bit x86 computing.
The origins of x86 date back to 1978 with Intel‘s iconic 8086 16-bit microprocessor. This evolutionary CPU architecture eventually reached 32 bits with the release of the 80386 (commonly called the 386) in 1985.
The 386 was a revolutionary processor for its time, introducing features like:
- Full 32-bit internal architecture
- Integrated MMU for virtual memory support
- Multitasking capabilities
- 32-bit instruction set and registers
The 386 laid the foundation for modern protected mode OS like Windows. It also introduced the 32-bit instruction set and programming model referred to today as "x86."
Later in 2003, AMD released the first x86 processor with 64-bit extensions – the Athlon 64. Intel followed shortly after with its own 64-bit enabled Pentium 4 chips.
However, all x86 processors retained backwards compatibility with 32-bit x86 software. This ensured compatibility across generations – a key factor in the architecture‘s longevity.
Program Files vs Program Files (x86)
Windows XP SP1 was the first Windows version to support 64-bit computing. To maintain compatibility with 32-bit programs, it introduced separate Program Files folders:
C:\Program Files– for native 64-bit programsC:\Program Files (x86)– for 32-bit programs
This separation remains today. The (x86) folder provides compatibility for running older 32-bit software on 64-bit Windows.
According to Microsoft:
"The Windows-on-Windows (WoW) layer seamlessly handles 32-bit applications and processes regardless of whether the operating system beneath is 32-bit or 64-bit."
So in essence, Program Files (x86) contains files for the WoW64 subsystem – a emulator that allows 32-bit and 64-bit code to execute side-by-side.
Why Does Steam Use the x86 Folder?
With the stage set, now we can explain why Steam installs to the Program Files (x86) folder.
Despite gaming‘s transition to 64-bit, the Steam client itself remains a 32-bit program for compatibility purposes.
As a result, it installs to the x86 directory by default, even on 64-bit Windows.
According to Steam‘s documentation:
"All Steam applications are installed in Program Files (x86) due to Steam being 32-bit…"
But why hasn‘t Steam also moved to 64-bit? There are likely a few reasons driving this decision:
1. Avoid Compatibility Regressions
Migrating the client to 64-bit risks breaking compatibility with 32-bit only systems. Based on the Steam Hardware survey, roughly 25% of users still run 32-bit Windows. Changing architectures could block them from Steam.
2. Stability Concerns
The existing 32-bit client is stable and time-tested. As the saying goes "if it ain‘t broke, don‘t fix it." Porting millions of lines of code to an entirely new architecture is asking for trouble.
3. Performance Differences Minimal
While 64-bit has advantages, for general desktop usage and gaming x86 vs. x64 performance differences are small. For Steam itself, there is likely little incentive to undertake a rewrite.
By retaining backwards compatibility, Steam ensures the broadest possible userbase can access its services and content.
Issues With Installing Games to Program Files
The 32-bit Steam client generally functions fine installed inside Program Files (x86). However, installing games here is not recommended. Some downsides include:
Permissions Issues
The Program Files folder has limited permissions. Installing games here can prevent mods or community patches from working correctly.
For example, a common error is Error writing to file when a game tries to modify files it does not have write access to.
Data Loss
Placing game files inside Program Files risks losing access if Windows needs to be re-installed or reset. Generally, only the Windows partition is wiped – losing any installed games.
Slower Load Times
Program Files resides on the primary system drive, which tends to be slower than secondary HDDs or SSDs. Games load faster when installed to a separate Steam library folder on a different drive.
For these reasons, most advise installing Steam games to a location outside of Program Files – like D:\SteamLibrary.
Moving the Steam Installation
If you wish to move Steam out of Program Files (x86), it‘s a simple process:
- Exit Steam completely
- Browse to
C:\Program Files (x86)\Steam - Copy the entire Steam folder to the desired location like
D:\Games\Steam - Delete the original
C:\Program Files (x86)\Steamfolder - Create a shortcut to
D:\Games\Steam\Steam.exe - Launch Steam! It will automatically use the new install location
Here‘s a visual guide:
Fig 1. Copying the Steam installation folder
For new Steam setups, during installation you can select "Choose location for Steam installation" to pick a custom folder.
Always install games to secondary drives – not the Windows system drive!
Fixing "Untrusted System File" Errors
When launching Steam from a new location, you may see this error:
Failed to load steamui.dll.Untrusted system file (C:\Program Files (x86)\Steam\steamui.dll).This occurs because Windows treats files in Program Files as "system" files. When you move them, Windows sees them as untrusted.
To fix, simply revert ownership of steamui.dll using these steps:
- Right-click
steamui.dlland select Properties - Go to the Security tab
- Click Advanced
- Change the Owner back to your user account
- Apply changes
This makes you the owner again so Windows trusts the file.
SSD vs HDD – Which is Better for Steam?
When installing Steam, an important decision is whether to use an SSD (solid state drive) or traditional HDD (hard disk drive) for storage. Let‘s compare the pros and cons:
| SSD | HDD | |
|---|---|---|
| Speed | Much faster read/write speeds | Slower than SSD |
| Capacity | Lower capacities (500GB – 2TB typical) | Higher capacities available (up to ~10TB) |
| Price | More expensive per GB | Cheaper per GB |
| Lifespan | Limited write endurance | No write restrictions |
Generally, it is recommended to install the Steam client and frequently played games to an SSD. This provides faster launch times and load times.
For your library of unplayed or older games, use a high capacity HDD for cheap bulk storage. Steam makes it easy to set multiple install folders across different drives.
Specific benefits of gaming on an SSD include:
-
Faster Level Loading: Levels and maps load much quicker – sometimes 50%+ faster. No more long waiting!
-
Reduced Texture Pop-In: Higher streaming speeds mean textures load as intended, instead of popping in late.
-
Snappier Game Launches: Games start quicker with an SSD. Boot times can be 2-3x faster.
-
Speedier Installs/Updates: New games download and update faster. Patches are applied quicker as well.
So in summary, use SSDs for your active Steam library and HDDs for cold storage of unplayed games. This balances performance and capacity.
Closing Thoughts
Although Steam defaults to installing to the antiquated Program Files (x86) directory, this entry hopefully shed light on the reasons behind that behavior. We covered topics ranging from x86 history to SSD vs. HDD comparisons.
While the 32-bit client causes some downsides, Valve likely retains compatibility to avoid massively disrupting its 120+ million userbase. Migrating platforms is never easy!
For best results, install Steam and active games to SSD storage outside of Program Files. And utilize high capacity HDDs for your inactive game library. This sidesteps issues while delivering great performance where it matters most.
Did you learn something useful today? Let us know if you have any other tips or questions around optimizing your Steam installation and gaming performance! We‘re always happy to chat more about PC gaming.
