Windows 10: Hyper-V stops working after bios update

Before I ask the question, here's my hardware:

Intel Core i7-9700k CPU @ 3.60GHZ overclocked to 4.6GHZ

32.0GB Ram 31.9 usable

Nvidia Geforce RTX 2080

Windows 10 Home Insider Build#19628


Hyper-V was working fine until around a week ago when not only did it break vms, it caused a bsod labled

HYPERVISOR_ERROR

On vmware it gives me this error:


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


And apparently this isnt a huge help.

It leads to vmwares website which leads me to microsoft and then there is a dead end, because I have win10 home.


Any help is appreciated

winterfoxx

:)

 

Firmware update or hyper-v causes automatic repair loop everytime

Microsoft does not upgrade BIOS firmware you have to install the BIOS firmware from your computer manufacturer website.

Use the following steps to enable Hyper-V on Windows 10:

• Open Control Panel.
• Click on Programs.
• Click on Turn Windows features on or off.
• Check the Hyper-V option making sure: Hyper-V Management Tools and Hyper-V Platform are also selected.
• Click OK to begin the process.

 

Hyper V deativication

Hi Geoffrey,

Hyper-V lets you run an operating system or computer system as a virtual machine on Windows. Before proceeding in disabling
Hyper-V, please create a backup of your files for security purposes.

To disable Hyper-V, please follow the steps below:

• On the Cortana search box, type Turn Windows Features on or off and press
  Enter.
• Look for the Hyper-V folder.
• Uncheck the tick-box next to the main Hyper-V folder and click
  OK.
• Restart your PC.

Should you have further questions, please let us know.

 

Firmware update or hyper-v causes automatic repair loop everytime

Actually some machines can receive Firmware updates through Windows Updates. As for the reboots, I would also look at Secure Boot getting fouled up and clearing that option to reset it. The Hash may not match when it reboot causing these errors.