Intel graphics and media control panel windows 10 2017
T07:03:38.386+08:00| mks| I125: MKS-RenderMain: Collecting RenderOps caps from DX11Renderer
#Intel graphics and media control panel windows 10 2017 keygen
This is the from the two different vmware log of VM startup. So if the workaround is successful, your VM log should not show an Intel HD 4600. You will likely see something similar in your VM vmware.log that it just sees the Intel graphics first and simply just creates a DX11 device. When I switched Nvidia control panel to use Intel graphics as the preferred, it came first and Workstation simply created DX11 device context and sure enough the VM wasn't using the Nvidia GPU. It looks like it just creates a DX11 device context on whatever the first render device Windows gives it. Under the hood, Workstation 12.5 for Windows is using DirectX 11 unless it is disabled in the vmx configuration. Hopefully the result is your VM instance is using Nvidia and you get to keep your dual display configuration.
keep the Intel HD graphics enabled in the EFI/BIOS, so that you get to keep 2 displays booting up.