Forum Discussion
Baltazarus
Aug 06, 2021Copper Contributor
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 ...
schm1dt
Aug 09, 2021Copper Contributor
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.
Shabbar
Aug 12, 2021Copper Contributor
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
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
- schm1dtAug 12, 2021Copper ContributorYeah 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)
- KazuiKurosakiAug 12, 2021Copper ContributorDid 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?