Windows 10 20H2 CRITICAL_PROCESS_DIED  

Hello,

first off, I've gone through all posts related to my issue and nothing would lead to success.

So, a few days ago I upgraded from Win7 to Win10 20H2 and apparently commited a huge mistake by throwing O&O ShutUp 10 on the "fresh" install. I selected various recommended settings to prevent Windows from leaking too much data. After a restart suddenly the keyboard stopped working. 2 reboots later the OS stopped working entirely and since then I'm stuck in said CRITICAL_PROCESS_DIED bootloop. I tried safe mode, debug mode and whatnot mode, anything in that list, all options lead to the same bluescreen.

In command line of course I tried to run sfc /scannow, of course without any success (Windows resource protection could not start the repair service). So I progressed to various commands using dism.exe:

- mounted Windows image (install.wim)
- dism /image:F:\ /cleanup-image /restorehealth /source:\mount\windows /LimitAccess

Surprisingly it returns an error message and just won't do anything.

Chkdsk is the only utility that works as intended, even fixes some errors but it has zero effect on Windows boot.

I attached two logfiles which could be useful. It seems that Win10 stumbles upon Hamachi drivers which cause some kind of trouble. However, I have no idea how to deal with that issue and I'm running out of ideas after 3 days of finding a solution.

What am I doing wrong? Any ideas?

Thanks in advance

zebal said:

Your DISM command is not valid because you need to specify /Online parameter to work on running Windows

Code:

DISM OS Provider: PID=1408 TID=1444 "Failed to query the value SystemRoot."

Try with:

Code:

Dism /Online /Cleanup-Image /RestoreHealth /Source:D:\mount\windows /LimitAccess

and share fresh log

/online function is not available in WinPE environment. Regular Win10 won't fire up so I have to stick with WinPE and retricted possibilities.

Any other way to make it work?

You mean the text in lower left corner? I tried all options being offered in that menu, including removing updates. System restore doesn't work and just throws me back to the menu.

Only thing that appears to work is the command prompt, all other options fail with error messages. That's the frustrating part and I have no idea how to modify files from there that interrupt the boot process. Regedit and notepad are accessible from there of course but I don't know in what way it could be useful.

zebal said:

Yes, after you boot from USB into installation setup (not into recovery environment of current Windows)
There after you choose "Repair my computer" select "Startup repair"

Still nothing. It starts doing some diagnostics and then tells me it was unable to repair the system. Quite the same as in WinPE on hard disk.

Maybe it's a naive thought but is there a chance to exclude that malicious driver from somewhere in order to normalize the boot process? Don't know what else to do

Thanks for your patience and assistance so far.