Workstation Pro AMD-V disabled even if enabled in BIOS

[HenrikOlerud]

Hi

I can't get Workstation to work on my work computer.

I get the error message when I try to load (any) OS in Workstation, "This host supports AMD-V, but AMD-V is disabled"

I've already done/tried the following:

-virtualization eanbled in BIOS

- hyper-v removed under "turn windows features on or off".

I'm in touch with company IT support and they suspect that this may be linked to Virtualization Based Security on Credential Guard GPO.

What exactly should they look for?

I'm running Windows 10 Enterprise, version 1803, and currently latest Workstation Pro Edition, 15.5.1

[wila]

Hi,

After you make a change to the BIOS you have to power cycle the host.

IOW, the power must be removed for a bit (unplug the power cable, wait 20 seconds and plug it back in)

--

Wil

[HenrikOlerud]

Hi

Thank you for the suggestion.

I've now worked with IT-team at work, disabled Virtualization, restarted, then enabled again, hard-restarted (removed battery for a minute), and then booted.

Still same error message...

[wila]

Hi,

Have you tried updating the firmware/BIOS?

--

Wil

[HenrikOlerud]

Yes. latest version.

Iit seems Credential Guard GPO is enabling the Virtualization Based Security and preventing VMware VMs from starting. Is there anything I can do?

[wila]

Hi,

OK, I would have expected a slightly different error, but it certainly would explain your problems.

There's this KB article, but that mainly tells you to disable CG and VBS

https://kb.vmware.com/s/article/2146361

and more steps

https://www.techcrumble.net/2018/05/vmware-workstation-and-device-credential-guard-are-not-compatibl...

At this point in time disabling is the only way around it.

VMware and Microsoft have been working together so that this can be enabled, but this has not yet even made it in a public beta.

So for the moment there's no ETA for that.

More info:

https://techcommunity.microsoft.com/t5/Virtualization/VMware-Workstation-and-Hyper-V-Working-Togethe...

--

Wil

[HenrikOlerud]

Thank you for your assistance wila. Much appreciated!

Disabling it goes against corporate IT policy, so I'm kind of stuck...

I guess I could boot up hyper-V, install linux and then run workstation.

haha, but that's somewhat of a cumersome workaround that kind of defeats the purpose.

I guess I'll just have to wait, and run workstation on my personal computer until some resolution to this known problem emerges.

[wila]

Hi,

You're welcome.

It was a major engineering challenge for VMware to even get this working.

They showed it off at VMworld that it actually runs.

See also:

https://s3.us-east-2.amazonaws.com/vmworld-europe-2019/HBI2654BE.mp4 (around the 28:00 mark)

But running in a controlled environment is not the same as being able to release a product.

So hopefully soon.

--

Wil

[HenrikOlerud · Accepted solution]

hi.

Just a quick update. We have remote IT that "thought" they had enabled BIOS over the air, as HP support this.

My Lenovo PC apparently does not, as when IT turned up on site they discovered this.

Thus, solution is to double and triple check BIOS is enabled.

Case closed.