is Program Files (x86) installation bad for steam to be installed in?

[craigsters]

C:\Program Files (x86) <I moved steam from this directory to > C:\Program Files\Steam

I read that older games don't run good in the Program Files (x86) folder and that you should install steam in Program Files area instead, something about over secure or sensitivity of it handling 32bit games or programs and administration issues , something not processed or handled properly in Program Files (x86) in Windows 10 and later

I'm out of my elements here and I'm novice with understanding this stuff sorry, my head hurts from talking geek now or trying too

Craig goes back to corner to bang rocks together

[Azza ☠]

"Program Files (x86)" is for 32-bit programs, while "Program Files" is meant for 64-bit programs.

There's very little security risk running 32-bit apps/games, but 64-bit can be slightly more secure. You would already have to be targeted by a hacker or exploit.

Under Windows Security > Device Security > Core Isolation > Memory Integrity

Having that turned on randomizes your app/game memory usage (location of data under the RAM). This is more of a limited range for 32-bit than 64-bit. It prevents malicious code being injected into it or data sniffing at certain memory locations.

This is more important for the Operating System protection, which should be running as 64-bit.

Unless you have a very important app, I wouldn't worry about it being 32-bit.

MAC get a complete 64-bit version of Steam. However, Windows users use to just be 32-bit only, but now on 64-bit operating systems (since an update around 2018) now get a 64-bit steamwebhelper.exe process. The steamwebhelper.exe process is Steam's built-in web browser, also used to display the Steam store, and forum, etc. The steamerrorreporter64.exe is also 64-bit, used if a crash occurs to report the issue back.

[The Troll King]

"Dont be a ♥♥♥♥♥", that's the best advice any computer person can give you.

[Crashed]

It's normal for it to be installed in that path by default because the Steam Client Bootstrapper is a 32-bit application.

This happens because Steam Setup asks for the Program Files folder for 32-bit applications.

[Hammer Of Evil]

its called (x86) because of the intel '86' processor series, like the 8086, that processor line was re-designed into a 32bit processor from 16 bits, and the name just stuck.

it doesn't mean its '86 bits' - its a folder structure that's intended for 32 bit applications to use, since microsoft thought a lot of people would be dragging their feet moving to 64bit structures

so - (x86) - 32 bits
- (x64) - 64 bits

you can use this knowledge when you download programs or utilities on your pc, now you know. many still offer 32bit options for ppl still using 32bit processors.

32 bit programs are best installed to the x86 folder to prevent 32bit components from possible interaction with 64 bit programs. its a nice way to keep things seperated but functional.

if you do have problems though, you can install 64 bit games to a different folder, just create a steamlibrary in a different location

the main differences between 32bits and 64bits is generally the amount of data sets + memory each program can be allocated. it seems simple to say that, but that's actually a monumental difference in the world of bits and bytes.

hope it helped.

[wadmodder1999]

Valve has always delayed the release of the x64-exclusive update for the Steam client for decades now. With this decade where Windows 11 dumped 32-bit processors and the end-of-life of Windows 10 in 2025 for non-LTSC users, and 2032 for the remaining users, perhaps Valve could finally be able to announce the 64-bit exclusive update this decade, whenever they feel like that 32-bit Windows is dead for Steam users.

[Stingray_tm]

I would not worry, where Steam installs its client as long as you have your Steam client from Valve with the official installer. Usually there is no need to change any default install options for most software.

[Crashed]

Originally posted by wadmodder1999:

Valve has always delayed the release of the x64-exclusive update for the Steam client for decades now. With this decade where Windows 11 dumped 32-bit processors and the end-of-life of Windows 10 in 2025 for non-LTSC users, and 2032 for the remaining users, perhaps Valve could finally be able to announce the 64-bit exclusive update this decade, whenever they feel like that 32-bit Windows is dead for Steam users.

Still unlikely because even the latest Canary build still has WOW64.

[wadmodder1999]

Well unless Google Chrome or Chromium, which is a component of Steam required for it to run properly, drops support for 32-bit Windows users.