Screen updating issues after updating from 17.0 to 17.6.3

[wtstephens]

This is an issue for Windows 10 and Windows 2000 (yikes!) virtual machines (on my Windows 11 host).

For instance, I scroll some text in Visual Studio Code and it looks like this:

And a few seconds later (maybe 5 or 10 seconds even), it updates to the correct display:

Did I miss doing something during the upgrade to 17.6.3? 

I updated the VMWare Tools in each VM -- is there anything else to do?

Thanks for any help!

Warren

[Jose Fonseca]

We've been doing improvements on 3D acceleration support on Workstation for Windows.  It's possible there's a regression somewhere.

For starter, please provide us the vmware.log and mksSandbox.log corresponding to a run where this issue happens, so we understand the GPU HW and SW used here.

[Jose Fonseca]

Also, please double check you have the latest GPU drivers installed.

[wtstephens]

Thanks for the response!

My Windows 11 host NVidia GPU drivers are from 2023-02-18 (version 527.27) -- the latest are obviously about 2 years newer.

How likely is the host driver the issue?

[Jose Fonseca]

On 2nd look, the issue looks like one we reproed internally and are working on.

Still, we recommend using the latest GPU drivers (or latest stable drivers when available.)  Those are the ones we test regularly against.

[Shibdas Bandyopadhyay]

This looks like something we are looking at right now. Can you please try with this config option mks.enableDX12Presentation=FALSE and check if that is better. Please attach the vmware.log and mksSandbox.log too when you try it out, thanks!

[Proud2BProud]

None of this works.  Updating all drivers does not work.  mks.enableDX12Presentation=FALSE does not work.  Been working with Broadcom support for a month and nothing they do works.  Good luck.

[dalewood]

I had been experiencing a similar issue with graphics being 'messed up'. It shows up as a "patch" of the virtual screen with small pixilated blocks. This area will usually self correct after several seconds but was extremely annoying.

I applied (note I added quotes) and saw an immediate elimination of the pixilated blocks:

  mks.enableDX12Presentation = "FALSE" 

There did not appear to be a rhyme or reason to when the pixilated blocks would appear, but it seemed worse when the windows 10 host was verifying a RAID 10 SATA (4 SATA SSD drives).

At least so far, thank you for posting 1) this is being actively looked into, and 2) the config option.

[Proud2BProud]

I have solved my Mouse response, Keyboard response, Graphics response Issues with Win11 Host and Win10 Guests using VMWarePro v17.6.3.

Solution = DISABLE the Accelerate 3D Graphics option for the Display

[Shibdas Bandyopadhyay]

I was about to reply to you to turn off 3d to check if the slowness you are seeing is from the graphics side. In general there can be a multitude of problems causing the slowness. For your case, it indeed seems the like 3d was causing the issue.

If you want to have a similar graphics behavior as of 17.5.2, please try with following config options (and keep the 3d on)

mks.enableDX12Presentation=FALSE

mks.enableVulkanRenderer=FALSE

Also please attach vmware.log and mksSandbox.log

[Proud2BProud]

This did not work.

Only working option is to disable as I have indicated.

I will not troubleshoot any further because spent 40hrs already and have no patience now.

Attachment has logs and vmx

I am done - thanks

[wtstephens]

That fixed it!  Thanks! 

Adding this line to my preferences.ini file did solve the screen update problem -- I did restart VMWare Workstation (but did not have to reboot either VM, they had been paused).

mks.enableDX12Presentation = "FALSE"

I did not have to update the video drivers.

[jack bayt]

THANK YOU!!!!!!
This screen updating issue has been driving me crazy - Visual Studio code with a partially corrupted screen makes fast scrolling and searching for things so frustrating.  Its not just vscode, I see other apps where dialog boxes will not show up and like you the cmd window. 

I added the mks.enableDX12Presentation = "FALSE" to %USERPROFILE%\AppData\Roaming\VMware\preferences.ini - restarted workstation - and it worked perfectly!