windows 10 vmware workstation pro 12 conflict

texture-filter=mipmap: FPS: 255 FrameTime: 3.922 ms texture-filter=linear: FPS: 252 FrameTime: 3.968 ms texture-filter=nearest: FPS: 237 FrameTime: 4.219 ms use-vbo=true: FPS: 546 FrameTime: 1.832 ms use-vbo=false: FPS: 230 FrameTime: 4.348 ms I don't know what to put for the VMName though. Not talking about inside WSL2 client here. And I don't want to wait another 2-3 years until the Hypervisor Platform API matures and then probably still having performance regressions.Ĭan I enable ExposeVirtualizationExtensions for the client that the main Windows 10 OS runs in. So that if Vmware or Virtualbox are started they will be able to access the Intel VT-x (and AMD equivalent) instructions?īasically I finally want to be able to run WSL2 while still keeping the Virtualbox support that I rely on. Wouldn't it be easier to just enable ExposeVirtualizationExtensions globally? Set-VMProcessor -VMName -ExposeVirtualizationExtensions $true However this API has been buggy for the last few Windows builds and after 2 years it is still not stable. The official solution as per the FAQ is that VMware and Virtualbox change their software so it uses the Hyper-V backend instead of their own via the Hypervisor Platform API.

It is the same issue as why those tools will not run with Windows Defender Credential Guard enabled. But this conflicts with 3rd party software like VMware or Virtualbox.

Windows 10 vmware workstation pro 12 conflict