7 ms·
Why Does Microsoft Still Offer a 32-bit OS?
- ocdtrekkie 9y ago"This is how bad it is -> When Microsoft released Windows Vista in 2007 it was 64-bit and also ran all 32-bit programs flawlessly. So at that time I was baffled why Microsoft ALSO released Windows Vista in 32-bit only mode – a version that refused to run any 64-bit binaries." For what it's worth, at that time, a lot of computers were still being sold with 32-bit only processors or an inadequate amount of RAM to handle 64-bit Windows. I can't count how many machines I saw sold with Vista and 1 GB of RAM. This actually became the subject of a class action lawsuit: https://www.slashgear.com/acer-offers-to-settle-vista-class-action-suit-with-flash-drive-apology-26279471/ https://www.slashgear.com/acer-offers-to-settle-vista-class-... It also makes sense supporting those users upgrading their computer to the newer, more secure OSes. So I can see why Microsoft wants to continue to make 32-bit builds people can upgrade to for a number of years. I suppose the only real mystifying question is when doing a fresh install of Windows, it would allow you to ever select 32-bit. If the installer detects adequate system resources for 64-bit, that's what it should install.
- Grazester 9y agoYeah. Its called having options and you don't get much of that with Apple. I remember when Apple stopped supporting the Core 2 DUO machines because the EFI was 32bit(not even the processor). I was not pleased
- Jtsummers 9y agoWasn't that only the first generation of hardware they made with Intel's processors? IIRC, my friend and I both got laptops about 3 months apart and mine had support longer than his, I don't know if this was the issue or not.
- pkamb 9y agoThe first Intel Macbook Pro in Early 2006 was Core Duo (32-bit), then in October they reved them with Core 2 Duo (64-bit w/ 32-bit EFI). I remember specifically because I had to wait out the first couple months of my freshman year of college without a laptop, waiting for that 64-bit support that was supposed to drop at any time...
- Jtsummers 9y agoRight. I guess I replaced mine from that revision before it became an issue.
- tssva 9y agoYou lose at least one thing with 64 bit Windows versus 32 bit, support for legacy 16 bit applications or components. When Windows Vista, 7 and 8 were released there were still many in use which alone justified Microsoft releasing 32 bit OS versions. I still see them in use today but at a much much lower rate than 5 years ago when Windows 8 was released.
- shawnz 9y agoI don't think it would have been so hard for them to develop an emulation layer to run 16-bit programs on 64-bit if they were really concerned about having that functionality. It's not like performance issues are going to be a concern in a 16-bit application. So that might be a reason people still use 32-bit Windows, but it surely isn't the reason that Microsoft keeps building for 32-bit.
- MaulingMonkey 9y agoThrowing DOSBox at the problem is easy. Supporting the horrible legacy abominations combining 16-bit windows 3.1 targeting programs running side-by-side and interacting with 32-bit programs is a whole new can of worms. Maintaining an existing works-just-fine 32-bit build is way easier than writing, testing, QAing, and fielding support requests when the emulator layer breaks some poor bastard's existing workflow.
- acchow 9y agoWould it work in a 32-bit VM?
- 0x0 9y agoMaybe but then you need to maintain a whole separate windows installation with separate printer and scanner drivers and network logins and so on. Plus your files are hidden away inside a vm disk image. If all you need is some light internet/mail access and your legacy applications, while still being able to use your peripherals, 32bit windows fits the bill perfectly as long as 64bit windows refuses to implement 16bit compatibility.
- PhasmaFelis 9y agoBecause some users still have 32-bit computers. How is this not obvious? He's talking like there are people with 64-bit PCs running 32-bit Windows out of cluelessness or spite.
- bluedino 9y agoThere are entire companies with deployments of 32-bit Windows 7 installs.
- srett 9y agoWhich 32bit cpu would anyone want to use Windows 10 on? That has to be a real pain. > He's talking like there are people with 64-bit PCs running 32-bit Windows out of cluelessness or spite. Cause this is what's going on, he's stating that explicitly.
- geofft 9y ago> Because some users still have 32-bit computers. How is this not obvious? It is completely not obvious that there are Windows 10 users with 32-bit computers. Here's an analysis from Debian trying to figure out whether to default to the 64-bit image: https://lists.debian.org/debian-devel/2017/06/msg00059.html https://lists.debian.org/debian-devel/2017/06/msg00059.html No one installs i386 new -- machines that are non-amd64-capable are: * mainstream machines from 2004 and earlier * a brief wave of mobile devices, now thankfully gone * deeply embedded, usually incapable of running [the standard Debian installer] From the followup comments, there were apparently a few netbooks using the mobile chipsets as late as 2012, but I doubt a netbook from 2012 using a mobile chipset is going to be well-supported by Windows 10, regardless of CPU architecture.
- lebrad 9y agoWhen my sister started grad school at Harvard she bought a brand new 64-bit Dell laptop from the school store that came preinstalled with 32-bit Windows. I was amazed. I wiped the computer and installed a 64-bit OS, but there are definitely people out there selling 64-bit PCs running 32-bit Windows out of cluelessness.
- 9y ago
- jaclaz 9y agoI may read it the wrong way, but basically it says "since all (98.4%) our customers have more than 2 Gb of RAM, then Microsoft should only make 64 bit OS". So, how many of Microsoft's customers are also customers of Backblaze? Like 0.1%? As a side note, the even point for the need to go 64 bit (bigger OS, bigger executables, more memory used, etc.) is not in my experience at the 4 Gb of RAM level, but rather at the 6 Gb.
- TimeToFly 9y agoI think you actually did. They are not saying - "Hey, we are having only a few 32bit customers, Microsoft should dump them". The problem is much more complex.
- jaclaz 9y agoNo, they are saying, more or less "Hey, having to support a tiny fraction of our users that are on 32 bit causes us a whole lot of problems, so, since we don't have the guts to tell these customers to switch to 64 bit, we are telling Microsoft what they should do in order to totally remove the inferior OS architecture."
- marcosdumay 9y ago> So, how many of Microsoft's customers are also customers of Backblaze? Looking at Backblaze logs, 100%.
- ComputerGuru 9y agoI imagine an upgrade path from 32-bit to 64-bit installations would take care of a huge chunk of the population MS keeps the 32-bit editions around for (enterprise 32-bit installations on 64-bit-capable hardware). There's no technical reason this cannot be offered, as the Windows installer already replaces all system directories, detects incompatible hardware, disables drivers that aren't supported, and everything else that would be technically required.
- ryanburk 9y ago> There's no technical reason this cannot be offered this actually isn't true. and I say this as the person who pushed for a 32->64bit upgrade path at microsoft in longhorn. at the most basic level - it is easy for the core OS. but any apps you've installed are going to be a crapshoot to see if they work, with their installers only expecting a 32bit OS, registry, etc. upgrade is hard enough as it is so risking the experience to a customer of breaking many of their apps with no good path to resolution isn't worth it versus waiting ~3-5 years for a PC purchase cycle and their next preinstalled version of windows being 64bit and going from there.
- ComputerGuru 9y agoLike I said, no technical reason. Just a user experience one.
- shawnz 9y agoThis is a terrible article. > The main gigantic upside of a 64-bit process is the ability to support more than 2 GBytes of RAM ... Since only 1.6% of Backblaze customers have 2 GBytes or less of RAM, the other 98.4% desperately need 64-bit support, period, end of story. This would only be true if all those Backblaze customers were only running one process on their machines. With PAE, A 32-bit system can support more than 2 GB, just not a 32-bit process. And actually, there are workarounds available to enable even that. > And remember, there is no downside. There is a downside. 64-bit systems consume more RAM since every pointer and word is double the size. This could mean a performance penalty due to more swapping too. > Because there is zero downside, the first time it could, Apple shipped with 64-bit OS support. No, Apple did this because they are in control of the hardware their OS runs on, so they can ensure that everyone is supported. Microsoft don't have that luxury. Even then, Apple was still building for 32-bit just 5 years ago. They also weren't first to support it as the author seems to imply -- 64-bit Windows XP was available before OSX even ran on Intel CPUs. > There are a variety of security features such as ASLR (Address Space Layout Randomization) that work best in 64-bits. The 32-bit version is inherently less secure. Yeah, in the sense that it's easier to guess a 32-bit long number than a 64-bit long number. It's still unfathomable. > Supporting both versions is complicated. The more data our customers have, the more momentarily RAM intensive some functions (like inheriting backup state) can be. The more data you have the bigger the problem. Backblaze customers who accidentally chose to disable 64-bit operations are then going to have problems. Has Backblaze honestly ever had this problem, where 2GB of RAM was not enough to reliably find a customer's backup state? That seems ridiculous to me.
- likelynew 9y ago> No, Apple did this because they are in control of the hardware their OS runs on, so they can ensure that everyone is supported. Microsoft don't have that luxury. I don't think Windows 10 supports any of the 32 bit only processors. AFAIK, all Intel and AMD processors in last 10 years has 64 bit support. Update: Another user(geofft) mentioned debian analysis which confirms my point(albeit it says, none in last 13 years): https://news.ycombinator.com/item?id=14524215 https://news.ycombinator.com/item?id=14524215 Update 2: Looks like I am wrong. See comments below it.
- TazeTSchnitzel 9y agoLots of new computers are sold with 32-bit Windows on them. I think this is primarily devices with lower memory, because 32-bit Windows uses less RAM and less disk space. I own a Windows 10 tablet with 1GiB RAM, for example.
- kogepathic 9y ago> I own a Windows 10 tablet with 1GiB RAM, for example. I own a Dell Venue 8 (3845) and the reason it's running Windows 10 32-bit instead of 64-bit is because Intel inexplicably decided to ship 32-bit UEFI on Bay Trail instead of 64-bit UEFI. As far as I know, all Bay Trail devices are running a 32-bit copy of Windows because of this. For Linux this isn't a problem, you can have grub x86 load an x86_64 kernel, but Windows doesn't have something similar. So 32-bit bootloader forces you to have a 32-bit OS. So, thank Intel. I'm sure Microsoft and OEMs would have put x64 Windows on it if they could have.
- problems 9y ago> As far as I know, all Bay Trail devices are running a 32-bit copy of Windows because of this. Can you not just boot it in BIOS mode? Should be possible for the OS to escalate from there.
- dom0 9y agoAt least some of these devices don't have that option.
- kogepathic 9y agoCorrect. There is no way to "legacy" boot on the tablet. So it's 32-bit UEFI or a brick.
- likelynew 9y agoI am so much shocked by the comments here giving reasons that they provide 32 bit operating systems, ranging from ability to run 16 bit softwares, to the speed. I mean, it's not a bad thing to debate, but I seriously did not expected it here.
- overgard 9y agoIt usually doesn't matter, but there are two possible downsides of 64bit: - Every pointer becomes twice as big (8 bytes vs 4 bytes). - Potentially less data fits in the CPU cache lines, because the data is bigger. One thing I wonder if the 32 bit edition mostly exists for small VM's?
- johnvega 9y agoThe upcoming battery friendly ARM based windows PC will support x86 emulation 32-bit apps in near native speed. Not sure if it will support x64 now or in the future and perhaps someone can comment if this is a technical limitation or an economical or both. https://news.ycombinator.com/item?id=14518290 https://news.ycombinator.com/item?id=14518290
- xorblurb 9y agoI think they don't support x64, and probably they never will, or at least not before a very long time. It's possible MS can leverage part of its existing WoW code with x86 on ARM64. They would have more work to do with x64 on ARM64. Plus the CPU might need special support to help things, for example I'm curious about how to efficiently emulate the stronger memory model of x86 on an ARM, and if the CPU provides help, it might be using low level tricks, reusing some bits here and there, to do the magic. Just some wild hypotheses though.
- MisterKent 9y agoMost of the comments addressed the issues with the article. It mostly boils down to, Microsoft will support legacy for as long as possible (such as 16 bit apps), some performance advantages of 32 bit OSes. And that one reader who correctly stated that some are still on 32 bit CPU architectures. But really, is nobody concerned that the author of TFA was the CTO of Backblaze and that somehow nobody stopped this awful article from being published?
- 0x0 9y agoThis quote: > Moving over to a 64-bit OS allows your laptop to run BOTH the old compatible 32-bit processes and also the new 64-bit processes. In other words, there is zero downside (and there are gigantic upsides) is fairly clueless. I know of several enterprises that actually still depend on the 16bit NTVDM MS-DOS emulation for some legacy systems. Only 32bit windows 10 can keep running those; 64bit windows 10 removed that feature. So there is definitively not "zero downside". Edit: This quote: > I can't imagine having any problem hiring somebody to rewrite the original functionality but in a modern 64 bit Python program. Probably take somebody a weekend for most apps? is so laughable I won't even comment further.
- Joeri 9y agoBut why do they offer 32 bit windows to consumers? I get why you'd keep some embedded skew for just this dos emulation legacy case, but why are 4% of backblaze customers running a 32 bit windows? Microsoft shouldn't be offering that as a choice.
- problems 9y agoWhat if those customers want to run legacy 16 bit apps in NTVDM? I have a few games I like that I occasionally fire up a 32 bit VM for just for this reason. If you're using 16-bit Point of Sale software for example you might just decide to stick with 32-bit Windows as the VM wouldn't be worth it and would add more complexity for users.
- braveo 9y agoI'm curious, why this approach instead of something like DOSBOX?
- MaulingMonkey 9y agoThe question is why add a VM layer (and suffer the loss of direct hardware access for drivers / dongles / having all your programs in the same context / user confusion / other drawbacks) just so you can run a 64-bit host? This doesn't always have an answer. Even if you do use DOSBOX, you still need to run a guest OS - will that be DOS, unpatched and unsupported Windows XP, or something relatively modern (if still 32-bit) that might let you stem the tide - instead of decaying further into your legacy hellhole?
- wilhil 9y agoI remember back in Windows Vista days (and early Windows 7 builds) doing extensive 32-bit Vs 64-bit testing and the 32 bit system outperformed the 64-bit in everything from startup time to application launch time. This being said, PAE doesn't seem to work great and out of a lab, when you start running multiple applications, you will usually want 4GB memory on the smallest system and typically 8GB, so, I think 64-bit is worth the sacrifice! (No idea if still true, haven't done tests like this in many years)
- deleted 9y ago[deleted]
- m-j-fox 9y agoQuestion: why did Firefox ask if it was allowed to "take and record video" on this page?!?
- tempestn 9y agoBut, but when you upgrade to 64-bit you DO lose access to 16-bit programs! (I seriously did go into slight withdrawal when I couldn't play BOWEP Tetris anymore. No other Tetris will ever be the same...)
- ChiliDogSwirl 9y agoThe way Microsoft implemented 32-bit support in Windows 64 broke a lot of the legacy applications I help maintain (from an admin/support standpoint, not development standpoint) at work. Years after switching to 64-bit Windows, we still uncover subtle bugs that need to be patched in our configuration or by the vendor (if they still exist). If these applications were more mission-critical, we'd definitely want to stick with 32-bit Windows.