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.

 

[MeiRct]

Transferring personalization

Hi Kari,

I think this is the best tutorial I've seen about migrating Windows 7.

4 years after publishing, and I'm wondering, any chance that there is by now a progress with transferring the OS personalization settings?

I saw this reply mentioning Easy Transfer, but the user didn't tell us how it worked for him.

We have new computers in our company for few months, and this is the only thing that prevents me from switching to one of them.

 

[Kari]

I saw this reply mentioning Easy Transfer, but the user didn't tell us how it worked for him.

Easy Transfer is my recommendation, easiest way to migrate the user settings.

A more work including alternative is to boot to Audit Mode, delete all existing user accounts, customize the default user profile (theme, colors, settings and so on), then sysprep with an answer file with variable CopyProfile set true:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            [hl]<CopyProfile>true</CopyProfile>[/hl]
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:X:\Sources\install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> 
</unattend>

After sysprep you need then recreate the users which get the customizations and settings from the modified default user profile. The problem is that as the CopyProfile only works when there are no existing user profiles, it's not very practical in this case.

If interested here's the tutorial: http://www.sevenforums.com/tutorials/285983-user-profile-customize-during-installation.html

This complete walkthrough might also give some ideas: http://www.sevenforums.com/tutorials/319903-windows-7-image-customize-audit-mode-sysprep.html

Kari

 

[MeiRct]

Thanks for the reply Kari.

Can you please tell what are the steps to combine Easy Transfer with each of the three methods from your tutorial?

And another major question:
Is it possible to switch between different versions of Windows 7, let's say from "Home Premium" to "Ultimate"?
Same question about switching from 32bit to 64bit, or the other way around.
If it's possible, what are the special or additional steps for achieving it?
(I'm asking about Sysprep as well as Easy Transfer)

 

[Kari]

Can you please tell what are the steps to combine Easy Transfer with each of the three methods from your tutorial?

1. Transfer user profiles using Easy Transfer (tutorial)
2. Generalize the Windows image as told in this tutorial (method 1, 2 or 3)
3. Move Windows to a new computer or hardware
4. Restore user profiles using Easy Transfer

Is it possible to switch between different versions of Windows 7, let's say from "Home Premium" to "Ultimate"?

No. You can use the Windows Anytime Upgrade to upgrade the current Windows edition to a superior edition any time you want to, before or after moving Windows to a new computer.

Tutorials:

• http://www.sevenforums.com/tutorials/88163-windows-anytime-upgrade-enable-disable.html
• http://www.sevenforums.com/tutorials/95744-windows-anytime-upgrade-how.html

Same question about switching from 32bit to 64bit, or the other way around.

Switching the bit version once Windows is installed is absolutely not possible. The only way to do this is a clean install. A 32 bit Windows will always remain 32 bit, to upgrade it to 64 bit version you need to do a fresh, clean install with a 64 bit install media and vice versa.

If it's possible, what are the special or additional steps for achieving it?
(I'm asking about Sysprep as well as Easy Transfer)

Sysprep has nothing to do with upgrades, see the answers above.

Kari

 

[wranglers1]

I know this is a windows 7 forum, but can I ask if the sysprep method described above would work for windows 8.1 retail?

 

[Kari]

I know this is a windows 7 forum, but can I ask if the sysprep method described above would work for windows 8.1 retail?

Hi Wranglers, welcome to the Seven Forums.

Yes. In all Windows version from Vista to Windows 10, this generalizing method is the only one recommended by Microsoft to move the installation to a new computer or hardware setup.

Do you you know our sister site the Eight Forums? If you get any issues doing this on Windows 8 or 8.1 start a thread there and let me know about it.

Windows 8 Forums

Kari

 

[Bill4Prez]

I've tried following this tutorial using method 3, but after generalising I'm unable to create the system image using Windows backup. When I click on create system image, nothing happens. Some googling leads me to believe that after running sysprep some services are disabled, is this possibly the reason? If so how can you create the image using Windows backup, or what else might have caused the issue?

I ended up just shutting down and creating an image with Clonezilla and the system I imaged seems fine after starting back up (except for having to do the restart in safe mode first trick).

 

[Kari]

Hi Bill, welcome to the Seven Forums.

Windows Backup is a bit tricky to start with and in Audit Mode sometimes impossible. In later versions of Windows it does not work at all when in Audit Mode, starting from Windows 8.

I recommend all users to choose Method Two using any third party imaging software instead of Method Three with Windows Backup. I use Macrium, you Clonezilla, other users other programs.

Good to know that you got your image anyway .

Kari

 

[dsa44]

Hi, thanks for this tutorial. I will be putting in a new mb/memory/cpu and was curious as to what would be the difference between doing the sysprep, or simply running the "repair" option from the win7 install disk after replacing the mb.
Thx

 

[Kari]

Hi, thanks for this tutorial. I will be putting in a new mb/memory/cpu and was curious as to what would be the difference between doing the sysprep, or simply running the "repair" option from the win7 install disk after replacing the mb.
Thx

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.

The decision is yours. The Sysprep method as told in tutorial works and is the official and only method recommended by Microsoft. All other third party methods to do the same are at least to some extent based on Sysprep (re: tools to capture your Windows installation from HDD and move it to SSD).

It's your computer, your choice. It might just work doing it as you described.

Kari

 

[dsa44]

Thank you for that. I will do a sysprep after a full image backup, but was just trying to get my brain wrapped around the differences, really as an intellectual exercise. (Back in the day, I remember removing items from the device manager before a mb swap.)
I suppose one big thing is that the repair option seems to be able to run only from within a booted windows desktop, so one would have to gamble that the system would even be able to get to the desktop after replacing the mb me thinks.
And just to verify, there would not really be a need to first run the "easy transfer wizard" since theoretically everything should stay intact.
Cheers, DSA

 

[Kari]

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.

 

[dsa44]

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.

 

[Kari]

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]

"Moving or copying a Windows image to a different computer without running sysprep /generalize is not supported."

Actually, i have done that once (without even knowing at that time about sysprep), and moreover, it was through an eSATA connection.
There are many things that "can't be done" )), but wich in practice are very well to be done (and also the opposite...)! Other exemples: a laptop that officially "cannot boot" through PCMCIA or ExpressCard... that actually boot it..., a laptop that officially "can not have or recognize" (even on the website of the chipset manufacturer...) more than 4gb of ddr2 RAM... that actually is very well with 8gb ddr2..., and so on.

 

[Kari]

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:

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.

 

[dsa44]

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.

Well sysprep completed fine. Swapped mb, rebooted with ahci mode, got the boot menu, hit windows 7 and got error.
Windows failed to load because the kernel is missing or corrupt.
File: /windows/system32/ntoskrnl.exe

It then suggests to load the install disk and "repair your computer"

Tried it again changing back to ide mode in the bios and same thing happened.

Anything else I can try??

Thx

 

[Kari]

Did you try the repair?

 

[dsa44]

Did you try the repair?

Trying it now....

 

[dsa44]

Did you try the repair?

Trying it now....

No good, even tried the repair in ide mode and ahci mode. Keeps saying ....ntoskrnl.exe..... kernel missing or corrupt.
I think I will try to restore the system backup image, then just try to reboot and see what happens, unless you can think of anything else.....