Windows 7 Installation - Transfer to a New Computer

Just wanted to thank you for posting this. It worked like a charm ONLY after I connected my SATA Optical DVD drive to the motherboard. It error-ed out 6 times+ in a row until I reconnected the DVD Optical Drive (which didn't contain a disk) and then rebooted. It completed the entire transition without a hitch and I was off and running.

Great work to everyone in this community, the best I've seen on the internet. Very thorough and detailed.

Thanks Kari,

for this very informative information.
I followed this guide, but had the fatal "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer." Looping over endlessly.
I looked though all the posts and on post #193 Paul RJ's solution saved my bacon. Thank You Paul. Just a note: his guide said to use SHIFT F11 but for me it was SHIFT F10 to get me to the windows Command Processor window.

The rest was easy and my son with his new motherboard with AMD APU and all his games on his old hard drive was up and running. That was two days ago with no issues.

Thanks again Kari for the guide and Paul for your post. :)

Hi, I'm from Italy and just registered to this forum. I have carefully read this interesting tutorial since I have plans to change only motherboard and cpu and hoping that win7 pro installed on an SSD will recognize the new HW.
On a Command window I have just tested sysprep.exe which immediately returned an error message saying the following (I have to translate from the italian text): Impossible executing sysprep in a computer upgraded to a new Window's version. It is only possible in a personalized (clean) version of Windows.
What should I do?
Thank you for your help.

Solved, I deleted the registry's key called "upgrade" on HKEY_LOCAL_MACHINE\system\setup
I wonder why my system was considered "upgraded"! Perhaps because it was sold along with some hardware, so like an OEM version. Is it possible?

Hi Guys
My problem is a little different. The old motherboard is FUBAR so I am unable to change the system to a generic windows system with sysprep. I found an interesting article that uses DISM to replace the drives of the installed windows system Here.
However after adding all the new drivers using my new MB driver disk the system now get stuck in the repair loop. I have also followed the other article in this site about the repair loop where I have replaced the registry with the backup copy. which took me back to the blue screen I got after booting the first time on the new hardware.
So in my wisdom I decided to try the following:
Restore old registry
use DISM to add the new drivers to the windows
Restart
No joy
The system still wants to try and repair itself and fails with the following message
Problem Signature
Provider Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200305
Problem Signature 05: AutoFailover
Problem Signature 06: 17
Problem Signature 07: NoRootCause
OS Version 6.1.7600.2.0.0.256.1
Locale ID 1033

So the question is how can I prevent the system from going into thew repair loop
Thanks for you help

I'm again up and running but had to solve another bug of sysprep; try to go on Services (services.msc) scroll down to Windows media Player Network Sharing Service and disable it. Click OK and reboot. Run again sysprep and now it should work. In my case the sysprep routine took 4 hours!!!

Kari said:

Hello GFdS, welcome to the Seven Forums.
You didn't read the tutorial to the end? This quote from my tutorial, first page on this thread:

Very sorry! yes, I also saved and printed your tutorial, but since I decided to go for Method One I was silly enough not to read your excellent tutorial to the last line

The system is OK but there is a glitch which I'm going to explain in a dedicated topic.

Thank you again! :)

Gianmaria