VMware Communities
dh77771
Contributor
Contributor
Jump to solution

Windows Insider Build 17666 does not allow a VM to start

When starting VMWARE with insiders build 17666 released May 9, 2018 VMWARE complains that credential guard/device guard is enabled but if you check the settings as described in document 2146361 neither are enabled and the procedure described to make VMWARE work has no benefit. Only solution I could find is to revert to an earlier build (17661) which allows VMWARE to work properly but has a issue with Explorer crashing so I would like to move off this version ASAP.

Reply
0 Kudos
1 Solution

Accepted Solutions
Scillonian
Hot Shot
Hot Shot
Jump to solution

Have you also gone to Windows Defender Security Centre > Device Security > Core Isolation and disabled the settings there?

View solution in original post

Reply
0 Kudos
3 Replies
Scillonian
Hot Shot
Hot Shot
Jump to solution

Have you also gone to Windows Defender Security Centre > Device Security > Core Isolation and disabled the settings there?

Reply
0 Kudos
dh77771
Contributor
Contributor
Jump to solution

That does allow the VM to start but why was it not a problem with the 17661 builds and earlier?

Great that it works but I wonder why it became a problem?

Reply
0 Kudos
Scillonian
Hot Shot
Hot Shot
Jump to solution

That does allow the VM to start but why was it not a problem with the 17661 builds and earlier?

From my observations these settings have been disabled by default in earlier builds but perhaps they are now enabled by default as Microsoft pushes forward with virtualisation based security.

Reply
0 Kudos