![]() ![]() VMware Workstation and Device/Credential Guard are not compatible.Powering on a vm in VMware Workstation on Windows 10 host where Credential Guard/Device Guard is enabled fails with BSOD (2146361).Run Hyper-V in a Virtual Machine with Nested Virtualization.Simply run the below command to enable that feature Set-VMProcessor -VMName -ExposeVirtualizationExtensions $true See Using Hyper-V with Oracle VM VirtualBoxĮnable nested paging so that you can run other hypervisors inside Hyper-V. ![]() Use a hypervisor that supports Hyper-V like VirtualBox.If you have VMs running in other hypervisors like VMWare then just migrate them to Hyper-V If you want to use the sandbox feature then unfortunately you can't disable Hyper-V like in other answers. However on Windows 10 Build 18305 and up, beside the guard features, Windows Sandbox will also enable Hyper-V, because it's also a thin layer of virtualization METHOD you need to go into the control panel, then programs, then turn windows feature on or off, and Then it will pop up a window where you need to uncheck. More detailed information about those commands can be found on Manage Windows Defender Credential Guard If you don't need that level of security you can disable them by running DG_Readiness_Tool_v3.5.ps1 -Enable -AutoRebootĬopy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Yīcdedit /create device partition=X: As mentioned in another answer, Core isolation, Application Guard, Credential Guard and Device Guard utilize the Hyper-V feature. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |