Reply to Message

View discussion in a popup

Replying to:
PeterVM100
Contributor
Contributor

BSOD Windows 10 KB5023696 - SYSTEM THREAD EXCEPTION NOT HANDLED

From my experiments (below), I have concluded that the BSOD ONLY HAPPENS when using VMware. Tested v16 & 17.

I have spent countless hours on this issue, does anyone have a solution? Do VMware employees, i.e technicians,  look at these discussion groups?

 

Installing KB5023696 and rebooting Windows I get BSOD, "EXCEPTION THREAD NOT HANDLED"System:
Host Windows 10 22H2 64bit
VM 16 (also tried 17)
Guest Windows 10 22H2 32bit

All experiments were done with a fresh/clean install of Windows 10 (host & guest) downloaded from M$ website
No Windows configuration of any kind in either the host or guest

This has been happening for about a year, started out with Win versions 20H... , 21H... now 22H... - all exactly the same result when trying to update to new Windows 10 versions.


Today, I have tried manually installing 1 update at a time. It is always KB5023696 that causes BSOD upon reboot

When I did a fresh installation of just Windows 10 (tried 32 and 64) with no VM, KB5023696 installed with out incident. Therefore the problem is definitely when trying to apply this update in a VM.

Some of my notes: (none of the suggestions I found on the internet worked)
SYSTEM THREAD EXCEPTION NOT HANDLED
DCOM 1084, comsysApp {182c40f0-32E4-11D0-0DAOc9231C29}
DCOM 1084, ShellHWDetection {DD522ACC...
DCOM 1084, TokenBroker Windows.internal.security.authentication.web.TokenBroker Internal

Normal BootUp
warning Windows.SecurityCenter.SecurityAppBroker
warning Windows.SecurityCenter.SecurityAppID

Solutions Tried:
1. Delete Software Distribution, windows catalogue - no actionable results
2. Command - no actionable results
    a. sfc /scannow
    b. dism /online /cleanup-image /checkhealth | /scanhealth | restorehealth

3. DCOM services necessary - ensured running
    a. Dcom Service Process Launcher
    b. Background Task Infrastructure Service
    c. Local Session Manager
    d. Remote Call Procedure

4. Safe Mode - Troubleshooter (see additional troubleshooters) - no actionable results

Reply
0 Kudos