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.

 

[Wozby]

To fix sleep mode problem try turning off network adapters, and audio controllers. Go to device manager and then go to power management, to turn off these devices

Ok, I right clicked my computer, pressed manage, then I went to device manager, but I cannot find anything that says power management.

Mate power management is usually in the Control Panel > Power options.

Hmm, that's not what I'm looking for, unfortunately. Thanks for the reply, but what Arianna3 is suggesting is something different, but I'm not sure exactly what. Arianna3 said to go to device manager and then power management, but I do not see power management in Device manager, and when I go to the normal power management under control panel, there's no options for turning off network adapters or audio controllers. Also, under the control panel power management, there is no option for having the computer automatically go into sleep mode after a certain period of time. I wonder if this is a drawback of the motherboard/cpu I just installed, but I have no idea.

 

[Arianna3]

Go to device manager, click on network adapters, click on the controller displayed under network adapters and you will see power management

 

[Wozby]

Go to device manager, click on network adapters, click on the controller displayed under network adapters and you will see power management

Thanks anyway, but I managed to fix the problem by reinstalling my graphics drivers.

 

[A Guy]

Go to device manager, click on network adapters, click on the controller displayed under network adapters and you will see power management

To clarify for any other readers

Device manager> Expand Network adapters> Right click on the adapter> Properties...THEN you'll see Power management

A Guy

 

[Wozby]

Administrator/permissions problems after transfer to new mobo/cpu

As the title says, ever since I transferred my HDD over to my new motherboard, I've been having all kinds of problems with administrator access and permission to access certain folders and what not.

For example, at least one of the games on my HDD won't work unless I run as administrator, even though I never needed to do that on my old mobo. Other problems include: certain programs not being able to start or complete some task because I need to run them as administrator, even though I didn't need to before the transfer; google chrome not being able to install some extensions unless it is run as administrator (I also just figured out why one of my extensions wasn't working. It couldn't or didn't have permission to access a folder in the Chrome appdata), and internet explorer not downloading anything unless I run as administrator.

So, my question is how I am supposed to re-give my account administrative control so my programs work without me having to find out what folder is causing the problem just so I can go open the folder and confirm administrator access?

Thank you for helping.

 

[oreo27]

Hi All,

I wonder if anyone has ever gone through what I'm about to do. Basically, the machine I'm currently using a sysprep image coming from an old hard drive and motherboard. This time around, I'm planning to change my processor as discussed on this thread:

http://www.sevenforums.com/hardware-devices/343252-will-amd-fx-6300-work-asrock-n68c-gs-fx.html

I'm planning to once again sysprep my system to be ready for the newly installed processor. Will it work? Do I need to do it in the first place?

 

[Kari]

I'm planning to once again sysprep my system to be ready for the newly installed processor. Will it work? Do I need to do it in the first place?

There are almost as many answers and opinions about this as there are geeks . My stand should already be known, I always refer to this:

   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.

(Warning from a Microsoft TechNet support article, also shown at very beginning of this tutorial.)

Replacing processor counts as "new computer". In my opinion, based on quite a long experience, I recommend you to generalize your Windows installation with Sysprep before replacing the CPU.

If doing so, please do not forget this (also told in 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.

Kari

 

[oreo27]

I'm planning to once again sysprep my system to be ready for the newly installed processor. Will it work? Do I need to do it in the first place?

There are almost as many answers and opinions about this as there are geeks . My stand should already be known, I always refer to this:

   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.

(Warning from a Microsoft TechNet support article, also shown at very beginning of this tutorial.)

Replacing processor counts as "new computer". In my opinion, based on quite a long experience, I recommend you to generalize your Windows installation with Sysprep before replacing the CPU.

If doing so, please do not forget this (also told in 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.

Kari

Thanks for the input. I'm too lazy to re-install everything as it will take a lot of time. It's easier to re-activate Windows and some other applications tied to the GUID of the PC. Hopefully I get to replace it in the coming weeks.

 

[Kari]

I would appreciate if you kept us informed, how it went.

 

[oreo27]

I would appreciate if you kept us informed, how it went.

Sure thing! I'll let you know in about 2 weeks

 

[alicemalt77]

Hi Kari
Can "SYSPREP Generalise" be used to -- transfer the OS of a SATA HDD to a SATA SSD ?
Thanks

 

[Kari]

Hi Kari
Can "SYSPREP Generalise" be used to -- transfer the OS of a SATA HDD to a SATA SSD ?
Thanks

Hi Alicemalt77, welcome to the Seven Forums.

Yes, it can, although most SSD manufacturers also offer tools to do that. If you decide to use this method, it's Method Two or Three for you.

Kari

 

[alicemalt77]

Thanks Kari.
So there wont be any issue with TRIM or whatnot using Method 2 & 3 ??

 

[Kari]

There might be, that's why I mentioned that SSD manufacturers provide the tools for moving your Windows from HHD to SSD. Consult the manual of your SSD to see details.

Personally I have never done this with an SSD, I cannot tell about pros and cons.

 

[RaviR]

Hello All,

So basically what I want to do is change my motherboard because my x16 slot is not working, in researching how to do so I came across this tutorial. I have a few questions about my setup and doing this method, I'm sorry if it was asked already in the thread.

Currently my setup is an SSD as my OS, a 1TB WD Black HDD as my game installs - meaning all my game installations go to D:\Program Files, My Temp folder is also on this HDD, another 1TB WD Blue HDD as My Documents and Movies etc files are here. Honestly when I first got my system I had done some configurations to extend my SSD's life and unfortunately I cannot remember all the stuff that I did.

So, can I just do the sysprep + image and change my motherboard? I'm planning to get back the same model Mobo so just making sure it will work.

Any other information required please let me know.

*edit*

I believe I had followed this tutorial way back when I got my system:

http://lifehacker.com/5802838/how-to-maximize-the-life-of-your-ssd


Thank you

 

[Kari]

Basically all you have to do is to do as told in Method One, the simplest one. Disconnect all external devices except the main display, mouse and keyboard, run Sysprep with both generalize and shutdown switches, replace the MoBo and reboot.

Please create a system image or backup your files using any other method before proceeding.

Kari

 

[RaviR]

Woohoo! Thought I would have lost the configurations etc. Thank you for the help

 

[Kari]

Just a word of experience: as always with the computers, anything can go wrong, even in a well documented standard procedure. Do not forget to make a backup first!

 

[ICIT2LOL]

Agree with Kari mate I especially always back up the registry after a clean install or before I do any changes to it. I find that a really good safety net.

 

[rayd]

How To Clear Just Computer Name Before Imaging

I have a computer with some softwares that I don't have the source installation files to install on another PC. All our PCs are same model and spec. I've imaged the source PC and deployed the image to other PCs without any issue, but I the computer name could be the issue. As all computer names would be the same.

How I can clear just the computer name on the PC before shutting down and getting image using 3rd party software, so on first startup after image deployed, system will ask just for computer name?

I tried sysprep via GUI but it's clearing some other configs that I don't want to change (change in log on screen and more).

I tried playing with ComputerName key in registry, with no luck.