Forum Discussion
PROCESS1_INITIALIZATION_FAILED (Windows 11 Upgrade 10.0.22000.120) after reboot.
Ok, so I was enjoying the Windows 11 until I installed 10.0.22000.120 Upgrade. After that one upgrade, this turned into a horrible nightmare. My pc booted up and after loading circle screen passed, I ...
By any chance, has anyone here tried using BCDBoot to repair their boot entries? I suspect that they are what's causing these shenanigans, especially regarding the Windows Rollback entry, which from what I've seen points to the wrong path for it's WinRE image.
- I already did that and it did not help
the only workaround is to replaced the winre.wim with the one from previous build
and copy to "C:\windows\system32\recovery\
and use the command line in elevated prompt command
reagentc /disable
reagentc /setreimage /path C:\windows\system32\recovery\
reagentc /enable- Yeah that can work for now, it's caused by MS integrating a broken KB update into WinRE on direct upgrades to .120, although I'd personally suggest putting the old WinRE.wim image into your actual recovery partition for the sake of making it a little cleaner (should be able to do this via windows install media)
- Did this work "the only workaround is to replaced the winre.wim with the one from previous build
and copy to "C:\windows\system32\recovery\
and use the command line in elevated prompt command
reagentc /disable
reagentc /setreimage /path C:\windows\system32\recovery\
reagentc /enable"
work for you?
- Could you explain where you see the wrong path to WinRE image ?
I can easily reproduce the bug, if you have a way to fix it, please share and I can try.
For now I worked around the problem by updating to 22000.100 first and then in a second step let W.U. go to 22000.120. With the 2 step update I don't see the bug at all.- If you do "bcdedit /enum all" in an admin command prompt on a system that has the BSOD issue, specifically when rolling back to Windows 10 in my case, then look for the Windows Rollback BCD entry, you'll notice that it looks for the WinRE.wim image inside C:\$WINDOWS.~BT, however, that folder will end up actually being found in windows.old. Regarding the upgrade issue, the BCD entry and folders used for that likely will be different, in that case just find one labelled along the lines of 'Windows 11' or 'Windows Setup', check what folder the 'device' and 'osdevice' entries try to access, and check where it's located to see if the actual location matches with the location that the BCD entry is checking for.
Regarding the rollback issue in particular, that occurs on systems successfully upgraded to 22000.120 directly which attempt to go back to win10(leading to the process1 BSOD). In that case, you could try copying the BT folder over to the root C drive, ensuring that 2 copies are present in both C and C:\Windows.old, and then attempt the rollback and see if that works, or you could try using bcdboot to rebuild the BCD manually. For the upgrade issue, I'm not too sure on that since I haven't encountered it myself.
