I’ve been getting the flickering black screen issue that appears to be impacting several users of Workstation (Pro and Player). My first event was in November 2022, but it didn’t start crashing so frequently that the VM became useless until last week. It’s presenting as a crash of DWM.exe (Desktop Window Manager) and/or the guest video driver (SVGA 3D) per the Windows application log, with no corresponding entries on the host’s logs. My host and guest are Win10. The guest is pretty clean and does not have a network adapter, so this couldn’t have been a guest update that caused this.
Windows 10 21H2
3GB Graphics Memory
Here’s a list of posts with the same issue:
Most of these state that issues began around Oct/November 2022
I’ve tried all of the fixes that I could find and it still persists. The most success came from updating to Player 17 since the issue stopped for about 5 hours.
So far I’ve tried:
Updating Player from v.16 to v.17
Uninstalling and reinstalling Workstation Player (v.17)
Running repair on the hypervisor
Updating my host video driver (1080ti)
Messing with resource allocation for the guest
Turning off 3D graphics acceleration
Set to single monitor mode, setting it to a fixed lower resolution
Manually extracted the Vmware guest video driver and installing that (SVGA 3D 8.17.01.001)
Found the “Current Drivers on Windows Update (82290)” page that does list a newer version of WDDM (Windows Display Driver Model) than what I have (https://kb.vmware.com/s/article/82290), the listed driver version is 8.17.02.0014. Page is dated November 2022 (potentially related?).
Checking the Windows Update Catalog, I didn’t see a Win10 driver update for that date.
Found that there’s a newer tools version (188.8.131.5235119), installed and checked the video driver version, it’s now 9.17.04.0002.
Did not fix the issue.
Hopefully Vmware is actually working on this…
I'm having similar issues without any success, starting around the same time frame. The frequency of DWM.exe crashing is inconsistent, but it can by 10+ times a minute at its worst.
Really hoping vmware provides a solution to this problem as its been around far too long now.
I've been researching this and here's what I have found:
1. VMWare Workstation has 2 modes of operation - default and under WHP (Windows Hypervisor Platform)
2. Disabling WHP had an effect of stabilizing my VM and the crashes stopped, but it was only until next reboot. They still ocurred after. WHP allows third-party hypervisors to run off of Windows APIs, at the cost of some guest performance and nested virtualization capabilities. Apparently, this is broken, -OR- (I haven't tested) needs also Hyper-V enabled.
3. I updated to VMWare Tools 12.1.5 - no effect. Updated to latest Windows cumulative update - no effect. Turned off all Aero effects from Advanced System Settings - no effect.
4. I ran
in the guest OS, which found some corrupt files. This by itself did not solve the issue, but I had to try. It's good to fix those before continuing. At this step I downgraded VMWare tools to 12.1.0 again but that also didn't help.
5. I had Virtual Machine Platform - Enabled and HyperV - all disabled in 'Turn Windows features on or off'. VMP allows WSL (Windows Subsystem for Linux) to run... By making the OS run virtually. Therefore, disabling only Windows Hypervisor Platform only would not have worked it seems, as VMWare is running inside a virtual container or conflicting with WSL, in a way, still attempting to use WHP. I may be completely wrong, this is not documented very well.
Why it worked for 1 reboot, I do not know, reboots by themselves did not fix anything, I had tried that too. Maybe it's a bug or omission from the devs that allowed it to run normally once. Disabling VMP too and rebooting today fixed it again. No DWM crashes.
IMO: The application HAS TO give more information on what mode it's working in and what it needs to do so in something like a small checkbox list.
TL;DR: Disable all Hyper-V, Windows Hypervisor Platform, Virtual Machine Platform in 'Turn Windows features on or off'. Reboot. Maybe twice, my machine did twice by itself. Try your VMs now, then drop a reply if that worked for you or not.