Windows 10: Windows 11 CRITICAL_PROCESS_DIED no code Loops on Diagnose PC, after Windows update

Hi All, I had a Windows 11 23F2 update, on completion I found that my CCTV application did not work correctly, so I invoked a restore from the week previous. On reboot, the desktop was blank, I closed down and since received the CRITICAL_PROCESS_DIED error, and doesn't collect error info past 0%. Even using a Windows created bootUSB, the tools do not see the SSD, even if I invoked another build, the installation fails as it does not detect the SSD Windows encrypted partition. Running Command only sees the X drive, any commands pointing to the Windows C drive fails, Bitlocker does not invoke at

:)

 

Critical_Process_Died BSOD

Hi,

In order to resolve your concern, we suggest that you to follow these steps:

• If you've installed any new apps or devices, uninstall or unplug them and restart your PC.
• Make sure your PC has the latest updates:

• Go to the search box.
• Type Windows Update then Enter.
• Select Check for updates.
• In the Settings menu, select Check for updates button.
• When it's finished, restart your PC.

You may also check this
link for more troubleshooting steps regarding critical_process_died error message.

Let us know how it goes.

 

Win10: windows update stuck at never ending loop ?

When in win10:

• Update&security -> Windows update -> Finding update... .... .... ....

Planning to download the latest Win10.ISO (vers.1803) and manually update:
- Then wait that my ordered new SSD arrives and clone the old HDD to it.

 

Windows 10 stuck in "CRITICAL_PROCESS_DIED" loop after update.

Several weeks ago, windows restarted my computer after installing some automatic updates. Upon rebooting, my computer flashed a BSOD message "CRITICAL_PROCESS_DIED". Nothing seemed to fix this upon successive reboots, but windows eventually
prompted me to rollback to a previous state.

This removed the "CRITIAL_PROCESS_DIED" error, but windows keeps trying to reschedule this update. Successive updates lead to the same "CRITICAL_PROCESS_DIED" BSOD. So, I am stuck in a continual loop where I am being forced to update,
then roll back, over and over.

After an hour in the loop, I finally made it to advanced startup and loaded 2 recovery store points back (current recovery point kept uninstalling and reinstalling the offending updates). One of the following of these has to be causing
this loop:

• Adobe Flash Player update (version 1511- KB3201860)
• Microsoft Word 2010 update (KB3118312)
• Windows Malicious Software Removal Tool (KB890830)
• Microsoft Silverlight (KB3193713)
• Cumulative Windows update (KB3192441)

My computer used to be 100% stable, but has recently been BSOD before I can even boot to the log in screen.

I think I may have narrowed down the problem to KB3192441 (Cumulative WIndows Update), but I am not certain.

Are there any log files/steps I can take to fix my machine? This is becoming a huge pain. I am worried my restore point will eventually be lost and my machine will be bricked until I can reinstall windows.

BTW, I ran sfc /scannow and it finished before BSOD'ed. Results:

2016-11-02 19:49:31, Info CSI 000057f8 [SR] Verify complete

2016-11-02 19:49:31, Info CSI 000057f9 [SR] Repairing 1 components

2016-11-02 19:49:31, Info CSI 000057fa [SR] Beginning Verify and Repair transaction

2016-11-02 19:49:31, Info CSI 000057fb [SR] Repairing corrupted file [l:36 ml:37]"\??\C:\WINDOWS\Provisioning\Packages"\[l:41]"Power.EnergyEstimationEngine.Control.ppkg" from store

2016-11-02 19:49:31, Info CSI 000057fc@2016/11/3:02:49:31.148 Primitive installers committed for repair

2016-11-02 19:49:31, Info CSI 000057fd [SR] Repair complete

2016-11-02 19:49:31, Info CSI 000057fe [SR] Committing transaction

2016-11-02 19:49:31, Info CSI 000057ff Creating NT transaction (seq 2), objectname [6]"(null)"

2016-11-02 19:49:31, Info CSI 00005800 Created NT transaction (seq 2) result 0x00000000, handle @0x41c

2016-11-02 19:49:31, Info CSI 00005801@2016/11/3:02:49:31.163 Beginning NT transaction commit...

2016-11-02 19:49:31, Info CSI 00005802@2016/11/3:02:49:31.169 CSI perf trace: