none
Win10 Hyper-V ran fine, now says "the hypervisor is not running", something is unhappy in service startup RRS feed

  • Question

  • Hi there,

    I have a Thinkpad P50 with the latest 1.56 bios from 2/21/2019, with the hardware virtualization and DEP things set in BIOS, and all the video drivers set to latest as of a week ago or so.

    It has been running Hyper-V machines for me for over a year just fine.

    Some patches or whatever updates came down, and all of a sudden none of my Hyper-V VMs will start with this message:
    ----------------------------
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          5/18/2019 9:42:15 PM
    Event ID:      20148
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      THINKSMARTIE
    Description:
    Virtual machine 'New Virtual Machine' could not be started because the hypervisor is not running (Virtual machine ID DD5EEC19-64E4-4448-BD41-76F53028AAA5).
    The following actions may help you resolve the problem:
    1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
    2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.)
    3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
    ----------------------------

    Now, it looks remarkably like this issue from long ago
    https://social.technet.microsoft.com/Forums/windows/en-US/5621cc86-b8de-4fe7-8d49-a07a6c5dc0c5/quotthe-hypervisor-is-not-runningquot-has-worked-in-the-past-on-same-hardware?forum=w8itprovirt so I went through all the same troubleshooting steps there.


    Systeminfo.exe output:
    ----------------------------
    Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                               Virtualization Enabled In Firmware: Yes
                               Second Level Address Translation: Yes
                               Data Execution Prevention Available: Yes
    ----------------------------
    Coreinfo.exe output:
    ----------------------------
    HTT             *       Hyperthreading enabled
    HYPERVISOR      -       Hypervisor is present
    VMX             *       Supports Intel hardware-assisted virtualization
    SVM             -       Supports AMD hardware-assisted virtualization
    X64             *       Supports 64-bit mode
    SMX             *       Supports Intel trusted execution
    SKINIT          -       Supports AMD SKINIT
    NX              *       Supports no-execute page protection
    SMEP            *       Supports Supervisor Mode Execution Prevention
    SMAP            *       Supports Supervisor Mode Access Prevention
    PAGE1GB         *       Supports 1 GB large pages
    PAE             *       Supports > 32-bit physical addresses
    PAT             *       Supports Page Attribute Table
    PSE             *       Supports 4 MB pages
    PSE36           *       Supports > 32-bit address 4 MB pages
    PGE             *       Supports global bit in page tables
    SS              *       Supports bus snooping for cache operations
    VME             *       Supports Virtual-8086 mode
    RDWRFSGSBASE    *       Supports direct GS/FS base access
    FPU             *       Implements i387 floating point instructions
    MMX             *       Supports MMX instruction set
    MMXEXT          -       Implements AMD MMX extensions
    3DNOW           -       Supports 3DNow! instructions
    3DNOWEXT        -       Supports 3DNow! extension instructions
    SSE             *       Supports Streaming SIMD Extensions
    SSE2            *       Supports Streaming SIMD Extensions 2
    SSE3            *       Supports Streaming SIMD Extensions 3
    SSSE3           *       Supports Supplemental SIMD Extensions 3
    SSE4a           -       Supports Streaming SIMDR Extensions 4a
    SSE4.1          *       Supports Streaming SIMD Extensions 4.1
    SSE4.2          *       Supports Streaming SIMD Extensions 4.2
    AES             *       Supports AES extensions
    AVX             *       Supports AVX intruction extensions
    FMA             *       Supports FMA extensions using YMM state
    MSR             *       Implements RDMSR/WRMSR instructions
    MTRR            *       Supports Memory Type Range Registers
    XSAVE           *       Supports XSAVE/XRSTOR instructions
    OSXSAVE         *       Supports XSETBV/XGETBV instructions
    RDRAND          *       Supports RDRAND instruction
    RDSEED          *       Supports RDSEED instruction
    CMOV            *       Supports CMOVcc instruction
    CLFSH           *       Supports CLFLUSH instruction
    CX8             *       Supports compare and exchange 8-byte instructions
    CX16            *       Supports CMPXCHG16B instruction
    BMI1            *       Supports bit manipulation extensions 1
    BMI2            *       Supports bit manipulation extensions 2
    ADX             *       Supports ADCX/ADOX instructions
    DCA             -       Supports prefetch from memory-mapped device
    F16C            *       Supports half-precision instruction
    FXSR            *       Supports FXSAVE/FXSTOR instructions
    FFXSR           -       Supports optimized FXSAVE/FSRSTOR instruction
    MONITOR         *       Supports MONITOR and MWAIT instructions
    MOVBE           *       Supports MOVBE instruction
    ERMSB           *       Supports Enhanced REP MOVSB/STOSB
    PCLMULDQ        *       Supports PCLMULDQ instruction
    POPCNT          *       Supports POPCNT instruction
    LZCNT           *       Supports LZCNT instruction
    SEP             *       Supports fast system call instructions
    LAHF-SAHF       *       Supports LAHF/SAHF instructions in 64-bit mode
    HLE             *       Supports Hardware Lock Elision instructions
    RTM             *       Supports Restricted Transactional Memory instructions
    DE              *       Supports I/O breakpoints including CR4.DE
    DTES64          *       Can write history of 64-bit branch addresses
    DS              *       Implements memory-resident debug buffer
    DS-CPL          *       Supports Debug Store feature with CPL
    PCID            *       Supports PCIDs and settable CR4.PCIDE
    INVPCID         *       Supports INVPCID instruction
    PDCM            *       Supports Performance Capabilities MSR
    RDTSCP          *       Supports RDTSCP instruction
    TSC             *       Supports RDTSC instruction
    TSC-DEADLINE    *       Local APIC supports one-shot deadline timer
    TSC-INVARIANT   *       TSC runs at constant rate
    xTPR            *       Supports disabling task priority messages
    EIST            *       Supports Enhanced Intel Speedstep
    ACPI            *       Implements MSR for power management
    TM              *       Implements thermal monitor circuitry
    TM2             *       Implements Thermal Monitor 2 control
    APIC            *       Implements software-accessible local APIC
    x2APIC          *       Supports x2APIC
    CNXT-ID         -       L1 data cache mode adaptive or BIOS
    MCE             *       Supports Machine Check, INT18 and CR4.MCE
    MCA             *       Implements Machine Check Architecture
    PBE             *       Supports use of FERR#/PBE# pin
    PSN             -       Implements 96-bit processor serial number
    PREFETCHW       *       Supports PREFETCHW instruction
    Maximum implemented CPUID leaves: 00000016 (Basic), 80000008 (Extended).
    Logical to Physical Processor Map:
    **------  Physical Processor 0 (Hyperthreaded)
    --**----  Physical Processor 1 (Hyperthreaded)
    ----**--  Physical Processor 2 (Hyperthreaded)
    ------**  Physical Processor 3 (Hyperthreaded)
    Logical Processor to Socket Map:
    ********  Socket 0
    Logical Processor to NUMA Node Map:
    ********  NUMA Node 0
    No NUMA nodes.
    Logical Processor to Cache Map:
    **------  Data Cache          0, Level 1,   32 KB, Assoc   8, LineSize  64
    **------  Instruction Cache   0, Level 1,   32 KB, Assoc   8, LineSize  64
    **------  Unified Cache       0, Level 2,  256 KB, Assoc   4, LineSize  64
    ********  Unified Cache       1, Level 3,    8 MB, Assoc  16, LineSize  64
    --**----  Data Cache          1, Level 1,   32 KB, Assoc   8, LineSize  64
    --**----  Instruction Cache   1, Level 1,   32 KB, Assoc   8, LineSize  64
    --**----  Unified Cache       2, Level 2,  256 KB, Assoc   4, LineSize  64
    ----**--  Data Cache          2, Level 1,   32 KB, Assoc   8, LineSize  64
    ----**--  Instruction Cache   2, Level 1,   32 KB, Assoc   8, LineSize  64
    ----**--  Unified Cache       3, Level 2,  256 KB, Assoc   4, LineSize  64
    ------**  Data Cache          3, Level 1,   32 KB, Assoc   8, LineSize  64
    ------**  Instruction Cache   3, Level 1,   32 KB, Assoc   8, LineSize  64
    ------**  Unified Cache       4, Level 2,  256 KB, Assoc   4, LineSize  64
    Logical Processor to Group Map:
    ********  Group 0
    ----------------------------

    Hyper-V is in the bcdedit:
    ----------------------------
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=\Device\HarddiskVolume4
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {current}
    resumeobject            {f31ed562-5e25-11e9-b64b-c06358e0b935}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 30

    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \WINDOWS\system32\winload.exe
    description             Windows 10
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {ab915a34-5e1d-11e9-9518-85b7012bfd0e}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \WINDOWS
    resumeobject            {f31ed562-5e25-11e9-b64b-c06358e0b935}
    nx                      OptIn
    bootmenupolicy          Standard
    hypervisorlaunchtype    Auto
    ----------------------------

    Device Manager properties for "Microsoft Hyper-V Virtualization Infrastructure Driver" show no problems with "Device ROOT\VID\0000 was started."

    Enabling Microsoft-Windows-Hyper-V-VMMS-Analytic log and restarting the Hyper-V Service and then starting a VM shows this in Microsoft-Windows-Hyper-V-VMMS-Admin:
    ----------------------------
    Information 5/18/2019 10:09:09 PM Microsoft-Windows-Hyper-V-VMMS 14092 None Virtual Machine Management service is being shut down.
    Information 5/18/2019 10:09:09 PM Microsoft-Windows-Hyper-V-VMMS 19040 None The WMI provider 'VmmsWmiEventProvider' has shut down.
    Information 5/18/2019 10:09:09 PM Microsoft-Windows-Hyper-V-VMMS 19040 None The WMI provider 'VmmsWmiInstanceAndMethodProvider' has shut down.
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 32623 None The machine contains non-identical GPUs. This is not a supported configuration for RemoteFX.
    Error 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 15350 None The virtualization infrastructure driver (VID) is not running.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33452 None "Replication health limits:
    ReplicationHealthWarningCycleFactor: 10
    ReplicationHealthCriticalCycleFactor: 20
    ReplicationWarning30SecIntervalThresholdInSeconds: 300
    ReplicationCritical30SecIntervalThresholdInSeconds: 600"
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33454 None "Replication health limits:
    ReplicationHealthWarningCycleFactor: 6
    ReplicationHealthCriticalCycleFactor: 12
    ReplicationWarning5MinsIntervalThresholdInSeconds: 1800
    ReplicationCritical5MinsIntervalThresholdInSeconds: 3600"
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33456 None "Replication health limits:
    ReplicationHealthWarningCycleFactor: 4
    ReplicationHealthCriticalCycleFactor: 8
    ReplicationWarning15MinsIntervalThresholdInSeconds: 3600
    ReplicationCritical15MinsIntervalThresholdInSeconds: 7200"
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33458 None "Replication health limits:
    SupressDeltaReplicationCycleMissWarningAfterIrInHours: 24
    DelayInLastAppConsistentRecoveryPointCyclesWarning: 2
    NoProgressInIrOrResyncWarningThresholdInMinutes: 30
    NoProgressInIrOrResyncCriticalThresholdInMinutes: 60"
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 12514 None Found a certificate for server authentication. Remote access to virtual machines is now possible.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 20410 None Successfully started the Virtual Machine migration connection manager.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33480 None "Change tracking has defined following limits for free disk space.
    Free Disk space error limit 3072 MBs (Minimum value can be 1024 MBs).
    Free Disk space warning limit 4915 MBs."
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33481 None "Change tracking has defined following limits for pending log file size.
    Error limit : 50% (Minimum value 10%. Maximum value 100%).
    Warning limit : 40%.
    Information limit : 30%."
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33834 None Hyper-V would age out CDP reference points after 720 hours.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 33483 None Incremental Replication will timeout after 360 hours. Minimum value for timeout is 6 hours.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 14094 None Virtual Machine Management service is started successfully.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 19020 None The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
    Information 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 19020 None The WMI provider 'VmmsWmiEventProvider' has started.
    Error 5/18/2019 10:09:18 PM Microsoft-Windows-Hyper-V-VMMS 20148 None "Virtual machine 'DC' could not be started because the hypervisor is not running (Virtual machine ID A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5).
    The following actions may help you resolve the problem:
    1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
    2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.)
    3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
    "
    Error 5/18/2019 10:09:18 PM Microsoft-Windows-Hyper-V-VMMS 15160 None 'DC' failed to restore virtual machine state. (Virtual machine ID A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5)
    ----------------------------

    Meanwhile, Microsoft-Windows-Hyper-V-VMMS-Analytic shows this:
    ----------------------------
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to open global VID statistics object! HRESULT = 0x80070103
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None TesthooksWrapper::Initialize: Load RdvTestHooks.dll failed. HRESULT=0x8007007e. All test hooks checks will return default values.
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Synth3dPhysicalGPUManager::InitPhysicalGPUManager:The system has heterogeneous adapters with different descriptors.
    Error 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1102 None LpStatistics::Initialize: HbUtil init failed! Error = 2
    Error 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1102 None ServiceModule::PrepareToRunSelf: Failed to initialize LpStatistics with HRESULT: 80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None No guest interface device found : (VMID = 0FEADE0C-7CED-464D-9AD1-1DC20CA03362).
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None No guest interface device found : (VMID = 2889C52B-5037-42BD-9A5B-8DFBFB7D46A0).
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None No guest interface device found : (VMID = 4C20E12B-147F-4034-A3AB-321E1D360C05).
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None No guest interface device found : (VMID = A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5).
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None No guest interface device found : (VMID = DD5EEC19-64E4-4448-BD41-76F53028AAA5).
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set remoting certificate for VM 0FEADE0C-7CED-464D-9AD1-1DC20CA03362!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set remoting certificate for VM 2889C52B-5037-42BD-9A5B-8DFBFB7D46A0!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set remoting certificate for VM 4C20E12B-147F-4034-A3AB-321E1D360C05!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set remoting certificate for VM A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set remoting certificate for VM DD5EEC19-64E4-4448-BD41-76F53028AAA5!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set allowed hash algorithms for VM 0FEADE0C-7CED-464D-9AD1-1DC20CA03362!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set allowed hash algorithms for VM 2889C52B-5037-42BD-9A5B-8DFBFB7D46A0!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set allowed hash algorithms for VM 4C20E12B-147F-4034-A3AB-321E1D360C05!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set allowed hash algorithms for VM A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5!
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to set allowed hash algorithms for VM DD5EEC19-64E4-4448-BD41-76F53028AAA5!
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None "vm\service\resmgr\video\synth3dvideopoolrepository.cpp(884)\vmms.exe!00007FF76696D393: (caller: 00007FF7669622FB) Exception(1) tid(2138) 80004005 Unspecified error
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None [Synth3dPhysicalGPUManager::InitGpuStates()@1356] Caught exception: Unspecified error (0x80004005)
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 0FEADE0C-7CED-464D-9AD1-1DC20CA03362! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 0FEADE0C-7CED-464D-9AD1-1DC20CA03362! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 2889C52B-5037-42BD-9A5B-8DFBFB7D46A0! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 2889C52B-5037-42BD-9A5B-8DFBFB7D46A0! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 4C20E12B-147F-4034-A3AB-321E1D360C05! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for 4C20E12B-147F-4034-A3AB-321E1D360C05! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for A562BDE5-DB2F-4D8A-B365-C9FBEE1128C5! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for DD5EEC19-64E4-4448-BD41-76F53028AAA5! HRESULT = 0x80070002
    Warning 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1101 None VmmsRealizedVirtualMachine::GetBackupSnapshot: ReadString failed for DD5EEC19-64E4-4448-BD41-76F53028AAA5! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot 738CA875-CFA7-4913-BD17-4FD8C298B563! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot 738CA875-CFA7-4913-BD17-4FD8C298B563! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot C73F7EC5-BA6C-4F62-9338-E6D61A0ABD66! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot C73F7EC5-BA6C-4F62-9338-E6D61A0ABD66! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot 90309819-DEED-4F35-B259-82C34ED417F1! HRESULT = 0x80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None VmmsVirtualMachineSnapshot::GetReplicaType: ReadUnsignedInteger failed for snapshot 90309819-DEED-4F35-B259-82C34ED417F1! HRESULT = 0x80070002
    Error 5/18/2019 10:09:18 PM Microsoft-Windows-Hyper-V-VMMS 1102 None "vm\service\vmmgr\vmmsrealizedvirtualmachine.cpp(2219)\vmms.exe!00007FF766D3FF24: (caller: 00007FF766D334AF) Exception(2) tid(2138) 80004005 Unspecified error
    Error 5/18/2019 10:09:18 PM Microsoft-Windows-Hyper-V-VMMS 1102 None [VmmsRealizedVirtualMachine::RestoreInternal()@2325] Exception caught.: Unspecified error (0x80004005)
    ----------------------------

    I do have 5 VMs, and I think warning messages for each VM about guest interfaces and remoting certificates and hash algorithms can be safely ignored. That just leaves the errors:
    ----------------------------
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Failed to open global VID statistics object! HRESULT = 0x80070103
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None TesthooksWrapper::Initialize: Load RdvTestHooks.dll failed. HRESULT=0x8007007e. All test hooks checks will return default values.
    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1101 None Synth3dPhysicalGPUManager::InitPhysicalGPUManager:The system has heterogeneous adapters with different descriptors.
    Error 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1102 None LpStatistics::Initialize: HbUtil init failed! Error = 2
    Error 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 1102 None ServiceModule::PrepareToRunSelf: Failed to initialize LpStatistics with HRESULT: 80070002
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None "vm\service\resmgr\video\synth3dvideopoolrepository.cpp(884)\vmms.exe!00007FF76696D393: (caller: 00007FF7669622FB) Exception(1) tid(2138) 80004005 Unspecified error
    Error 5/18/2019 10:09:12 PM Microsoft-Windows-Hyper-V-VMMS 1102 None [Synth3dPhysicalGPUManager::InitGpuStates()@1356] Caught exception: Unspecified error (0x80004005)
    ----------------------------

    This smells like something is barfing with initialization of the video subsystem. I have an intel discrete Intel(R) HD Graphics 530 and NVIDIA Quadro M2000M with the latest drivers and happily driving built-in monitor and 2 4K externals without any problems.

    The VMs are on bitlockered drive, if it matters.

    I have already tried:

    - Disabled and reenabled HW virtualization and DEP setting in BIOS with cold boots

    - Removed and re-added Hyper-V

    Any idea what I can do before I am forced to reinstall this dev machine from scratch?

    Thank you!
    Daniel

    Sunday, May 19, 2019 5:25 AM

All replies

  • Did you enable RemoteFX for the VM?

    Warning 5/18/2019 10:09:11 PM Microsoft-Windows-Hyper-V-VMMS 32623 None The machine contains non-identical GPUs. This is not a supported configuration for RemoteFX.

    Sunday, May 19, 2019 5:43 AM
  • I don't know how to enable RemoteFX and don't ever remember enabling anything. 

    On a brand new VM I have created, the Settings\Add Hardware list shows RemoteFX 3D Video Adapter disabled. When selecting it, I see "We no longer support the RemoteFX 30 video adapter. You can keep usng this adapter on existing VMS, but you can't apply it to any new VMS." message.

    None of my old VMs have Physical GPUs associated with them either.

    Sunday, May 19, 2019 5:14 PM
  • Open powershell elevated, launch

    remove-windowsfeature hyper-v

    reboot

    Again, open an elevated powershell

    add-windowsfeature hyper-v

    (normally) done.


    Sunday, May 19, 2019 6:32 PM
  • As I've already mentioned, this has already been done to no effect, although I used Add Windows Components dialog instead of powershell cmdlet. But as I understand, the effect should be the same.

    Sunday, May 19, 2019 6:41 PM
  • Oh, sorry...clearly too much text for me to pay attention to details ;-)

    You could try to repair with an inplace upgrade of windows.

    Sunday, May 19, 2019 7:29 PM
  • Yes, indeed I could and likely would, just trying to avoid having all the hassle of the reinstall. Any one else has any ideas?
    Sunday, May 19, 2019 11:17 PM
  • An inplace-upgrade means no hassle. Start setup within windows - settings and files and programs are kept.
    Monday, May 20, 2019 3:58 AM