TSL02 Tracker

Re: BSOD Windows 10 KB5023696 - SYSTEM THREAD EXCEPTION NOT HANDLED

TSL02 — Thu, 20 Apr 2023 16:03:26 GMT

@PeterVM100: Did you try this solution: https://communities.vmware.com/t5/VMware-Workstation-Player/Problem-with-guest-system-Win-10-32-Bit/m-p/2962225 ?

That solved the problem for me and due to your description I think there is a good chance for you too.

Re: Problem with guest system Win 10 32 Bit

TSL02 — Tue, 18 Apr 2023 09:58:34 GMT

In the German VMware forum (vmware-forum.de) I got the following workaround which solved the problem for me.

Change the type of the hard disk from NVMe to SCSI. So the NVMe driver seems to cause the problem.

Step-by-step:

Power down the VM.
Backup the VM.
Edit VM settings.
Remove the hard disk (the VMDK-File is not deleted!).
Add a new hard disk. Choose "SCSI" as disk type and "Use an existing virtual disk". Select the "old" VMDK file and click "Finish".
Power on the VM. It will run into a BSOD (INACCESSIBLE BOOT DEVICE) two times and then the automic repair starts.
(I only have German Win10, so maybe my English translations of the following options do not have the same wording as used by Microsoft.) After some time you can choose between "Restart" and "Enhanced options". Select "Enhanced options", then "Trouble shooting" and again "Enhanecd options", then "Start-up aid" (the first selection option in the upper left corner). Again after some time it says that it can't repair your PC. But, if you choose "Shut down" and power on the VM again, it will start normally.
After that I could install all Windows updates without any problems.

Problem with guest system Win 10 32 Bit

TSL02 — Mon, 03 Apr 2023 11:12:23 GMT

Dear Community,

I am really getting desperate. For some time now, I have had the problem that guest systems with Windows 10, 32 bit (and only 32 bit!) crash when running Windows updates. I think there must be a solution for this.

First, the problem occurred in the following constellation:
Host system: Win 10 Enterprise, version 21H2, 64 Bit
Guest system: Win 10 Pro, version 21H2, 32 Bit
VMware Workstation Player 16.2.4

Everything worked fine until the September patchday 2022. With the October patches, the problem appeared for the first time and has been present ever since. The problem is always triggered by the cumulative update and manifests itself as follows. All updates are downloaded and installed. The subsequent reboot runs normally until the progress is up to 30 %, then the actual reboot of the virtual PC takes place. The light blue Windows 10 logo appears briefly and is followed by a BSOD ("SYSTEM THREAD EXCEPTION NOT HANDLED"), then a second reboot again with the same BSOD. Afterwards an automatic repair starts and the updates are undone. After that the VM starts again normally, but just with patch status September 2022. I have also already downloaded the current cumulative update from Microsoft's update catalog and installed "by hand", with the same result. And also the current VMware tools do not change anything.

I have now been able to reproduce this on 4 different computers in different constellations.

Tested host systems:
Win 10 Enterprise, Version 21H2, 64 Bit
Win 10 Enterprise, Version 22H2, 64 Bit
Win 10 Pro, version 21H2, 64 bit
Win 10 Pro, version 22H2, 64 bit

Tested guest systems:
Win 10 Pro, version 21H2, 32 bit
Win 10 Pro, version 22H2, 32 bit
Win 10 Enterprise Evaluation, version 22H2, 32 bit

Tested Vmware Workstation versions:
Player 16.2.4
Player 16.2.5
Player 17.0.0
Player 17.0.1
Pro 17.0.1 (30-day trial)

I just tried again a few days ago. Created a new VM with the current Workstation Pro 17.0.1, installed Win 10 Enterprise Evaluation, version 22H2, 32 bit in it with the ISO currently available from Microsoft (the ISO has the September 2022 patch level), with no other software installations or settings changes. Afterwards just run Windows Update and the reboot ends with BSOD again.

By the way, I don't have this problem with a 64-bit Windows as a guest system. I also can't imagine that I'm the only one who has this problem. Tips I've read about this so far (including this forum) haven't worked. Some say that the problem was solved with version 16.2.5 or 17.0.0. Others say that reducing the number of CPU cores for the VM to 1 helped. For me this does not change anything.

Does anyone have an idea or solution?

Re: Windows Updates Failed - noob to VM Ware (currently a VBox user)

TSL02 — Mon, 21 Nov 2022 10:31:36 GMT

It was available yesterday afternoon (in Germany) too.

Re: Windows Updates Failed - noob to VM Ware (currently a VBox user)

TSL02 — Mon, 21 Nov 2022 09:04:12 GMT

As I write in my original post, I experience this problem only with 32-Bit-Win10Pro. Another VM with 64-Bit-Win10Pro doesn't show this issue.

Re: Windows Updates Failed - noob to VM Ware (currently a VBox user)

TSL02 — Mon, 21 Nov 2022 09:00:40 GMT

I can't confirm that for Workstation Player 17.

I've tested that yesterday. I installed the brand new version 17 of Workstation Player. Then I created a new VM and installed 32-Bit-Win10Pro 22H2 using the most recent ISO from Microsoft. That results in build 19045.2006 (including September patches). After applying the November patches, Win10 crashes during reboot.

Re: Windows Updates Failed - noob to VM Ware (currently a VBox user)

TSL02 — Sun, 20 Nov 2022 20:43:04 GMT

Seems that I encounter the same problem.

Host systems: Windows 10 Pro and Enterprise 21H2 and 22H2

Guest system: 32-Bit-Version!!! of Windows 10 Pro 21H2 and 22H2

I have this problem since the october patches of Win10. Every time I try to install these patches or the november patches in the guest system, Win 10 crashes during reboot and then "repairs" itself. The behaviour is the same on different machines, even with a new VM built from scratch, but only with the 32-Bit-Version of Win 10. A 64-Bit Win 10 (Enterprise) in another VM is running without any difficulties. Unfortunately, the current Win-10-ISO from Microsoft includes only the spemtember patches. Due to that it is not possible to built a new Win-10-VM with october/november patches included.

Edit: Same behaviour with Worstation 16.2.4 and Workstation 17.0.0