Event ID 17 — Hypervisor Availability
Applies To: Windows Server 2008
This is preliminary documentation and subject to change.
.jpg)
Hypervisor availability
Event Details
| Product: | Windows Operating System |
| ID: | 17 |
| Source: | Microsoft-Windows-Hyper-V-Hypervisor |
| Version: | 6.0 |
| Symbolic Name: | HV_EVENTLOG_FAILED_TO_OPEN_REG_KEY |
| Message: | Hyper-V launch failed; the registry key %1 could not be opened by the Hyper-V boot driver (status %2). |
Resolve
Check BCD store
The hypervisor launch configuration information could not be read from the Boot Configuration Data (BCD) store. The BCD store contains boot configuration parameters and controls how the operating system is started in Windows Vista and Windows Server 2008 operating systems. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM (NVRAM) entries (in Extensible Firmware Interface-based operating systems).
You can use the Bcdedit.exe command-line tool to update BCD store with the correct launch options as referenced in the error, and then restart the server. Bcdedit.exe is located in the \Windows\System32 directory by default.
Note: Administrative privileges are required to use bcdedit to modify the BCD store. Unless otherwise specified, bcdedit operates on the system store by default.
On PC/AT BIOS systems, the BCD store resides in the active partition's \boot folder. On EFI systems, the file is located on the EFI system partition (ESP) under \EFI\Microsoft\Boot.
Caution: The BCD data store is a registry hive, but that hive should not be accessed with the registry API. Interaction with the underlying firmware occurs in the supported BCD interfaces. For this reason, BCD stores should be accessed only through the associated tools or WMI API. Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
For further information on using Bcdedit.exe, see https://go.microsoft.com/fwlink/?LinkId=147513
Verify
Hypervisor successfully starts.