Monday, December 22nd 2025

by AleksandarK Monday, 01:34

In a December 19 Steam client update, Valve has finally ended support for the 32-bit Steam application on Windows 11 and Windows 10 operating systems. According to the official release notes, updates for the 32-bit Steam client will continue to be provided for systems with 32-bit Windows versions until January 1, 2026. This marks the end of one of the last official 32-bit applications that actively supported the 32-bit versions of Windows. As the software industry continues to phase out 32-bit support, this decision is a natural progression, encouraging consumers to transition to 64-bit operating systems and compatible software.

Valve has been planning this change for some time to simplify software maintenance. However, only a very small number of users will be affected by this decision, as almost no one is still using the outdated 32-bit operating system. Those still on a 32-bit OS will need to upgrade their hardware or reinstall 64-bit OS versions, if their hardware permits, to continue using the official Steam Client. For those planning to stick with 32-bit builds, there is still hope. Enthusiasts frequently create unofficial backports of modern clients. For example, an earlier version of the Steam Client was unofficially backported to Windows 7 SP1 x64 and Windows 8.x x64.

Related News

This marks the end of one of the last official 32-bit applications that actively supported the 32-bit versions of Windows 11 and Windows 10.Windows 11 never shipped in a 32-bit version ;)

News Editor

ncrsWindows 11 never shipped in a 32-bit version ;)Good point. Fixed. Thanks!

2006 I installed a 64 bit gnu gentoo linux on a AMD Turion MT-32. I really wonder how many 32 bit boxes are out there in active use with steam. Basically 20 years 64 bit capeable processors most likely and a few stick to outdated old 32 bit world. Last 32 bit application which annoyed me was skype - I hardly used steam.

No modern software should be supporting 32-bit by now; everyone should have dropped it at least 10 years ago. I’ve been on only 64-bit since Vista, so around 19 years. I’m surprised Steam supported it for this long.

Raiden85No modern software should be supporting 32-bit by now; everyone should have dropped it at least 10 years ago. I’ve been on only 64-bit since Vista, so around 19 years. I’m surprised Steam supported it for this long.It was mostly the fault of MS dragging their feet at the behest of some big business clients. Originally, 8 was supposed to be 64-bit only. That fell through. Then the same was true with 10. That also fell through. They finally bit the bullet with 11. And now when the only consumer Windows with mainstream support is 11, Valve can also finally depreciate the 32-bit client.

Does it automatically upgrade my client when the update was installed or do I have to reinstall the client? According to task manager steamservices(dot)exe is still 32-bit

SqutzyDoes it automatically upgrade my client when the update was installed or do I have to reinstall the client? According to task manager steamservices(dot)exe is still 32-bitNo, that’s correct, while the client application is fully transitioned to 64-bit (it was mostly already there), the steamservice is still 32-bit for now. It’s not actually part of the client, it’s essentially a dirty hack by Valve for elevated privilege to install runtimes and some other assorted things without asking for admin elevation every time.

Raiden85No modern software should be supporting 32-bit by now; everyone should have dropped it at least 10 years ago. I’ve been on only 64-bit since Vista, so around 19 years. I’m surprised Steam supported it for this long.Actually there is reason even for win10 era devices to use 32bit windows. Memory overhead is a factor, if you had 2 or 4gb of ram on budget devices back in the day, it made a difference.

Especially back when most applications did not run in 64bit mode anyway. Of course this only played a part in updating older devices to windows 10 and maybe early windows 10 devices.

On another note:
Linux client meanwhile stays 32Bit and is pretty much the only 32bit application people still use.

Unfortunately the Steam Client Service is still 32bit for some reason.

qlumActually there is reason even for win10 era devices to use 32bit windows. Memory overhead is a factor, if you had 2 or 4gb of ram on budget devices back in the day, it made a difference.

Especially back when most applications did not run in 64bit mode anyway. Of course this only played a part in updating older devices to windows 10 and maybe early windows 10 devices.

On another note:
Linux client meanwhile stays 32Bit and is pretty much the only 32bit application people still use.no, the reason is to use 16bit exes, windows on x86_64 mode cannot run them (but can run all x86_32 ones just fine)

TomorrowUnfortunately the Steam Client Service is still 32bit for some reason.

Super Dainty Moderator

TomorrowUnfortunately the Steam Client Service is still 32bit for some reason.

OnasiThere is zero reason for it to be switched to 64-bit. It’s just a “Run as” function. It doesn’t need access to more memory space. Again, the name is a bit misleading, it’s not actually a part of the main CEF client application.Solaris17Could be for some time. This is just a service, it doesn’t interface with people, process purchases or otherwise hold data. Other then cleaning up there tech stack for ease of maintenance this doesn’t need to be 64bit for any performance reason.If that's the case then converting it to native 64bit should be extremely easy, right?
Much easier than making the main client 64bit.

Windows and other programs also have 64bit services. Even if it offers no performance benefit, even these dont need access more memory, even if it's not a user facing service.

Super Dainty Moderator

TomorrowIf that's the case then converting it to native 64bit should be extremely easy, right?It’s a system service not a pretty gui. Less code maybe, but more stringent testing, then MS blessing which takes time.

Selayano, the reason is to use 16bit exes, windows on x86_64 mode cannot run them (but can run all x86_32 ones just fine)It is definitely a reason, too but generally was not relevant for home users, not much in any case. If it was just for that, they may have limited 32 bit for pro / enterprise.
The system requirements also list a minimum of 1GB for 32 bit and 2gb for 64bit so microsoft acnowledges the memory difference too, it really does make a difference when you are low on ram.

Solaris17It’s a system service not a pretty gui. Less code maybe, but more stringent testing, then MS blessing which takes time.I have over a hundred services running with no GUI. They are all 64bit. That's a pretty weak argument.
Truth is there's no good solid argument why a developer should maintain 32bit service when their main program is already 64bit.

Anyone arguing otherwise should get with the times. 32bit is history. The only reason - the very reason this transition hasn't happened before is because of WoW64. I swear it's black magic. Possibly the the best and most invisible emulation layer ever created.

Ok. Im not a developer, but personally i try to use one system or a program for the same thing.
Yes maybe some other system or a program may be more efficient or better suited for some specific task, but for maintenance it's bad.

For example i recently converted a bunch of my older RAR2, RAR3 and RAR4 self extracting archives to the newest RAR5 standard.
Sure, i could have left some of them on the older version for some minor benefits in compression, but i figured that since im devoting my time for this conversion anyway then i might as well go all the way. Besides these archives are small and i use store, not compress.
Also WinRAR dropped support for creating RAR4 archives and earlier this year dropped 32bit support too.

I can only assume Valve will eventually convert both their Windows service (no impact) and the Linux client (high impact) to 64bit too and we can stop arguing about something so trivial.

Super Dainty Moderator

TomorrowThat's a pretty weak argument.I’m not arguing. I don’t care what you think. I’m guessing valve doesn’t either.

OnasiNo, that’s correct, while the client application is fully transitioned to 64-bit (it was mostly already there), the steamservice is still 32-bit for now. It’s not actually part of the client, it’s essentially a dirty hack by Valve for elevated privilege to install runtimes and some other assorted things without asking for admin elevation every time.So just to be sure. I do NOT have to reinstall the client for it to be updated to 64-bit version? :)

Resident Wat-man

Pretty sure I've had 64-bit support on all my hardware for the last 20 years. No reason for us to be stuck in the dark ages. At some point, we need to move on.

SqutzySo just to be sure. I do NOT have to reinstall the client for it to be updated to 64-bit version? :)No, that just comes with the CEF update of the client. Essentially, just like when Chrome went 64-bit only, most of actual modules and binaries are already there, the update just enabled them and (presumably) switched the executable. You don’t have to do anything.

SqutzySo just to be sure. I do NOT have to reinstall the client for it to be updated to 64-bit version? :)You don't have to do anything on your end.

It's all automatic.

However if you want, you can reinstall the client.

It's your choice.

Selayano, the reason is to use 16bit exes, windows on x86_64 mode cannot run them (but can run all x86_32 ones just fine)Sounds like a job for a VM. I mean friggin OS/2 can run Win16 apps, they ain't that tough.

imean yeah duh, but we all know how retarded enterprises can be, how obstinate they can be and how they love obsolete legacy tools

@Selaya
Yup, that’s pretty much the reason why it took MS longer than reasonably needed to fully depreciate 32-bit versions of Windows. Each time they tried they were faced with whining from enterprise customers about how they still have some niche dogshit software that just NEEDS a 32-bit OS. I would assume that by 2021 and 11 they either finally moved on, or MS realized how ridiculous it was that they were the only major OS that still offered a 32-bit version and just decided to go ”fuck it, not worth the hassle”.

Is it possible that some services remain at 32bit because many old games are still 32bit? Steam has been around a long time, so legacy gaming might be at play here. As you may recall, Apple dumped 32bit app support back at the launch of Catalina. This basically made Steam gaming on macOS a futile effort, because most of the games that you could play on a Mac weren’t 64bit either.