Upgrade XP 32bit to Win7 64 bit?

[ChadVader]

Ok, so I’m pretty sure I read you can’t upgrade from XP 32 bit to Win7 64 bit. Your existing copy of XP has to already be 64 bit.

However, I also read a while ago that you can transfer xp 32 bit to xp 64 bit by paying $10 and Microsoft will send you a 64 bit DVD.

I’ve been searching the Microsoft website and only found a link for Vista 32 to Vista 64. Can you go from Xp 32 to Xp 64? If so, does anyone have a link, because I can’t find it.

Thanks.

 

[rflcptr]

No, the keys are different. What you read was in regards to Vista, alone.

 

[ambientZ]

xp32 -> 7 64. You should be able to use the upgrade disk, but it won't actually do the upgrade, it moves your existing files to a backup directory and does a clean install (custom install).

 

[Catweazle]

I’m pretty sure I read you can’t upgrade from XP 32 bit to Win7 64 bit.

Please don't misunderstand the situation. If you are an XP 32-bit user you can still purchase a Windows Vista or Windows 7 Upgrade pack, upgrade your license, and use the 64-bit installation.

The lack of a 'valid upgrade path' only stops you from performing an over the top 'upgrade install'. The move from 32-bit to 64-bit is not a 'valid upgrade path, so when upgrading the ;license a custom clean install will need to be performed, all programs reinstalled, and all backed up user data restored afterwards.

 

[ChadVader]

Ok thanks, that makes sense.

 

[bigdogchris]

Ok, so I’m pretty sure I read you can’t upgrade from XP 32 bit to Win7 64 bit. Your existing copy of XP has to already be 64 bit.

This is not correct. You can upgrade to 7 64 since both Vista and 7 use the same keys for both 32 and 64 bit.

However, I also read a while ago that you can transfer xp 32 bit to xp 64 bit by paying $10 and Microsoft will send you a 64 bit DVD.

You don't need to do this ... and I think that deal was only for Vista.

I’ve been searching the Microsoft website and only found a link for Vista 32 to Vista 64. Can you go from Xp 32 to Xp 64? If so, does anyone have a link, because I can’t find it.

Not needed.

Buy Windows 7 x64 Upgrade and be done. Back up your files. Drop the disc in, run it and it will install files, reboot, install your OS and move your XP install to windows.old. Just delete it.

 

[Catweazle]

No worries. I find it quite disgusting that Microsoft continually fails to clarify the situation in its promotional materials. One can only assume that they are intentionally preying upon people unfamiliar with the procedures necessary, in order to generate more 'full install' higher priced retail sales!


Here's the relevent KB article from Microsoft, in relation to the move from Windows XP 32-bit to Vista 64-bit, using a Retail Upgrade pack:

http://support.microsoft.com/kb/932795

The scenario will be the same for the move to Windows 7.

 

[Arainach]

One can only assume that they are intentionally preying upon people unfamiliar with the procedures necessary, in order to generate more 'full install' higher priced retail sales!

Or that 95% of users would have no idea what the hell they were talking about and would only get confused.

 

[Catweazle]

That's kinda just saying the same thing a different way, Arainach.



Where the naivety factor kicks in is that generally people don't understand that 'upgrade compliance' and 'upgrade path' are two completely different things, which don't have a dependent relationship. 'Upgrade compliance' relates to eligibility for upgrading the license, whilst 'upgrade path' relates to the more practical task of upgrading the existing installation. When the procedure to be performed is a 'custom clean' install, then any consideration of 'upgrade path' becomes an irrelevence because the original installation isn't being updated.


Purchase a standalone copy of windows and what you are actually paying for is the license to use it rather than the product itself. Same things applies if you obtain Windows as a pre-installed item on a new PC. The relevent portion of the machine cost is covering your license to use, rather than your 'possession' of a working installation.

When you purchase and use an 'upgrade' Windows product what you are really paying for is an 'upgrade' of your license to use to cover right to use the newer product version rather than the older product version. 'Compliance' simply means that you've demonstrated that you have an earlier version to qualify the upgrade of license.



Microsoft further complicate the scenario, for the more naive folk, by making repeated claims that the installers for Windows Vista and beyond do not include a 'compliance check'. This claim is blatantly incorrect. From Vista onwards here is no longer the facility to boot from the new install disk and perform a clean install on a new hard drive, popping the old install disk in to verify compliance during the install. Instead, when an install key is used which falls within the 'allowable range' for upgrades, the installer will check to verify that a 'compliant' installation of Windows is already present on the machine. If no compliant installation is present then the installation process will refuse to proceed. If a compliant installation is found then the installer will check to see whether or not that inbstallation represents a 'valid upgrade path' for the new installation you have chosen to deploy, and present you with the 'Upgrade install' option if it is.

If Windows 7 works same way for upgrades that Vista did, you'll be prompted to boot to desktop in the old install, and launch setup from there in order to actually perform and upgrade install.