Windows 10 Version 1709 and Hyper-v Issue

Hyper-V virtual machines don’t start after you upgrade to Windows 10 Version 1709
This is a know issue that is caused  by Antivirus programs.
Bellow is the Microsoft Solution and article.


Consider the following scenario:
  • You have a Windows 10-based computer that has the Hyper-V role installed.
  • You upgrade the computer to Windows 10 Version 1709.
In this scenario, you cannot start virtual machines. Also, you receive the following error message:
Start-VM : ‘VM_NAME’ failed to start. (Virtual machine ID XXXXXX)
‘VM_NAME’ failed to start worker process: %%3228369022 (0xC06D007E). (Virtual machine ID XXXXXXX)
At line:1 char:1
+ Start-VM VM_NAME
+ ~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Start-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVM

Additionally, you see the following entry in the System log:
The Hyper-V Host Compute Service service terminated unexpectedly.  It has done this 11 time(s).

And you see the following entry in the Application log:
Faulting application name: vmcompute.exe, version: 10.0.16299.15, time stamp: 0x1a906fe6
Faulting module name: vmcompute.exe, version: 10.0.16299.15, time stamp: 0x1a906fe6
Exception code: 0xc0000005
Fault offset: 0x000000000000474b
Faulting process id: 0x3d78
Faulting application start time: 0x01d34d80559647e6
Faulting application path: C:WINDOWSsystem32vmcompute.exe
Faulting module path: C:WINDOWSsystem32vmcompute.exe
Report Id: 0ec19ef4-d52a-4135-ae72-5cba92ec909f
Faulting package full name:
Faulting package-relative application ID:

Response: Not available
Cab Id: 0

Problem signature:
P1: vmcompute.exe
P2: 10.0.16299.15
P3: 1a906fe6
P4: vmcompute.exe
P5: 10.0.16299.15
P6: 1a906fe6
P7: c0000005
P8: 000000000000474b

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 0ec19ef4-d52a-4135-ae72-5cba92ec909f
Report Status: 4
Hashed bucket:


This issue occurs because Windows 10 Version 1709 enforces a policy that configures Vmcompute.exe not to allow any non-Microsoft DLL files to be loaded.


To fix this issue, check whether you have a non-Microsoft DLL file loaded in the Vmcompute.exe process. One possible cause of this issue is your antivirus software.