# Windows 7 switching from 64 to 32 bit mode **URL:** \ **Category:** Factual Questions\ **Created:** [October 13, 2010, 3:23pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007 "2010-10-13T15:23:31Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Eutychus](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@Eutychus](https://boards.straightdope.com/u/Eutychus)\ **Post date:** [October 13, 2010, 3:23pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/1 "2010-10-13T15:23:31Z")
Quick question … I’m installing a 64 bit version of Windows 7 Professional. I will need to used the 32 bit version at times. Does switching from 64 to 32 bit (XP Mode) versions require a reboot or does it do it on the fly? ---
**Author:** ![Silophant](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Silophant](https://boards.straightdope.com/u/Silophant)\ **Post date:** [October 13, 2010, 3:25pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/2 "2010-10-13T15:25:51Z")
There’s no separate 32-bit mode in Windows 7. It’s just that 32-bit programs run as normal. If you’re talking about XP mode, like you seem to be, it’s a virtual machine, so it runs in a window, on the fly. ---
**Author:** ![Kinthalis](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/kinthalis/32/16084_2.png) [@Kinthalis](https://boards.straightdope.com/u/Kinthalis)\ **Post date:** [October 13, 2010, 3:27pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/3 "2010-10-13T15:27:35Z")
Unless I’m misunderstanding something they are two separate OS’s. You’ll need to dual boot them. Why do you need to run 32 bit windows? Legacy 16 bit code? ---
**Author:** ![Electronic\_Chaos](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Electronic\_Chaos](https://boards.straightdope.com/u/Electronic_Chaos)\ **Post date:** [October 13, 2010, 3:34pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/4 "2010-10-13T15:34:43Z")
> [@Kinthalis](#): > > Unless I’m misunderstanding something they are two separate OS’s. You’ll need to dual boot them. Why do you need to run 32 bit windows? Legacy 16 bit code? Nope. They are two separate OS’s, but you run XP mode through Windows Virtual PC. You’ll need Windows 7 Professional, Ultimate or Enterprise to access Windows XP mode, though. And yes, legacy 16 bit applications are about the only reason you need to run XP mode. ETA: [Link](http://www.microsoft.com/windows/virtual-pc/download.aspx) to download everything you need for XP mode. ---
**Author:** ![Eutychus](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@Eutychus](https://boards.straightdope.com/u/Eutychus)\ **Post date:** [October 13, 2010, 3:37pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/5 "2010-10-13T15:37:55Z")
> [@Electronic\_Chaos](#): > > Nope. They are two separate OS’s, but you run XP mode through Windows Virtual PC. You’ll need Windows 7 Professional, Ultimate or Enterprise to access Windows XP mode, though. And yes, legacy 16 bit applications are about the only reason you need to run XP mode. Actually Microsoft themselves are the problem. They haven’t really caught up and some of their own apps only run in 32 bit mode. ---
**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\ **Post date:** [October 13, 2010, 5:09pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/6 "2010-10-13T17:09:42Z")
> [@Electronic\_Chaos](#): > > Nope. They are two separate OS’s, but you run XP mode through Windows Virtual PC. You’ll need Windows 7 Professional, Ultimate or Enterprise to access Windows XP mode, though. And yes, legacy 16 bit applications are about the only reason you need to run XP mode. Drivers are another reason. I have an older but not ancient (5 years) printer/fax/scanner, and Canon refuses to release a 64-bit driver for it. So I’m stuck running XP Mode when I want to use it. ---
**Author:** ![AmunRa](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@AmunRa](https://boards.straightdope.com/u/AmunRa)\ **Post date:** [October 13, 2010, 6:23pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/7 "2010-10-13T18:23:47Z")
Are you sure you need to use XP Mode? Most 32 bit applications run just fine under Windows 7 64 bit (without XP Mode). The only blanket exception, that applies to most users, is drivers; due to the fact that all drivers must be signed by Microsoft in order to be used in a 64 bit version of Windows. ---
**Author:** ![ChrisBooth12](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@ChrisBooth12](https://boards.straightdope.com/u/ChrisBooth12)\ **Post date:** [October 13, 2010, 8:00pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/8 "2010-10-13T20:00:41Z")
You can run any 32bit app on a 64bit system just not the other way around, that is why you have to Program Files folder one for 64bit programs and one for 32 bit programs, I have a 64bit machine and have never once had to use Windows XP mode other then to give myself free dropbox referrels ---
**Author:** ![jz78817](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jz78817/32/1028_2.png) [@jz78817](https://boards.straightdope.com/u/jz78817)\ **Post date:** [October 13, 2010, 11:28pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/9 "2010-10-13T23:28:36Z")
> [@Eutychus](#): > > Actually Microsoft themselves are the problem. They haven’t really caught up and some of their own apps only run in 32 bit mode. such as? ---
**Author:** ![mittu](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@mittu](https://boards.straightdope.com/u/mittu)\ **Post date:** [October 14, 2010, 12:32am UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/10 "2010-10-14T00:32:34Z")
> [@Eutychus](#): > > Actually Microsoft themselves are the problem. They haven’t really caught up and some of their own apps only run in 32 bit mode. I second the call for an example here. I have never found a 32bit application bit that doesn’t work in 64bit Windows either from installing into the x86 Program Files folder or using compatibility mode. As has been stated the only issue seems to be with drivers for old hardware and that is the fault of the hardware manufacturer, not Microsoft. ---
**Author:** ![jz78817](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jz78817/32/1028_2.png) [@jz78817](https://boards.straightdope.com/u/jz78817)\ **Post date:** [October 14, 2010, 12:37am UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/11 "2010-10-14T00:37:54Z")
> [@mittu](#): > > > [@Eutychus](#): > > > > Actually Microsoft themselves are the problem. They haven’t really caught up and some of their own apps only run in 32 bit mode. > > I second the call for an example here. > > I have never found a 32bit application bit that doesn’t work in 64bit Windows either from installing into the x86 Program Files folder or using compatibility mode. As has been stated the only issue seems to be with drivers for old hardware and that is the fault of the hardware manufacturer, not Microsoft. the only issues I’ve ever heard of are either: 1. applications which install a kernel-mode component or driver (anti-virus/anti-malware programs, as an example) 2. 32-bit programs that are packaged with a 16-bit version of the installer (don’t laugh, they exist.) ---
**Author:** ![AmunRa](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@AmunRa](https://boards.straightdope.com/u/AmunRa)\ **Post date:** [October 14, 2010, 5:16am UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/12 "2010-10-14T05:16:12Z")
> [@mittu](#): > > > [@Eutychus](#): > > > > Actually Microsoft themselves are the problem. They haven’t really caught up and some of their own apps only run in 32 bit mode. > > I second the call for an example here. > > I have never found a 32bit application bit that doesn’t work in 64bit Windows either from installing into the x86 Program Files folder or using compatibility mode. As has been stated the only issue seems to be with drivers for old hardware and that is the fault of the hardware manufacturer, not Microsoft. I too am genuinely curious as to whether there is a legitimate example for this. It also be noted that driver issues are in a way Microsoft’s fault, since if they didn’t require the drivers to be signed (by Microsoft for a hefty fee) many of them would work just fine. The requirement for signed drivers was introduced with Vista x64. As far as I know it still applies only to the 64 bit version of Windows 7. ---
**Author:** ![mittu](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@mittu](https://boards.straightdope.com/u/mittu)\ **Post date:** [October 14, 2010, 5:29am UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/13 "2010-10-14T05:29:51Z")
A fair point but you can’t really blame Microsoft for trying to make the system as a whole more stable and secure. It is down to the manufacturers to submit their drivers for approval which only costs $250 per driver, or, as the Wiki article on WHQL testing states: > [@](#): > > A company can choose to sign their own drivers rather than go through the WHQL testing process. These drivers would not qualify for the “Certified for Windows” logos, but they would install on 64 bit versions of Windows and install without a warning message on 32 bit versions of Windows Vista or Windows 7 So the manufacturers could do it, it is just a question of how much work they are prepared to do to support legacy hardware on a new OS. In the case of printers this seems to be ‘not very bothered at all’ since most people replace their printers when the ink runs out. ---
**Author:** ![jz78817](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jz78817/32/1028_2.png) [@jz78817](https://boards.straightdope.com/u/jz78817)\ **Post date:** [October 14, 2010, 5:38am UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/14 "2010-10-14T05:38:28Z")
> [@](#): > > It also be noted that driver issues are in a way Microsoft’s fault, since if they didn’t require the drivers to be signed (by Microsoft for a hefty fee) many of them would work just fine. The requirement for signed drivers was introduced with Vista x64. As far as I know it still applies only to the 64 bit version of Windows 7. damned if they do, damned if they don’t. If a hardware manufacturer can’t stump up the “hefty fee” of $500, then it’s probably a good thing that I can’t install their driver. Oh and BTW, Microsoft doesn’t sign drivers, the vendor does after paying that $500 to Verisign for a certificate. ---
**Author:** ![sevenwood](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sevenwood](https://boards.straightdope.com/u/sevenwood)\ **Post date:** [October 14, 2010, 12:55pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/15 "2010-10-14T12:55:37Z")
> [@mittu](#): > > I have never found a 32bit application bit that doesn’t work in 64bit Windows… Unfortunately, I have two such programs (both of which, fortunately, run just fine under Windows 7’s XP mode). I suspect it’s because both programs meddle with the innards of the underlying OS much more than they should. - Microsoft’s own 32-bit Visual Studio 6.x (the last version before Microsoft switched to its “.net” technology, and I’ve got waaayyy too many old VB programs that would be a nightmare to convert). Microsoft hasn’t supported version 6.x for many years now. - Compaq’s 32-bit Visual FORTRAN compiler (which uses Microsoft’s Visual Studio 6.x as an underlying interface). Same problem: I support many huge, old programs which rely on idiosyncratic interfaces of that old compiler, which is no longer sold, updated, or supported. ---
**Author:** ![astro](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@astro](https://boards.straightdope.com/u/astro)\ **Post date:** [October 14, 2010, 1:13pm UTC](https://boards.straightdope.com/t/windows-7-switching-from-64-to-32-bit-mode/557007/16 "2010-10-14T13:13:06Z")
[From MIcrosoft](http://windows.microsoft.com/en-US/windows7/32-bit-and-64-bit-Windows-frequently-asked-questions) > [@](#): > > Can I run 32-bit programs on a 64-bit computer? > > Most programs designed for the 32-bit version of Windows will work on the 64-bit version of Windows. Notable exceptions are many antivirus programs. > > Device drivers designed for the 32-bit version of Windows don’t work on computers running a 64-bit version of Windows. If you’re trying to install a printer or other device that only has 32-bit drivers available, it won’t work correctly on a 64-bit version of Windows. To learn how to check for drivers, see Update a driver for hardware that isn’t working properly or go to the device manufacturer’s website. You can also get information about drivers by going to the Windows 7 Upgrade Advisor webpage. The Win 7 Professional package comes with both the 32 and 64 bit install options. You can either live with a 32 bit install, as the performance difference probably will be fairly negligible in real world use, or you can [install both 32 and 64 bit installs](http://social.answers.microsoft.com/Forums/en-US/w7install/thread/e5099d54-3d67-48c3-a77e-8a3ca1b2c994)and dual boot. You cannot switch on the fly.