While using windows 10 within VM Fusion 12 on Big Sur, screen goes black for a few seconds then will come back with a few flashes. Sometimes requires some input in order to prompt this. Almost like it has to redraw the screen. Sometimes occurs in close succession sometimes can be quite a while. When happening in close succession it becomes unusable. This was created to seperate out my problem from that of the “flickering” problem also mentioned in this forum. This problem does exhibit a flickering as it redraws from black and could be considered a flicker but realised the issue mentioned elsewhere is a constant monitor flicker rather than a flicker while redrawing. Not sure redrawing is what it is doing but not sure how else to describe it. I’ve seen this sort of thing occur when there is a memory leak but I have not confirmed that is the case.
I can also open a new ticked but I think this discussion would have been lost... and in this thread there are already a lot of important hints!
Hi,
re. AMD driver fix in Monterey.
The details about that are here:
https://communities.vmware.com/t5/VMware-Fusion-Discussions/VmWare-Fusion-crash-when-using-Altium-de...
But you are already using the latest driver in macOS Big Sur 11.5.2, so it is not that.
re. opening a ticket. You can mention this thread in the ticket, that's a common thing to do.
--
Wil
Maybe I'm doing something wrong... I'm not able to open a ticket on FUSION.... See enclosed png file!
Can you help
Hi,
I don't work for VMware... I only try to help out in my free time.
Looks like that your VMware Fusion license is not registered in the my.vmware.com portal?
goto: https://my.vmware.com/ then login -> Products and accounts -> product registration
You can add your license there.
Under "Manage licenses" in the box under the menu.. you should see your license.
If the license is already there, then you might not have support anymore as it is limited in time unless you buy extra support.
--
Wil
Solved by running the following command on the command prompt (as administrator) of the Windows guest:
bcdedit /set useplatformclock true
Solved it for me too
Thank you so much. I can confirm this resolves the screen hiccup issue on Windows 10 guests.
How did you figure this out? Tried debugging this for weeks and tried every suggestion (except for ditching fusion).
Would like to know what lead to the solution in terms of troubleshooting... Was there a log entry or something that clued you onto this fix?
"bcdedit /set useplatformclock true"
It's been a while since a use my virtual machines with this black screen flickering and I tried a lot of solutions without solving the problem. Those last weeks, I had this flickering screen every 5 secondes while I was using my virtual machines and it was really a pain using them.. I was even considering going to parallel desktop !
I tried the above solution one hour ago and I didn't had any black screen even using intensively one of my virtual machines...
bcdedit /set useplatformclock true
Will see on next few days how things are going but for now I'm pretty happy ![]()
Tried this setting on a new W11 guest VM under OSX 12.1 host. After re-starting the VM (important step!) the crashes have stopped. They used to occur every 15 seconds or so, and so far all is good. Will update this post if problem returns
Thank you, thank you, Thank you for sharing this fix!
I just installed a brand new Windows 11 VM and painstakingly migrated over from my windows 7 machine, 8 years of work files and set-up (keyboard shortcuts, autohotkey set up, outlook custom dictionaries and more blah blah blah. I thought i had it all done and then started to have this black screen DWM Desktop Windows Manager Appcrash issue. After so much searching i found this solution and so far not one recurrence of the problem. Bravo @SolverUser
bcdedit /set useplatformclock true
Thank you very much! I am using VMware Workstation Pro version 16.2.4 and the fix works like a charm.
Re:
bcdedit /set useplatformclock true
If you're using Windows 11, you might want to also try the Tech Preview, since that has better Win 11 support (on intel hosts).
After all the settings I had changed this was the one that solved it. Wow, thank you!
