Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just taken out a hard disk with Windows Server 2008 on and plugged it into a different PC and tried to boot it - it is blue screening and I can't even tell what the message says as it reboots immediately. I take it I cannot trasfer one hard disk with operating system installed straight onto another PC with a diff motherboard. I know Windows 2000 didn't like it but I'm sure XP was fine with it. Although I have limited experience with Server products I just thought I would double check.

share|improve this question
The problem also happened to me when I migrate Window 7 from a 8 yr old laptop to a new model. – abbr Jan 20 at 23:25
up vote 3 down vote accepted

The most probable reason you are getting a blue screen is conflicting drivers. Your Windows install is set up to boot a certain set of drivers meant for your old system and now that you are plugging the drive into a new machine, the drivers are causing problems.

You can attempt to recover/repair the installation using your Windows Server DVD (boot to the DVD and select the Recovery Console).

With a repair install you shouldn't lose any data, but the drivers should get updated automatically for your new system.

Keep in mind that you should never try this, and that you risk losing your data. Server migrations are not as simple as just plugging in the drive into a new machine, you have to account for the hardware changes that will occur before hand.

share|improve this answer
Aren't hardware auto-discovered and drivers installed on-demand? Why doesn't Windows installation program on boot suffer the same problem? I don't know about Windows but there are LiveCDs for Linux that doesn't require OS installation and works on most hardware. How do these programs handle hardware variation? – abbr Jan 20 at 23:21
Basically I would like to know more specifically what device driver can lead to blue screen. – abbr Jan 20 at 23:30

I know Windows 2000 didn't like it but I'm sure XP was fine with it

This is not true. Unless you were extremely lucky or were transferring between two nearly identical machines, XP did not support transferring the system disk to another computer.

Starting with Windows Vista (and including the associated server operating sytems: Server 2008 and Server 2008 R2), Microsoft changed the installation process such that it copies a generic system image to the disk that can reconfigure itself for whatever hardware it finds. This makes the odds of success for an endeavor such as much higher. However, this operation is still highly suspect, as a lot of things still happen on first boot and once certain drivers are installed they can conflict with other hardware.

share|improve this answer

Go to your BIOS, and set the hard drive mode from AHCI to compatibility. It NEEDS to be the exact same setting as your old computer.. (so if your old one is AHCI, and this one is compatibility, change that).

With the wrong storage driver, it can't read the drive, and it will blue screen like that every time. We've been seeing this exact problem moving drives between identical laptops at work.

If you can boot it to compatiblity mode, you can then look for AHCI drivers for your storage hardware, and update.

share|improve this answer

There is an easy way to migrate a hard drive to a new machine without reinstalling Windows: use the sysprep tool. It "generalizes" the Windows installation back to a "System Out-Of-Box Experience (OOBE)." In this mode, Windows will install needed device drivers for the new hardware the first time it boots.

See this guide for details; it targets Windows 7, but sysprep is installed by default for Windows Server 2008 as well.

Note that this process does rebuild portions of your registry, so you may lose certain configuration settings. E.g., when I personally used this technique, I was prompted to reenter the license key for some purchased software.

Finally, caveat emptor: Microsoft's sysprep article explicitly states that sysprep should not be used to reconfigure an existing Windows installation. That said, I have successfully used this approach to swap the hard drives between two different Windows 7 installations, and it worked like a charm—whereas without running sysprep, both machines blue-screened on boot after being swapped.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .