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.

 

[Kari]

They shouldn't be affected in any way. For Windows they are programs like any other programs, their own virtual drivers will remain in system. To be sure you need to try, I have never had any other virtualization programs installed on a Windows 7 system I have transferred to a new PC than Microsoft Virtual PC and XP Mode, and those worked well on the new system, too, after moving OS over.

 

[crashnbuen]

So, I tried to be extra careful and am now getting this error.

"The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install windows, click OK to restart the computer, and then restart the Installation."
[Setup is preparing your computer for first use]

I cant even get to F8 and go to safe mode. This might be even before that stage comes around.

I tried running the SSD in the original X61T also.

Thoughts? Suggestions?

 

[crashnbuen]

Kari - Please help. I took extra precautions now how do I solve this?

 

[Kari]

So, I tried to be extra careful and am now getting this error.

"The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install windows, click OK to restart the computer, and then restart the Installation."
[Setup is preparing your computer for first use]

I cant even get to F8 and go to safe mode. This might be even before that stage comes around.

I tried running the SSD in the original X61T also.

Thoughts? Suggestions?

Kari - Please help. I took extra precautions now how do I solve this?

I will response to all posts in my tutorial threads as soon as I can. I of course subscribe to them to get notified when there are new posts.

Please do not repeatedly message me. You have an issue, you post it here, when I'm online and have time I will check your post. OK?

Please be more precise. What did you do (tell as exact as you can)? In your message to me you told you took extra precautions? Which precautions? Do not leave anything out because you think it has nothing to do with this.

 

[crashnbuen]

I did the following:

Backup Image of entire SSD Disk using Acronis True Image.

DISABLE:
- Avira
- VMWare
- Oracle VBox

UNINSTALL:
- Thinkpad & Lenovo stuff
- Some other drivers as well

The SYSPREP went fine without any issues.

The Restart on new machine was going pretty well also and then got up to this point and boom:
SCREEN:
[Setup is preparing your computer for first use]

Message Box
"The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install windows, click OK to restart the computer, and then restart the Installation."

This messagebox keeps popping up everytime I restart.

Thoughts on what can be done? I cant get to Safe Mode using F8 or Advanced or any mode in anyway to pause this cycle.

 

[Kari]

My recommendation:

• Connect SSD back to old hardware
• Restore the system backup
• Backup your personal files and folders
• Connect SSD to new hardware
• Do a clean install
• Restore your personal files and folders from backup.
• Reinstall your software

 

[crashnbuen]

That's my backup plan. Is there anyway to bypass this issue faced post SysPrep?

Or something I can do prior to Sysprep to make this go through on my next attempt?

 

[Kari]

Did you try to boot the new hardware with install media (Windows 7 DVD or USB) and try the repair feature?

 

[crashnbuen]

Did you try to boot the new hardware with install media (Windows 7 DVD or USB) and try the repair feature?

Not. Would that have helped?

 

[Britton30]

Did you try to boot the new hardware with install media (Windows 7 DVD or USB) and try the repair feature?

Not. Would that have helped?

IT might but you have to try it to see.
http://www.sevenforums.com/tutorials/3413-repair-install.html#post31238

Sorry, wrong tutorial, use Kari's suggestion instead.

 

[Kari]

IT might but you have to try it to see.
http://www.sevenforums.com/tutorials/3413-repair-install.html#post31238

I would first try the system repair option, booting from install media and selecting Repair your computer:



I do not know if it helps but it is definitively worth to try. Select the Startup repair option:

 

[crashnbuen]

Oh! this one. Got it. Will try. I thought you were saying Repair Install.

 

[crashnbuen]

I ended up restoring from Backup Image and running Startup Repair (as the restored image did not boot). Go it boot and running on X61T

And then after making a few System Restore snapshots on X61T, popped it in straight into T61 from X61T. (Very similar chipsets) - So, except for few drivers that had to be updated, its running well and good.

I might try SysPrep over next weekend with the additonal steps recommended by Kari and see if it can be a cleaner leaner machine with a fresh Hardware driver base.

 

[yjgfikl]

Secondary Drive

Hey Kari, you must be exhausted from all these questions.

First, I'd like to start by thanking you for this awesome guide. I've got one hopefully simple/quick question. I'll be upgrading my motherboard and processor within the next few days. I've got Windows 7 Pro installed on my SSD, and the majority of my programs/games on a regular hard drive. Will the programs still refer to my P: drive for programs after sysrepping?

Thank you so much for this thread, and I'm sorry I had to contribute to the question-asking.

 

[Kari]

Hey Kari, you must be exhausted from all these questions.

First, I'd like to start by thanking you for this awesome guide. I've got one hopefully simple/quick question. I'll be upgrading my motherboard and processor within the next few days. I've got Windows 7 Pro installed on my SSD, and the majority of my programs/games on a regular hard drive. Will the programs still refer to my P: drive for programs after sysrepping?

Thank you so much for this thread, and I'm sorry I had to contribute to the question-asking.

Sysprep does not change the references to various drives. The only thing it does if used as told in this tutorial is to remove all hardware specific information, to allow you to move the Windows to a new computer.

A program installed in X: will still run from X: after the move.

 

[Scoop]

Kari,

Great thread I read it all but I may have missed an answer to a couple of questions that I have about Sysprep.

- I'm running Win 7 x64 Home Premium OEM version. My PC was built at a local store (Micro Center) and was originally configured for RAID 1 . I had problems with the array so a few months after the initial PC build, the store disabled the RAID config and re-installed Windows.

Since Windows was re-installed after the initial install, I'm guessing that Sysprep won't work for me. Does that sound right?

- Does Sysprep work with Windows OEM version, but possibly requiring a phone reactivation from MS?

 

[Britton30]

It will work as far as I know it is a reinstall not an upgrade, say, from Home Premium to Ultimate. It works fine if your OS is a system Builder type of OEM.

 

[Kari]

Since Windows was re-installed after the initial install, I'm guessing that Sysprep won't work for me. Does that sound right?

If it is the first, initial installation of Windows or a reinstall is totally irrelevant. Sysprep works always when Windows is installed clean (Custom install instead of Upgrade install), regardless of if an OEM or Retail install media is used or how many times it is reinstalled. Microsoft does not support sysprepping Windows when it is in-place upgraded. There are three of these unsupported scenarios:

1. An older Windows version is upgraded to a later version keeping installed software
2. A Windows edition is upgraded to a superior edition of the same version keeping installed software
3. Any Windows version edition and version is repair installed (repair install = in-place upgrade to same edition and version)

- Does Sysprep work with Windows OEM version, but possibly requiring a phone reactivation from MS?

Sysprep works on any Retail and OEM version exactly the same way. A sysprepped Windows needs to be reactivated which in case of OEM version means it can usually be reactivated only when it stays on the same hardware. Moving a sysprepped OEM Windows image to another computer or same computer with new hardware components does usually not work, not even with phone activation.

Internet is full of success stories about users who have managed to reactivate an OEM Windows on different hardware; however, I do not want to create false expectations so I do not recommend transferring an OEM Windows. it might work, depending on the mood of the MS support tech who takes the call but it cannot be guaranteed.

Kari

 

[Scoop]

Thanks for the info. I suspected that (OEM married to the MoBo/PC hardware) but I wanted to ask anyway.

I don't anticipate the need to try moving my OEM install to new hardware but if something happened to my MoBo, I might try it and see what happens.

I use Acronis (2011) for backups and it includes the "universal restore" option (restore to dissimilar hardware) but if I'm understanding the OEM issue, that wouldn't work.

 

[Britton30]

Generally a factory OEM, such as Dell, HP, etc, can't be moved. System Builder OEMs can be but will take a call to MS to reactivate it.