Windows 7 Installation - Transfer to a New Computer

Kaktussoft · 09 Apr 2013

iamjim said:

I've done the registry changes, so it may be a while before I see you again. I can't thank you enough for all your help.

Backup only takes 1 hour or maybe 2 hours. Didn't you make a backup before trying sysprep (the failed attempts)?

Kaktussoft · 09 Apr 2013

iamjim said:

I've done the registry changes, so it may be a while before I see you again. I can't thank you enough for all your help.

Sorry.. there's more to change. Read #490 again. I editted it

iamjim · 09 Apr 2013

I test everything I can before depending on it. The backup takes an hour and the restore takes an hour and fifteen minutes, and if it had worked I might have gone on to replace the motherboard. Unfortunately things didn't work out. The sysprep executed with no error messages. I tried to restart Windows on my existing system to prove this process works -- it didn't. It would reach the point where Windows displays the colorful balls and has them rotate among themselves. When the first ball (it's the red one) appeared it would instantly reboot. It recycled at this same point about 4 times when I gave up and restored my backup.

Yes, I backed up before trying sysprep the first time. That was a few days ago so my system has changed since then.

Are you saying the changes highlighted in red in #492 are incorrect? If so, do you think that's what caused the restart problem?

iamjim · 09 Apr 2013

Latest version:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Cleanup]
"{67196725-a666-73a6-a048-412e48a3b856}"="C:\\Windows\\System32\\spopk.dll,Sysprep_Clean_Opk"
"{1e7f4452-a4b4-5a32-d01e-70397b096ced}"="sqmapi.dll,SqmSysprepCleanup"
"{2c8a362b-4dc1-38b9-c4d8-ce732ddcc48e}"="C:\\Windows\\System32\\wevtapi.dll,EvtIntSysprepCleanup"
"{86297dc3-52b0-7d4e-f9a8-572bb66ac5ae}"="C:\\Windows\\System32\\LangCleanupSysprepAction.dll,Sysprep_Generalize_MUILangCleanup"
"{03513543-c453-2e4f-3200-c2f12d89732a}"="C:\\Windows\\System32\\shsetup.dll,Sysprep_Cleanup_Shell"
"{1f954290-a3bd-7c6b-ac99-fda4b6fe1603}"="wer.dll,WerSysprepCleanup"
"{67011352-10f6-73b5-0c1b-833a374ea884}"="C:\\Windows\\System32\\spnet.dll,Sysprep_Clean_Net"
"{d9d03ab7-c7a6-4587-1dcd-fb0609f92d84}"="C:\\Windows\\system32\\capisp.dll,CryptoSysPrep_Clean"
"{79b40229-f48c-7547-16d3-ec814bdc5adc}"="C:\\Windows\\system32\\msdtcprx.dll,SysPrepDtcCleanup"
"{352676dd-145f-cf4f-feb3-aa882aa02408}"="C:\\Windows\\System32\\mssrch.dll,MSSrch_SysPrep_Cleanup"
"{f9e8597e-e3f1-9942-5fbc-2ce1ce25c0e2}"="C:\\Windows\\System32\\sysmain.dll,PfSvSysprepCleanup"
"{ccf004d0-c18e-a2d4-b4ea-08ccb5259f11}"="srcore.dll,SysprepCleanup"
"{de7df4f0-0ce9-ca23-6049-1807de6941d3}"="drmv2clt.dll,Sysprep"
"{9733bd0b-72a8-af29-76ba-be8ae2c8be6f}"="C:\\Windows\\System32\\spwinsat.dll,Sysprep_Clean_WinSAT"
"{b4db0c88-1c6a-c5e8-f385-df67f3f1f575}"="C:\\Windows\\System32\\tapisysprep,TapiSysPrepClean"
"{e0053bef-049c-9ba1-e7db-793f9e538edd}"="C:\\Program Files\\Common Files\\Microsoft Shared\\Ink\\IpsMigrationPlugin.dll,Sysprep_Cleanup_IPS"
"{EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80}"="C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize]
"{67196725-a666-73a6-07bd-00f3276e41cf}"="C:\\Windows\\System32\\spopk.dll,Sysprep_Generalize_Opk"
"{899480af-8f8b-16c1-58aa-df121c7314ed}"="C:\\Windows\\System32\\reagent.dll,WinRE_Generalize"
"{8bc7dae9-655e-8ca5-d3d1-771286930ef6}"="C:\\Windows\\System32\\wuaueng.dll,GeneralizeForImaging"
"{1e7f4452-a4b4-5a32-5cc0-12a85b132913}"="sqmapi.dll,SqmSysprepGeneralize"
"{d0c365cf-6d23-9db2-b74d-4e1efd035af7}"="C:\\Windows\\System32\\sppnp.dll,Sysprep_Generalize_Pnp"
"{960b724d-0479-6dd8-0470-6c42dc9b8f85}"="C:\\Windows\\System32\\iphlpsvc.dll,IphlpsvcSysprepGeneralize"
"{243bb634-be68-0139-f4c8-f1c87dade9d7}"="C:\\Windows\\System32\\setup\\tssysprep.dll,LSMSysPrepBackup"
"{df593d24-f963-8be2-86d6-c722da22bf5b}"="C:\\Windows\\System32\\setup\\tssysprep.dll,RdpSysPrepGeneralize"
"{03513543-c453-2e4f-5ee6-b970cace3cd8}"="C:\\Windows\\System32\\shsetup.dll,Sysprep_Generalize_Shell"
"{1f954290-a3bd-7c6b-2062-3fd9d1266740}"="wer.dll,WerSysprepGeneralize"
"{4840d621-1b47-334f-b1a6-321233838362}"="C:\\Windows\\System32\\dhcpcsvc.dll,DhcpClient_Generalize"
"{67011352-10f6-73b5-85e9-6064e10071b9}"="C:\\Windows\\System32\\spnet.dll,Sysprep_Generalize_Net"
"{3aa3f98d-491f-7656-533f-7db889fff253}"="C:\\Windows\\System32\\slc.dll,SLReArmWindows"
"{d9d03ab7-c7a6-4587-c28d-ccc47a787790}"="C:\\Windows\\system32\\capisp.dll,CAPISysPrep_Generalize"
"{6a6b0fac-5606-6e68-410d-e7bf974f5136}"="C:\\Windows\\System32\\spbcd.dll,Sysprep_Generalize_Bcd"
"{8fd6ce7c-4301-d490-719b-d787d2bde1cd}"="C:\\Windows\\System32\\nlmsprep.dll,NetworkListManager_Generalize"
"{79b40229-f48c-7547-1eb2-96b7091aa28f}"="C:\\Windows\\system32\\msdtcprx.dll,SysPrepDtcGeneralize"
"{8dde3abb-19cb-88f8-4e07-05c697cc2872}"="RacEngn.dll,RacSysprepGeneralize"
"{20b6ca3b-166d-4e8d-af73-72df2987e480}"="msmmsp.dll,MountMgr_Generalize"
"{71e01f6c-a271-b3b1-05f0-8c48a330cb4c}"="C:\\Windows\\System32\\winshfhc.dll,MRTComponent_Generalize"
"{ccf004d0-c18e-a2d4-ee22-e585dac90889}"="srcore.dll,SysprepGeneralize"
"{b636fa27-124f-6436-6a6f-2fe2739a2b89}"="C:\\Windows\\System32\\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize"
"{EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1}"="C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp]
"DoNotCleanUpNonPresentDevices"=dword:00000000
"PersistAllDeviceInstalls"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize]
"{67196725-a666-73a6-f6ab-3497d0a40953}"="C:\\Windows\\System32\\spopk.dll,Sysprep_Specialize_Opk"
"{1e7f4452-a4b4-5a32-23c7-60544b9fbb46}"="sqmapi.dll,SqmSysprepSpecialize"
"{d0c365cf-6d23-9db2-a63c-82c27e3d227b}"="C:\\Windows\\System32\\sppnp.dll,Sysprep_Specialize_Pnp"
"{f2cc75b9-d402-9402-88bf-66c14455b53b}"="C:\\Windows\\System32\\scecli.dll,SceSysPrep"
"{6df51e09-336f-ea94-0218-900956130400}"="C:\\Windows\\System32\\setup\\tssysprep.dll,RCMSysPrepRestore"
"{243bb634-be68-0139-2848-d06e242bc47b}"="C:\\Windows\\System32\\setup\\tssysprep.dll,LSMSysPrepRestore"
"{c6f34f3e-6ff5-8e21-4561-c2be81045f3e}"="C:\\Windows\\System32\\oobe\\winsetup.dll,SpSetupOnlineSettingsSpecialize"
"{df593d24-f963-8be2-2e23-229f6b9bef89}"="C:\\Windows\\System32\\setup\\tssysprep.dll,RdpSysPrepRestore"
"{03513543-c453-2e4f-0753-7a178cea9807}"="C:\\Windows\\System32\\shsetup.dll,Sysprep_Specialize_Shell"
"{1f954290-a3bd-7c6b-71c7-f5472ac291e2}"="wer.dll,WerSysprepSpecialize"
"{ee629431-b0b8-b5bf-594c-604cd9837b21}"="C:\\Windows\\system32\\catsrvut.dll,SysprepComplus"
"{d9d03ab7-c7a6-4587-b30d-046ffeeb096e}"="C:\\Windows\\system32\\capisp.dll,CryptoSysPrep_Specialize"
"{6a6b0fac-5606-6e68-30fc-1a64408619ba}"="C:\\Windows\\System32\\spbcd.dll,Sysprep_Specialize_Bcd"
"{79b40229-f48c-7547-35a2-cee9227ca977}"="C:\\Windows\\system32\\msdtcprx.dll,SysPrepDtcSpecialize"
"{8dde3abb-19cb-88f8-9f6c-bb34f0675314}"="RacEngn.dll,RacSysprepSpecialize"
"{b2bcbf98-0698-50af-2dd3-55500a4d8173}"="C:\\Windows\\System32\\aecache.dll,Sysprep_Clean_AECache"
"{27134efe-69d3-9b47-dd9d-054d61ca886d}"="fthsvc.dll,FthSysprepSpecialize"
"{97134f37-94aa-b706-1323-32a78266ef5a}"="radardt.dll,RdrSysprepSpecialize"
"{b7124681-dafe-6f39-7452-7905c40bdf5f}"="DDACLSys.dll,DDACLSys_Specialize"
"{EC9FE15D-99DD-4FB9-90D5-676C338DC1DA}"="C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE"

Kaktussoft · 10 Apr 2013

iamjim said:

I test everything I can before depending on it. The backup takes an hour and the restore takes an hour and fifteen minutes, and if it had worked I might have gone on to replace the motherboard. Unfortunately things didn't work out. The sysprep executed with no error messages. I tried to restart Windows on my existing system to prove this process works -- it didn't. It would reach the point where Windows displays the colorful balls and has them rotate among themselves. When the first ball (it's the red one) appeared it would instantly reboot. It recycled at this same point about 4 times when I gave up and restored my backup.

Yes, I backed up before trying sysprep the first time. That was a few days ago so my system has changed since then.

Are you saying the changes highlighted in red in #492 are incorrect? If so, do you think that's what caused the restart problem?

the registry changes are done correct!

Are you willing to skip sysprep and use another method? Of course you must have a good backup!

uninstall all software no longer needed. Graphics cards utilities and network card utilities for example. All the software for onboard devices.
Open device manager and uninstall all devices no longer needed (don't reboot)
Upgrade graphics driver to "Standard VGA-graphics adapter" (don't reboot). But only if it was onboard.
Upgrade SATA driver in IDE ATA/ATAPI -controllers as well to standard stuf. This is very important!! (don't reboot)

So just cleanup a bit.

Just right click on the device in device manager and select "upgrade driver"->from computer->pick from list. Put checkmark at "display compatible drivers". Take the standard microsoft driver.

These instructions are made on dutch machine so maybe I translated not 100% correct.
Now shutdown (not reboot) machine and power off completely (disconnect power from wall socket). Swap motherboards, be sure SATA in BIOS is in same mode as on old BIOS (most likely AHCI).

Software to make it bootable (maybe it boots already without issues):
https://www.dropbox.com/sh/ogvkez2hnab1isv/GMh6pwmwcP (my dropbox)
Burn the ISO to DVD on a working machine (can be done prior to motherboard swap)
Read te pdf file. From page 10 is relevant information. Choose "adjust the OS to the new hardware automatically". Boot from the DVD of course to do that.

Now reboot normally and check device manager. Remove old unneeded stuff.

Upgrade the drivers using motherboard CD. Mostly some menu or by running setup.exe

iamjim · 10 Apr 2013

You use the phrase "Upgrade SATA driver in IDE ATA/ATAPI -controllers as well to standard stuf." I'm not sure what the term 'upgrade' means in this context. The way you use it it would be more like downgrade. Do you mean "change?"

I've downloaded the files and scanned the pdf briefly. A disk made from the .iso file boots.

As I read the pdf this thing should be able to do everything. If so, why do I have to remove devices and software before starting the show? If it can do everything I don't run the risk of deleting something I shouldn't.

If the pdf said it could see a flash drive I missed it -- can it?

Since most drivers for the new motherboard are on a disk, I assume I can remove the boot DVD and replace it with the motherboard DVD?

Kaktussoft · 10 Apr 2013

iamjim said:

You use the phrase "Upgrade SATA driver in IDE ATA/ATAPI -controllers as well to standard stuf." I'm not sure what the term 'upgrade' means in this context. The way you use it it would be more like downgrade. Do you mean "change?"

I've downloaded the files and scanned the pdf briefly. A disk made from the .iso file boots.

As I read the pdf this thing should be able to do everything. If so, why do I have to remove devices and software before starting the show? If it can do everything I don't run the risk of deleting something I shouldn't.

If the pdf said it could see a flash drive I missed it -- can it?

Since most drivers for the new motherboard are on a disk, I assume I can remove the boot DVD and replace it with the motherboard DVD?

You can use the procedure you describe as well. But you have to uninstall the software I mentioned earlier as well. They're most likely not working at all. Indeed by saying UPGRADE I mean CHANGE.

Does the motherboard have drivers in logical folders? All drivers have an inf file? Choose "adjust the OS to the new hardware automatically". If some critical drivers are not found point it to DVD with motherboard drivers.

After windows boots fine... check device manager and delete stuff not in machine anymore. Any failures there like question marks? Delete those devices. Run setup or something alike from motherboard dvd.

So indeed the procedure is what you describe. Documentation is quite clear

Since most drivers for the new motherboard are on a disk, I assume I can remove the boot DVD and replace it with the motherboard DVD? =>yes

If the pdf said it could see a flash drive I missed it -- can it?=>yes any usb2.0 port. and most of usb3 ports. esata as well.

churin · 10 Apr 2013

If I attempt to launch sysprep.exe the following is returned. This W7 is a clean install. What could be wrong?

Kari · 10 Apr 2013

churin said:

If I attempt to launch sysprep.exe the following is returned. This W7 is a clean install. What could be wrong?

The only possible reason, if as you say it is a clean install, is that you have done a repair install later on. See my post from yesterday: Windows 7 Installation - Transfer to a New Computer

The same warning is also told at the beginning of this tutorial as quoted here:

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

Kari

churin · 10 Apr 2013

I believe I never run In-Place upgrade to repair W7. I run "Repair" many times after booting to W7 setup DVD. Whatever the reason, it appears that I cannot use sysprep.

I guess there is no way around it.