To resolve the issue, use one of the following methods.
Method 1
To resolve this issue, you can disable the hypervisor. The hypervisor can be disabled and enabled independent of the Hyper-V role. This does not uninstall all Hyper-V components. To do this, follow these steps:
Note When hypervisor is disabled, Hyper-V virtual machines cannot be started.
- Run Command Prompt as an Administrator.
- Type bcdedit and then press Enter.
- Under Windows Boot Loader an identifier is reported. Type bcdedit /set {identifier} hypervisorlaunchtype off and then press Enter.
Note identifier is a placeholder for the identifier reported.
The ability to quickly toggle between having the hypervisor turned on and off is achievable through adding an additional boot entry. To do this, follow these steps:
- Run Command Prompt as an Administrator.
- Type bcdedit /copy {default} /d "Hypervisor Off". An identifier will be returned that indicates a new boot entry was created successfully.
- Type bcdedit /set {identifier} hypervisorlaunchtype off and then press Enter.
Note identifier is a placeholder for the identifier that was returned in step 2.
After you finish these steps, a boot entry named "Hypervisor Off" is available when you start the computer. When you select the startup entry, hypervisor is disabled.
Method 2
As a last resort to regain the Connected Standby power state, you must disable the Hyper-V role. Disabling the Hyper-V role uninstalls all Hyper-V components. To do this, follow these steps:
- On the Windows charms bar, select Settings, and then start Control Panel.
- In Control Panel, select Programs, and then click Programs and Features.
- In the left menu bar, select Turn Windows features on or off.
- Click to clear the Hyper-V check box.
- Click OK.
Note Other components that use Hyper-V may have their functionality reduced or eliminated if the Hyper-V role is removed.