- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is definitely triggered by a change coming from Microsoft in KB5019959.
I'm running Ubuntu 18.04 as the host VMWare Workstation Pro 15.5.7 and all my 64-bit Windows 10 VM's have applied KB5019959 just fine - no problem.
Its only my 32-bit Windows 10 VM's that are BSOD with SYSTEM THREAD EXCEPTION NOT HANDLED.
Unfortunately I can't upgrade to v16 or v17 of VMWare due to this issue here which VMWare has ignore for almost a year.
My system dual boots and even when I run Windows 10 x64 as the Host the 32-bit Guests still BSOD on KB5019959.
I really don't think VMWare reads any of these boards anymore ![]()