Windows 7 Installation - Transfer to a New Computer

How to Transfer your Complete Windows 7 Installation to New Computer​

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.

This tutorial will show you how to do the transfer.

   Information

Windows 7 System Preparation Tool is a powerful, native Windows tool. When for instance used in so called Audit Mode, it let's you to freely configure Windows 7 to be then deployed to other computers as hardware independent image.

In this tutorial we use System Preparation Tool (sysprep) to prepare your Windows 7 installation to be moved to a new computer, keeping all your installed applications, program settings and user profiles. You can use this method for instance when you have bought a new PC and want to transfer your existing setup completely, without need to reinstall everything, or when you want to make major hardware changes like change the motherboard or GPU, which would usually cause Windows to stop booting normally.

   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 do not recommend to use this method on RAID systems. All experiments on RAID I know have failed.

With the speed of today's hardware evolution, most of us geeks are upgrading the hardware more often than operating system. Upgrading hardware can be painfully slow process if we need to reinstall the operating system and all our installed applications, plus transfer program settings and user profiles.

Using sysprep makes this easy. Changing the motherboard, or for instance an old ATI GPU to a new nVidia GPU quite often causes Windows 7 not to be able to boot anymore. This fact is usually accepted by the user, who then reinstalls the OS and all applications and transfers user profiles from a backup location.

Same thing when buying a new computer with completely different hardware setup compared to the old one, or trying to restore a system image to different hardware setup. Normally this would include a complete reinstallation of Windows 7 and all applications.

Why not use sysprep to avoid reinstalling? Here are the different scenarios where you can use it.

   Warning

An upgraded Windows cannot be sysprepped. As this method is based in sysprepping, this tutorial is valid only for Windows setups which have not been upgraded.

This means that if you have for instance in-place upgraded Vista to Seven, or using Anytime Upgrade upgraded for instance a Home Premium to Ultimate, you cannot sysprep and this tutorial cannot be used in your case.

Notice that a repair install is also an upgrade install, so if you have ever done a repair install (= in-place upgrade to same edition), you cannot sysprep.

PLEASE DO NOT FORGET TO CREATE A SYSTEM IMAGE BEFORE PROCEEDING!​

As you can read on this thread, on rare occasions this method does not work. If this happens, you can always restore your system using your backup image.

Backup Complete Computer - Create an Image Backup
System Image Recovery

IE10 Users: Please read this article first: Sysprep Fatal Error With IE 10 (FIX) | System Administration

METHOD ONE

Changing hardware components but keeping old hard disk(s)

Use this method if you:
- Change other hardware components but keep your old HD containing Windows 7
- Move the HD containing Windows 7 to another computer

1. Before installing new hardware, boot Windows 7 normally
2. Disconnect all external hardware except mouse, keyboard and main display. If your system folders are located only on C: drive, disconnect all other hard disks except that containing the C:. In case of relocated system folders, for instance the profile folder Users located in another drive and other system folders on C:, first move the relocated system folders back to C: then disconnect all other drives. Reboot after this
3. Run Command Prompt as administrator
   .
   
   .
4. Type to Command Prompt: %windir%\System32\Sysprep\Sysprep.exe, and hit Enter
   .
   
   .
5. In sysprep dialog that opens, choose System Cleanup Action as Enter System Out-of-Box-Experience (OOBE), select Generalize, select Shutdown Options Shutdown. Click OK
   .
   
   .
6. Sysprep generalizes now your Windows 7 setup and shuts down your computer. Do not run any other programs during this phase!
   .
   
   .
   
   .
7. Switch the main power of your PC off and install the new hardware OR dismount the hard disk(s) and mount it (them) to a new computer
8. Boot the PC from sysprep generalized hard disk. You will notice Windows booting as if it was the first boot after installation, installing default drivers and updating registry. One or two reboots are needed, depending on your system specifications
   .
   
   .
   
   .
   
   .
9. When Windows finally boots up, you will need to enter all information as if this really was a new, fresh installation
   .
   
   .
10. Because your old user profiles already exist, Windows does not accept your normal username, but instead you have to create a new temporary user. I use username Test for this purpose
    .
    
    .
11. When login screen appears, choose your old user account to login
    .
    
    .
12. Windows boots now to default OOBE first boot desktop, with default 800*600 resolution and default theme. All your installed applications are there, as well as your old user profiles and folders. Windows has installed the default drivers for your setup, you can update them if needed
    .
    
    .
13. Go to Control Panel > User Accounts and delete the temporary user account (in this case Test) that you just created

METHOD TWO

Change the hard disk(s) or move Windows 7 setup to a new computer using third party imaging software

Use this method if you:
- Replace the HD containing Windows 7 on your old computer
- Move Windows 7 to a new HD on another computer

1. Follow steps 1 through 5 above (method 1)
2. Boot PC with an imaging CD/DVD (Paragon, Macrium etc.). See Macrium Reflect Free:at our sister site TenForums.com: Backup and Restore with Macrium Reflect Windows 10 Backup Restore Tutorials . Also see this post for a practical tip to create a Macrium system image.
3. Create an image of your system
4. Turn PC off, change the hard disk(s) and reboot with imaging application, restoring the image OR boot the new computer with imaging software and restore the image
5. Continue from step 7 above (method 1)

This procedure is failsafe, and works every time. There is nothing to worry, but of course it is recommended to make a backup before trying this. I have even used this method when some serious driver issues caused the PC to constantly crash (BSOD), to reset all drivers to Windows defaults and then reinstalling them one by one to find the culprit.

   Note

What does Sysprep generalizing do to my Windows 7 setup?

• All system specific information is removed or uninstalled
• Security ID (SID) of your hardware setup is reseted
• All system restore points are deleted
• All event logs are deleted
• All personalization is removed (taskbar, toolbars, folder options, start orb etc.)
• Built-in administrator account is disabled (if it was enabled) and needs to be re-enabled after the transfer if needed

What happens when booting first time after sysprep generalizing?

• First boot configuration is run
• New SID is created
• Re-arm counter is reseted if not already re-armed three times
• Windows 7 is booted using first boot default drivers and settings

I have tested all above mentioned methods with all versions of Windows 7, from Starter to Enterprise. It works every time, with one exception: for reasons unknown to me, sysprep seems sometimes dislike Windows Media Player networking service, which is by default started every time Windows 7 starts. In about every third time I've done this, I've got an error message when trying to generalize:



However, this is not a big problem. You just need to stop the WMP networking service, and run sysprep with generalize option again. You can stop the service in question by typing net stop WMPNetworkSvc to command prompt, and hitting Enter:



If you have any questions, do not hesitate to ask.

Happy computing!

Kari

EDIT: A Useful tip from xxxwea, as later confirmed by Victor:

Kari, just a suggestion.

You might note in the tutorial that if on first booting Windows can't finish configuring, a reboot into safe mode, then a normal reboot will allow it to finish successfully.

This has happened to me both times I used a sysprepped system drive in a new computer. I found the answer to this problem buried deep in this thread the first time I ran into it, and the same thing happened yesterday on a different computer.

It's a seemingly very silly solution, but it works. I do believe many people have abandoned their sysprep work when they encounter the problem.

I think the solution deserves more visibility.

 

[bhara]

it was nice but due to this some thing will get loose

better u guy can transfer the HDD to new computer and boot it with safe mode and install the drivers and restart it in normal mode

 

[Kari]

Should I clone my ssd to a hhd before I run sysprep? Then take the syspreped hhd to the new board, make sure it boots and then clone the hhd to the new sata3 ssd?

That's how I would do it.

 

[williamwclee]

in the tutorial, it is told after running the sysprep, next step is to clone/backup the harddrive and then restore the image onto another harddrive. As the system has already gone through sysprep, how could i do a cloning? Do i need a cd native booted cloning software? any suggestions?

 

[Kari]

Yes, you need a third party imaging solution that allows you to create an image when not booted to Windows. Macrium is one good solution.

 

[SevenRick]

Kari,

Question:

Why in post #14 below is it recommended to boot with an imaging CD\DVD? Once sysprep is complete and the hard drive moved into a new system, wouldn't the hard drive boot without the third party software?


The third-party software I use (Casper) does not require restoring the image. It clones the entire hard drive which is bootable as it is. Am I missing something here?

It simply means that if you want to transfer your Windows installation as it is, with applications and user profiles intact, to A) a new hard disk in your old computer, or B) to a completely new computer, you should do this:

• Boot your old computer normally to Windows
• Follow the steps 1 through 5 in method 1
• When sysprep is finished and computer shut down, boot it from an imaging CD/DVD. DO NOT BOOT NORMALLY TO WINDOWS!
• Now create a system image. Notice that this image contains at this point a complete image of your generalized Windows, ready to be booted "first time". Use external HD to store the image
• Shut down the computer

Now you have two choices, depending on what you are doing:

1. If you are changing hard disk to your old computer, do it now, then boot again from imaging CD/DVD and restore image to this new, virgin hd in your old computer. Boot then your computer normally from HD which now contains a generalized image of your old Windows setup
2. If you are transferring you Windows setup to a new computer, boot it with imaging CD/DVD and restore the image to its HD. Boot then the new computer normally from HD which now contains a generalized image of your old Windows setup

In both above mentioned scenarios you have restored a generalized image of your Windows setup to a new HD. Go back to tutorial method 1 following it from step 7 to the end, and you are done.

Kari

 

[Kari]

You are not missing anything. Quite an opposite, you have revealed an error in my response there. I have asked administrators to check if a member has deleted a post there, because I have really big difficulties to understand how I have responded so if the post you quoted is a response to the post above it.

The post in question is telling about scenario where HDD is changed. You only need to boot with imaging tool if / when you are moving the image to a new HDD. Only then.

If you move the HDD to new setup, you of course boot from that sysprepped HDD.

Thanks for showing the error in my response.

Kari

EDIT: Admin told me it's no longer possible to see if there were some deleted posts just before that post of mine. Anyway, I edited it now to answer the question above it.

I'm sorry that it has been there for quite a while now. The post did not made sense if it was a response to the question above it. Too long time now, I do not remember any deleted posts there but want to think there was some asking something that would have been answered with the post of mine you quoted. Don't want to think I'm such an idiot I would give so wrong answer...

 

[SevenRick]

Kari,

Well, that makes me feel better. I'm glad I could help clarify. That is the least I can do especially considering this is such a beneficial and informative thread.

Rick

 

[SevenRick]

Two follow up questions:

Are there any advantages to running sysprep in safe mode?

Is there a workaround for restoring lost personal settings, (toolbars, folder options etc) after running sysprep? Are these preferences stored in any particular folder(s) that could be copied over to the new system?

 

[ICIT2LOL]

Yes, you need a third party imaging solution that allows you to create an image when not booted to Windows. Macrium is one good solution.

Agree Kari I did find the later version of Macrium easier to use than the EaseUS to do that I was using as the problem with EaseUS is getting it back from large drive to small drive - can't be done.

 

[SevenRick]

I successfully ran sysprep, moved the ssd to the new machine and get the following errors and bsod:

1. Auto check program not found
2. Then windows logo, then blue screen flash with error c000021a "session manager initialization system process terminated."
3. immediate reboot

I was really hoping this would work, any ideas?

 

[apizz]

Failure to Complete Method 1

So I recently purchased a new motherboard so I can run sli on my computer rig. I have an SSD and an HDD, the former for boot and some applications and the latter for almost all of my games. I created backup images of both the SSD and HDD prior to doing anything.

I ran sysprep, checked generalized, and selected shutdown to prepare my PC with no issues. After replacing my motherboard however, when I reach step 7 instead of updating my registries and drivers to then restart and boot up, I keep getting an error message that the system configuration failed and that I need to restart my computer. Well, this keeps happening every time I restart.

I've looked on other forums about this issue but they're all regarding switching hard drives and not simply changing hardware and keeping everything else the same. I'm at a loss how to proceed . . .

Any help is much appreciated!

 

[Victor S]

I keep getting an error message that the system configuration failed and that I need to restart my computer. Well, this keeps happening every time I restart.

I don't recall the exact error message, but when I had an issue where configuration failed upon booting the sysprepped HD, I found the solution here.
When configuration fails, reboot into safe mode. It will fail again.
Then reboot into normal mode, and it will finish. Seems silly, but it has worked for me and others.

 

[Kari]

I keep getting an error message that the system configuration failed and that I need to restart my computer. Well, this keeps happening every time I restart.

I don't recall the exact error message, but when I had an issue where configuration failed upon booting the sysprepped HD, I found the solution here.
When configuration fails, reboot into safe mode. It will fail again.
Then reboot into normal mode, and it will finish. Seems silly, but it has worked for me and others.

That's the first thing I was thinking, too. A good tip, thanks Victor.

 

[apizz]

Thank you thank you Victor and Kari! You guys are the best. Computer is now installing devices, etc. (Step 7).

Terrific guide and support!

 

[SevenRick]

I successfully ran sysprep, moved the ssd to the new machine and get the following errors and bsod:

1. Auto check program not found
2. Then windows logo, then blue screen flash with error c000021a "session manager initialization system process terminated."
3. immediate reboot

I was really hoping this would work, any ideas?

Would the inability to not find the "auto check program" upon booting the syspreped drive have something to do with the "system reserve" partition being altered and Windows looking at the "C" drive at boot instead of system reserve partition?

 

[AndarielHalo]

I've scoured through this tutorial and the messages but it feels like I missed something...


The top of the tutorial warns that I should make a back-up image copy of my hard drive in the rare case that this transfer fails...

But when I looked into the thread, I found this post Kari made:

If you are keeping your old hard disk where Windows is installed, just changing the motherboard, there's no need to make an image. The image is only needed when you also change the hard disk.

So, when only changing the motherboard, do this:
- Sysprep as told in tutorial (Method One, steps 1 to 5)
- When computer is shut down, replace motherboard (Method One, step 6)
- Boot the computer (Method One, steps 7 to 12)

Given that I only want to change my motherboard and cpu, does this apply to me? Or is this just a case of "Always back up just in case" like an airplane seat floatation device?



As it stands, if there is a significant enough risk of losing all the data on my harddrive (like, between 5-10%) I'd sooner just buy a new copy of Windows 7 to install on a new harddrive (which I would need to buy as a back-up regardless).



Potentially an answer to my stuff: How would I know if this method doesn't work on me? Would there be a point where I could cancel the Windows installation or booting before it wipes my data? Or would it just automatically vaporize all the data on its own?

 

[Victor S]

Given that I only want to change my motherboard and cpu, does this apply to me? Or is this just a case of "Always back up just in case" like an airplane seat floatation device?

That's how I look at it. I've been restoring images for years. They've ALWAYS worked. No matter the success ratio with sysprep, it has failed for some people.
Let's say your new MB is bad, and has to be RMA'd. Do you want to go back to what you have while you wait out the RMA process? If you have an image you can do that immediately.
And if you do put your old MB back in, what if the sysprepped drive won't start Win 7 again. I don't know the odds on that, but I do know my success rate of restoring images to the same machine is 100%. So you can just restore the image, and avoid the new configuration of the sysprepped drive.
You've raised other questions about data that I can't answer, because I don't know your partitioning scheme. Installing Win 7 fresh will always raise questions of partitioning and possible data loss, so that has to be examined.
My bottom line is to alway take images, but what process is used really depends on the hardware you're working with, space available, partitions, etc.

 

[ICIT2LOL]

Hiyya Kari Now this is probably the dumbest query but I have read through the tutorial and am wondering why say changing a video card as you say from Ati to NVidia would cause Windows not to boot?

I can understand the mobo change and I now realise (I didn't till recently) that the OS is tied to the mobo, but as above I cannot get my head round the other hardware changes.

 

[Kari]

@AndarielHalo

I'm talking about two different images in the tutorial. It is really important you create a backup image always before you start actions like described in tutorial, in case something goes wrong. So, please backup your system before you start.

Then my post you quoted:

If you are keeping your old hard disk where Windows is installed, just changing the motherboard, there's no need to make an image. The image is only needed when you also change the hard disk.

So, when only changing the motherboard, do this:
- Sysprep as told in tutorial (Method One, steps 1 to 5)
- When computer is shut down, replace motherboard (Method One, step 6)
- Boot the computer (Method One, steps 7 to 12)

Here I am not talking about backup image. That was a response to someone who asked if he needs to make an image when he has sysprepped the HD and moves it to a new setup as described in tutorial's Method 1. If he has followed my instructions he had made a system backup image before starting but he don't have to image the sysprepped HD image because he keeps the old, now syprepped HD.

A bit confusing, trying in other words. Backup image is important before you start. To image sysprepped HD is only important (essential!) if you change the HD, move your Windows to another disk.

@ICit2lol

Yes, changing GPU does not generally cause boot issues but I have experienced them often enough to add that warning in tutorial.

Kari

 

[ICIT2LOL]

Thanks Kari I'll keep that in mind