Transfer programs from Windows 7 to new Windows install

[SIW2]

Yes, I imagine that would fix it.

Worked it out due to an issue with PAR and win 7 - sometimes win7 will start preparing comp for first use after every reboot.

Only sometimes - and only with win7.

Have you come across that with PAR and 7?

 

[RFHarris]

Win 7 problem it seems.

Shame you couldn't pin it down after a valiant effort.

Glad you managed to get your app. registry settings across fine.

I had a possibly related issue just now.

Out of interest, I created an install.wim from the recovery partition on an oem machine.

Then installed it on mine.

Was able to get to the desktop ok , but sysprep popped up every reboot.

Fixed it with this

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"SetupType"=dword:00000000
"SystemSetupInProgress"=dword:00000000
"SetupPhase"=dword:00000000
"CmdLine"=""
"OOBEInProgress"=dword:00000000

I suppose that is what you did offline.

Yes that is what I did or tried to do, from a stored registry here is what it looks like on my machine on the failing drive:

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"OsLoaderPath"="\\"
"RestartSetup"=dword:00000000
"SetupType"=dword:00000002
"SystemPartition"="\\Device\\HarddiskVolume1"
"SystemSetupInProgress"=dword:00000001
"SetupPhase"=dword:00000004
"CmdLine"="oobe\\windeploy.exe"
"OOBEInProgress"=dword:00000001
"WorkingDirectory"="C:\\Windows\\Panther"
"CloneTag"=hex(7):4d,00,6f,00,6e,00,20,00,4d,00,61,00,79,00,20,00,30,00,39,00,\
20,00,31,00,36,00,3a,00,33,00,33,00,3a,00,33,00,33,00,20,00,32,00,30,00,31,\
00,31,00,00,00,00,00
"SetupShutdownRequired"=dword:00000001

I found a vague reference on the Internet that in the %windir% (which I assume expands to point to the Windows directory) files somewhere there is another reference to OOBE at startup that should be adjusted but I don't know where it is. I still have the drive with the start up problem to test solutions.

 

[RFHarris]

Only way I know to run PAR is from its CD, choosing "Adjust OS" to remove all drivers, hardware ID and activation. Was that tried?

It always works to start Win7 which hasn't been corrupted already by SysPrep failure - which is the reason I mentioned it, since I have seen that failure.

Greg,

It seems to run the same way whether from the CD or from Paragon Software, running from the installed software is a little easier. I have installed the Paragon Backup and Recovery suite which I haven't used for backup yet but hope it does better than Acronis and supports backing across on my network. But here are the steps I have taken:

Open Paragon software and choose P2P Adjust OS option
The software correctly identifies the OS on the failing drive to adjust, I confirm that.
From the options I choose "Update Drivers Automatically etc", (Recommended)
I insert the MB CD and navigate to the chipset inf folder
Software responds with a processing bar indicating the CD drivers are being processed.
When finished I select Yes Apply Changes Physically, system responds with a scrolled list of changes and "Successfully Completed P2P Adjust Wizard"
Booted from the failing drive and same problem, - shift F10 and examine the registry and it still has same settings in setup key.

 

[SIW2]

Here is how it looked originally on mine:

[HKEY_LOCAL_MACHINE\PE_SYS\Setup]
"OsLoaderPath"="\\"
"RestartSetup"=dword:00000000
"SetupType"=dword:00000002
"SystemPartition"="\\Device\\HarddiskVolume1"
"SystemSetupInProgress"=dword:00000000
"CmdLine"="C:\\Windows\\system32\\oobe\\windeploy.exe"
"SetupPhase"=dword:00000004
"OOBEInProgress"=dword:00000001

"WorkingDirectory"="C:\\Windows\\Panther"
"CloneTag"=hex(7):54,00,68,00,75,00,20,00,41,00,70,00,72,00,20,00,31,00,36,00,\
20,00,31,00,39,00,3a,00,33,00,36,00,3a,00,30,00,30,00,20,00,32,00,30,00,30,\
00,39,00,00,00,00,00
"SetupConfigSetRoot"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
00,6f,00,74,00,25,00,5c,00,43,00,6f,00,6e,00,66,00,69,00,67,00,53,00,65,00,\
74,00,52,00,6f,00,6f,00,74,00,00,00

This is what I changed it to :

[HKEY_LOCAL_MACHINE\PE_SYS\Setup]
"OsLoaderPath"="\\"
"RestartSetup"=dword:00000000
"SetupType"=dword:00000000
"SystemPartition"="\\Device\\HarddiskVolume1"
"SystemSetupInProgress"=dword:00000000
"CmdLine"=""
"SetupPhase"=dword:00000000
"OOBEInProgress"=dword:00000000

"WorkingDirectory"="C:\\Windows\\Panther"
"CloneTag"=hex(7):54,00,68,00,75,00,20,00,41,00,70,00,72,00,20,00,31,00,36,00,\
20,00,31,00,39,00,3a,00,33,00,36,00,3a,00,30,00,30,00,20,00,32,00,30,00,30,\
00,39,00,00,00,00,00
"SetupConfigSetRoot"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
00,6f,00,74,00,25,00,5c,00,43,00,6f,00,6e,00,66,00,69,00,67,00,53,00,65,00,\
74,00,52,00,6f,00,6f,00,74,00,00,00


I didn't have this:

"SetupShutdownRequired"=dword:00000001

Not sure how windeploy is continuing to run if you removed it from cmdline entry.

I also renamed the Panther directory to OLD-Panther.

In the Panther directory is the autounattend.xml - amongst other things.

What is in your Panther directory ?

You might also look in Windows\Setup folder

Was fine on next reboot

(PE_SYS is just the name I loaded the hives as )

 

[RFHarris]

Here is how it looked originally on mine:

[HKEY_LOCAL_MACHINE\PE_SYS\Setup]
"OsLoaderPath"="\\"
"RestartSetup"=dword:00000000
"SetupType"=dword:00000002
"SystemPartition"="\\Device\\HarddiskVolume1"
"SystemSetupInProgress"=dword:00000000
"CmdLine"="C:\\Windows\\system32\\oobe\\windeploy.exe"
"SetupPhase"=dword:00000004
"OOBEInProgress"=dword:00000001

"WorkingDirectory"="C:\\Windows\\Panther"
"CloneTag"=hex(7):54,00,68,00,75,00,20,00,41,00,70,00,72,00,20,00,31,00,36,00,\
20,00,31,00,39,00,3a,00,33,00,36,00,3a,00,30,00,30,00,20,00,32,00,30,00,30,\
00,39,00,00,00,00,00
"SetupConfigSetRoot"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
00,6f,00,74,00,25,00,5c,00,43,00,6f,00,6e,00,66,00,69,00,67,00,53,00,65,00,\
74,00,52,00,6f,00,6f,00,74,00,00,00

This is what I changed it to :

[HKEY_LOCAL_MACHINE\PE_SYS\Setup]
"OsLoaderPath"="\\"
"RestartSetup"=dword:00000000
"SetupType"=dword:00000000
"SystemPartition"="\\Device\\HarddiskVolume1"
"SystemSetupInProgress"=dword:00000000
"CmdLine"=""
"SetupPhase"=dword:00000000
"OOBEInProgress"=dword:00000000

"WorkingDirectory"="C:\\Windows\\Panther"
"CloneTag"=hex(7):54,00,68,00,75,00,20,00,41,00,70,00,72,00,20,00,31,00,36,00,\
20,00,31,00,39,00,3a,00,33,00,36,00,3a,00,30,00,30,00,20,00,32,00,30,00,30,\
00,39,00,00,00,00,00
"SetupConfigSetRoot"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
00,6f,00,74,00,25,00,5c,00,43,00,6f,00,6e,00,66,00,69,00,67,00,53,00,65,00,\
74,00,52,00,6f,00,6f,00,74,00,00,00


I didn't have this:

"SetupShutdownRequired"=dword:00000001

Not sure how windeploy is continuing to run if you removed it from cmdline entry.

I also renamed the Panther directory to OLD-Panther.

In the Panther directory is the autounattend.xml - amongst other things.

What is in your Panther directory ?

You might also look in Windows\Setup folder

Was fine on next reboot

(PE_SYS is just the name I loaded the hives as )

I thought I had made all those changes, but maybe not. Anyhow I copied and printed your example and went back and carefully made every change and Voila! the system booted and after a long pause it started Windows and I got a message that Windows needed to restart to apply changes, it rebooted and started up fine. Have not run it through its paces yet but pretty sure it will be OK. I really appreciate all the help I have gotten.

BTW I have never been involved in PC or WAN support so I have not seen the problems and combinations that many on this board have. I do have a deeply technical background (what I remember of it) starting as a digital engineer for a computer manufacturer (not IBM) and also worked on technical and diagnostic software before leaving for a large corporation where I went through application software development and various levels of IT management before going into corporate management. On a personal level I always enjoyed PCs and starting in the late 70s early 80s I would assemble components on a bread board and burn programs into an EEPROM. So very much easier today to build a PC but so much harder to keep up with the software! I left the IT field in the later part of the 90s.

 

[SIW2]

Hey RF,

That is great news.

BTW - I have no idea what I am doing - I just guess.

 

[gregrocker]

SIW2, do you think it was SysPrep's failure that created the problem with PAR working correctly here, or another corruption?

Watch optional Windows Update for newer drivers. Unlike XP, Win7 drivers are automated with most in the installer and newer quickly arriving via optional Updates, especially when you enable hardware auto-updating: Automatically get recommended drivers and updates for your hardware

MS spent a fortune getting Win7 drivers into the installer or quickly via Updates, even paying manufacturers under WHQL to build them so they wouldn't hold out to force us to buy newer hardware as they did with Vista.