Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error  

Please post the results from these commands:

bcdedit | find "osdevice"

e:
dir

verifier /?

X:
x:\sources>

reg load hklm\temp E:\windows\system32\config\system

I typed the commands in your last post last night (copied to note #2) and then the above post (see note #1) and attached the copies from cmd window.

After this, I turned off the computer and then turned on. It went to the windows logo and then to black where it stayed, but did not give a BSOD. But when I re-started it, it did crash with the same driver error.

The steps to load the registry displayed:
X:\Windows\System32>reg load hklm\temp E:\windows\system32\config\system
The operation completed successfully.

Were you able to either run the query commands and / or turn off windows driver verifier?

Was regback run after loading the registry?

See if you can complete the steps in the link using the registry to turn off windows driver verifier.

Ok, I went thru it again and this time I was able to get to X:\Sources and load the registry into Tempsys exactly the way it says on that other post you linked. I found registry entries for Verifier, and deleted them. I actually found them in two ControlSets, I deleted them...unloaded the Tempsys, exited, restart...and again, it went past the windows logo screen and just went black. I have mouse control but nothing happens. I do not hear the hard drive working or see the activity light so I think its just sitting in black.

So I rebooted twice - once into safe mode where it froze in black & mouse froze too, and then back into normal windows where its black.

So...the result is no more BSODs, but windows is not fully loading after the logo screen.

Open the windows RE > startup repair > see if it generates a srttrail.txt > post a share link

Copy e:/windows/system32/logfiles/srt/srttrail.txt X:

Replace X: with drive letter assign to USB Flash Drive.


If you boot and see black > click these 4 keys simultaneously: win + shift + ctrl + b > report into the thread what you see and hear


See if you can boot into safe mode using the hardware method: (no attached drives)
a) power on > as soon as you see the Microsoft icon > power off
b) immediately repeat: power on > as soon as you see the Microsoft icon > power off
c) power on and see if it advances to the computers windows advanced troubleshooting menu

Plan to restore the image.

Those did not work. Startup repair generated an error window with:
Problem Event Name: Startuprepair offline
Problem signature 1 6.1.7600.16385
Problem signature 2 6.1.7600.16385
Problem signature 3 unknown
Problem signature 4 540
problem signature 5 Auto Failover
problem signature 6 1
Problem signature 7 no root cause

As for the image, its located on drive D: but its a Macrium file extension. I created a "recovery cd" like they recommended on that post but all it does is boot into a gray screen with a command prompt. So how would I run the image file? I checked it after I made it by mounting it as a drive and it mounted properly with looks like everything in there. So I just don't know how to work with it outside of Windows.

At this point its probably better to do a clean install of Windows 10. I'd still be able to install Macrim on it and mount the image as a drive to grab anything off of it, right? And to activate win10, I installed it & then rolled back to 7 during the free period in 2016 so then it should come up as activated even after a clean install, right? If not I would just enter the Windows 7 key?

Another thing I noticed is that all this messing around in cmd had shifted my drive letters again. Now the drive that I need to keep safe is letter C:! D: is showing as the 100mb system reserve; Windows 7 is installed in E:. I need to reset that. But I don't think it'll let me rename D because I think the reserve is where cmd is running from. I definitely can't let windows 10 install on C like it should or I'll lose everything.

Windows automatically assigns new letters while in Windows RE.
Commands are run in Windows RE to determine the applicable drive letter while in Windows RE.
Drive letter assignment in Windows should be the same when returning to Windows from Windows RE.

Few things work 100% of the time.
Unexpected things often happen so it's always best to create backup options.