Windows 7 Installation - Transfer to a New Computer

Just remember, and this is quite important: if you have an OEM license you might get re-activation issues. The Sysprep removes all activation data and Windows needs to be re-activated.

With a retail license this is not an issue, for users of an OEM license I want to remind about this, the quote from the tutorial:

   Warning

Using this method causes Windows 7 to lose all activation information, and it needs to be reactivated afterwards. If your Windows 7 is an OEM version, you might not be able to reactivate it, at least not without phone activation option.

I can reactivate with MS. Thx
2 last questions.

First, my system was setup as a dual boot, xp and win7, with win7 the default. So when pc boots, it goes straight into win7 as default after lingering a few seconds on the dual boot menu. Can I still just follow the sysprep guide once both drives are hooked into new mb? Or do I need to do something to the dual boot? ( I really don't plan on going back into xp, but that drive has lots of linked data from win7) I attached an image of my system drives. C: drive Disk 1 is the Win7 and D: drive Disk 0 is the XP.

Second regards AHCI mode. My older motherboard is just plain ide. I know one cannot just change the bios from ide to AHCI as win7 will blue-screen. But after running sysprep and plugging into new MB, can I set the new MB to AHCI mode on first boot and let win7 reconfigure for such? I guess there is some improvement overall with AHCI and ssd's over plain ide mode.
Thanks again.

The Disk0 (XP disk) will be not affected in any way, your dual boot should work as before also after the sysprep. If any dual boot issues occur, you can always create a new dual boot menu with BCDEDIT. A worst possible scenario is that the dual boot is gone but all the content of disk0 is still there and can be accessed.

Switching to AHCI should also work without any issues. Sysprep and shut down, replace the motherboard, on first boot go to BIOS and change to AHCI, let machine boot normally.

Robotu said:

Actually, i have done that once (without even knowing at that time about sysprep), and moreover, it was through an eSATA connection.
...

In my opinion I already explained how it is. This from my earlier post just a few days ago:

Kari said:

Before trying to answer your question, look what Microsoft has to say about it. This quote from the very beginning of this tutorial:

To start, a warning from Microsoft:

   Note

Important

You must use the Sysprep /generalize command to generalize a complete Windows installation before you can use the installation for deployment to a new computer, whether you use imaging, hard disk duplication, or another method. Moving or copying a Windows image to a different computer without running the Sysprep /generalize command is not supported.

OK, let's forget the Microsoft's way to use the words "You must". It's just their way to tell you that this is the tested, working way to do this and that they recommend using it.

That being said, any a bit more advanced geek can remove all hardware related information manually, not needing Sysprep or any third party tools. In addition, sometimes the move of the Windows system hard disk to another PC or changing a motherboard simply works without any whatsoever issues.

Did you try the repair?