You cannot start Hyper-V virtual machines after you enable the I/O verification option on a Hyper-V host computer that is running Windows Server 2012 or Windows 8

Assume that you have a Hyper-V host computer that is running Windows Server 2012 or Windows 8. After you enable the I/O verification option in Driver Verifier on the host computer, you cannot start virtual machines that are configured on the computer. Additionally, you receive the following error message on the host computer:



Additionally, the following error logs are logged under�Applications and Services Logs/Microsoft/Windows/Hyper-V-VMMS/Admin in Event Viewer:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: <Date><Time>
Event ID: 20144
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer_name.domain.com
Description:
The Virtual Machine Management Service failed to start the virtual machine '<machine_name>' because one of the Hyper-V components is not running (Virtual machine ID <ID_of_the_VM>)

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: <Date><Time>
Event ID: 15130
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer_name.domain.com
Description:
'<machine_name>' failed to start. (Virtual machine ID <ID_of_the_VM>)

This problem occurs because the I/O verifier option is not compatible�with Hyper-V drivers.

To work around this issue, disable the I/O verification option in Driver Verifier for all drivers on the host computer.

For more information about Driver Verifier, click the following article number to view the article in the Microsoft Knowledge Base: