VMware Communities
Naicisum
Contributor
Contributor

VMware Workstation 15.5.6 build-16341506 & Windows 10 2004 (OS Build 19041.329) - Credential Guard Error

Unable to boot VMs

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Visit http://www.vmware.com/go/turnoff_CG_DG for more details.

Transport (VMDB) error -14: Pipe connection has been broken.

Also see this in the logs:

2020-06-24T14:49:25.855-05:00| vmx| I005: IOPL_Init: Hyper-V detected by CPUID

2020-06-24T14:49:25.856-05:00| vmx| W003: WHP_CanBeInstalled: Hyper-V is not present, function should not be called.

2020-06-24T14:49:25.873-05:00| vmx| I005: IOPL_VBSRunning: VBS is set to 2

2020-06-24T14:49:25.873-05:00| vmx| I005: Msg_Post: Error

2020-06-24T14:49:25.873-05:00| vmx| I005: [msg.vmx.vbsRunningDetected] VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Visit http://www.vmware.com/go/turnoff_CG_DG for more details.

2020-06-24T14:49:25.873-05:00| vmx| I005: ----------------------------------------

2020-06-24T14:49:26.882-05:00| vmx| I005: Module 'IOPL' initialization failed.

0 Kudos
2 Replies
scott28tt
VMware Employee
VMware Employee

See: Powering on a vm in VMware Workstation on Windows 10 host where Credential Guard/Device Guard is ena...


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
Naicisum
Contributor
Contributor

This has been followed.

To resolve the issue do one of the following:

  • Upgrade host hardware and software to meet minimum requirements as described in the Cause section above.

There should be no need to disable anything.

0 Kudos