Moving HDD with Windows from one motherboard to another

I plan to add a HDD to my desktop just to install Windows 7 Pro x64 on it then move that hard drive to another computer. During installation I plan to enter the key for Windows 7 that belongs to the PC where the HDD will ultimately be moved.

My concerns are:

• Will the system boot from that HDD on another computer (if I set correct settings in BIOS, of course)?
• Is there going to be any problem with drivers on the other computer if Windows automatically installed drivers for the first motherboard?
• Are there other problems that might occur during this kind of operation?

Solution 1:

Moving a Windows Installation to Another Computer

1. If possible, don't enter the product key until you move the hard disk to the destination computer. You will have 30 days from the time of installation before you are required to provide the product key, so there's no rush to activate. If you have already activated Windows, then you may need to purchase another license for the destination computer (one exception is if you have a Retail copy of Windows which Microsoft's EULA permits being moved from one computer to another).

   When you activate Windows, it calculates a hash based on certain major hardware components in the computer, such as the motherboard, video card, and hard disk. The Windows license gets linked to this "fingerprint". If you were to activate Windows while installed on the source computer, that act would assign the license (via the product key) to that computer.

   If any of these fingerprinted components change, Windows may require re-activation. Changing the motherboard will definitely deactivate Windows. If this happens too many times, Windows will refuse to activate over the Internet.

2. Pre-install the storage controller and network drivers required by the destination computer. Thanks to Plug and Play, Windows will be able to automatically detect and install most of the drivers required by the destination computer. One critical exception is the boot drive's storage controller. This driver must be initialized before the PnP subsystem is loaded. If Windows doesn't have the correct storage driver, it will fail to load with a STOP 0x7B (Unmountable Boot Volume) error. Fixing this is time-consuming.

   Windows can boot without network drivers, but if the required driver isn't an inbox driver and you don't have access to the Internet, it can be a pain to get the network driver copied to the machine. In particular, you need access to another computer with Internet access. It's just easier to already have it on the machine.

3. If you're doing a clean install, consider using Sysprep. Sysprep is what OEM and System Builders use to pre-install drivers and other programs on a Windows installation image before deployment. After customizing the image, it is "armed". The next time the image is booted, the Mini Setup wizard runs and "installs" Windows (Warning: this removes existing user profiles!). This might be overkill for your situation, but worth consideration. This TechNet article on SysPrep is a good place to start.

   Note: Do not use Sysprep if you intend to keep your existing user profile(s)!