Windows 10 20H2 CRITICAL_PROCESS_DIED


  1. Posts : 5
    Win10, WinXP, Debian
       #1

    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
    Windows 10 20H2 CRITICAL_PROCESS_DIED Attached Files
      My Computer


  2. Posts : 1,244
    Windows 10 Pro x64 21H2 (Build: 19044.1415)
       #2

    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
      My Computer


  3. Posts : 5
    Win10, WinXP, Debian
    Thread Starter
       #3

    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?
      My Computer


  4. Posts : 1,244
    Windows 10 Pro x64 21H2 (Build: 19044.1415)
       #4

    Easiest way for you is to create bootable Windows 10 USB and use it to repair bad OS.

    Once you boot into installation setup, before clicking on "Install now" button, choose option "Repair my computer", this should make your original OS boot again.

    More information how to create bootable Windows 10 USB:
    https://www.microsoft.com/en-us/soft...load/windows10
      My Computer


  5. Posts : 5
    Win10, WinXP, Debian
    Thread Starter
       #5

    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.
      My Computer


  6. Posts : 1,244
    Windows 10 Pro x64 21H2 (Build: 19044.1415)
       #6

    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"
      My Computer


  7. Posts : 5
    Win10, WinXP, Debian
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 1,244
    Windows 10 Pro x64 21H2 (Build: 19044.1415)
       #8

    If you have nothing on that computer that you care about then it's easier to just reinstall Windows.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:53.
Find Us




Windows 10 Forums