Read on Twitter
Please RT
Q: I have important traditional 32-bit server apps running on Windows Server 2008 32-bit. I would like to move this app to a modern version like Windows Server 2016/2019. Is it possible to run 32-bit apps on Windows Server 64-bit editions?
Q: I have important traditional 32-bit server apps running on Windows Server 2008 32-bit. I would like to move this app to a modern version like Windows Server 2016/2019. Is it possible to run 32-bit apps on Windows Server 64-bit editions?
If so, do I need to worry about app compatibility?
Answers: Yes. Let's discuss.
Let's start with application compatibility with Windows client as a proof point.
Answers: Yes. Let's discuss.
Let's start with application compatibility with Windows client as a proof point.
For over 10 years, Microsoft has been shipping 64-bit Windows client & most people don’t even realize it. Most 32-bit applications just work! That’s how seamless application compatibility is with Windows.
Windows 64-bit provides terabytes of addressable memory support, better performance, scale, security and so much more. It's all goodness.
In terms of application compatibility:
1. 32-bit Windows/Windows Server can run 32-bit applications. 32-bit apps can access 2 GB memory.
2. 64-bit Windows/Windows Server can run 64-bit or 32-bit applications. 64-bit apps can access terabytes of memory.
1. 32-bit Windows/Windows Server can run 32-bit applications. 32-bit apps can access 2 GB memory.
2. 64-bit Windows/Windows Server can run 64-bit or 32-bit applications. 64-bit apps can access terabytes of memory.
Q: Does this mean Windows 64-bit editions can run ANY 32-bit app?
A: Not 100%. The crux of the issue is drivers.
32-bit Windows requires 32-bit drivers
64-bit Windows requires 64-bit drivers
You cannot mix & match 32-bit drivers w/64-bit operating systems & vice versa.
A: Not 100%. The crux of the issue is drivers.
32-bit Windows requires 32-bit drivers
64-bit Windows requires 64-bit drivers
You cannot mix & match 32-bit drivers w/64-bit operating systems & vice versa.
Again, Microsoft has been shipping 64-bit Windows client for 10+ years & most people don’t realize it.
The notable compat exceptions were really old printers, scanners & hardware devices that had 32-bit only drivers & the manufacturers didn’t produce 64-bit drivers (~2007).
The notable compat exceptions were really old printers, scanners & hardware devices that had 32-bit only drivers & the manufacturers didn’t produce 64-bit drivers (~2007).
Q: Is there a way to know for sure if my 32-bit Windows Server app will work with 64-bit Windows Server?
A: The best way is to test it, but here’s a good question to start with: “Does this 32-bit Windows Server app communicate with a specific piece of hardware?”
A: The best way is to test it, but here’s a good question to start with: “Does this 32-bit Windows Server app communicate with a specific piece of hardware?”
1.If the app communicates w/hardware, then it likely has a 32-bit driver which won’t work with 64-bit Windows Server. You need 64-bit drivers to run on 64-bit Windows.
2.If the app doesn’t communicate w/hardware, then it likely doesn’t have a driver dependency & has a higher likelihood of running on 64-bit Windows.
I hope this helps.
I hope this helps.
