It will run into a BSOD (INACCESSIBLE BOOT DEVICE) two times and then the automic repair starts. Select the "old" VMDK file and click "Finish". Choose "SCSI" as disk type and "Use an existing virtual disk". Remove the hard disk (the VMDK-File is not deleted!).So the NVMe driver seems to cause the problem. In the German VMware forum () I got the following workaround which solved the problem for me.Ĭhange the type of the hard disk from NVMe to SCSI. Others say that reducing the number of CPU cores for the VM to 1 helped. Some say that the problem was solved with version 16.2.5 or 17.0.0.
Tips I've read about this so far (including this forum) haven't worked. I also can't imagine that I'm the only one who has this problem. Afterwards just run Windows Update and the reboot ends with BSOD again.īy the way, I don't have this problem with a 64-bit Windows as a guest system. 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. Win 10 Enterprise Evaluation, version 22H2, 32 bit I have now been able to reproduce this on 4 different computers in different constellations. And also the current VMware tools do not change anything. I have also already downloaded the current cumulative update from Microsoft's update catalog and installed "by hand", with the same result. After that the VM starts again normally, but just with patch status September 2022. Afterwards an automatic repair starts and the updates are undone. 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. The subsequent reboot runs normally until the progress is up to 30 %, then the actual reboot of the virtual PC takes place. All updates are downloaded and installed.
The problem is always triggered by the cumulative update and manifests itself as follows. With the October patches, the problem appeared for the first time and has been present ever since. Guest system: Win 10 Pro, version 21H2, 32 BitĮverything worked fine until the September patchday 2022. Host system: Win 10 Enterprise, version 21H2, 64 Bit I think there must be a solution for this.įirst, the problem occurred in the following constellation: 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.
0 kommentar(er)
