Since the first of the two solutions looks to be too many steps, I elected to use the bcdedit approach. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.Īnother approach is run the following bcdedit command at an elevated command prompt and reboot.On the host operating system, click S tart > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.To disable Device Guard or Credential Guard disable the group policy setting that was used to enable Credential Guard. Since there could be lost data, the next approach is to attack this problem from the other side, Microsoft. If you are not in this predicament, then you can stop reading here. A forceful shutdown will be needed, but will loose the current state. These virtual machines have the Virtualization engine options greyed out. There are many virtual machines that are suspended. After removing those features, I was able to start the virtual machine.
0 kommentar(er)
