none
Hyper-V error VM failed to start. VM could not initialize RRS feed

  • Question

  • my system is able to run XP mode with hardware support on windows 7, and is also able to run Hyper-V on windows 8/8.1. But when ever I try to start any VM, even one with out a OS installed to it yet, I get a error message

    [VM NAME] failed to start.

    [VM NAME] could not initialize.

    there is no other error details listed in the error window except for the VM ID. I have checked to make sure that VT-x is still enabled in Bios. I have tried temporarily disabling my AV.


    forgot to add I am running Windows 10 Pro (Release) upgraded from Windows 7 Ultimate x64 SP1
    • Edited by Cybot Sunday, August 16, 2015 1:20 AM
    Sunday, August 16, 2015 1:13 AM

All replies

  • On Sun, 16 Aug 2015 01:13:27 +0000, Cybot wrote:

    there is no other error details listed in the error window except for the VM ID. I have checked to make sure that VT-x is still enabled in Bios. I have tried temporarily disabling my AV.

    Check to see if your computer supports SLAT:

    http://www.howtogeek.com/73318/how-to-check-if-your-cpu-supports-second-level-address-translation-slat/


    Paul Adare - FIM CM MVP

    Sunday, August 16, 2015 7:46 AM
  • yes it does. it's an i7. if it didn't I would not have been able to run hyper-v on 8.1 or xp mode using hw acceleration on windows 7.

    because I have hyper-v installed coreinfo only reported that I have a a hypervisor running. I will go ahead and uninstall it again and run the program again. However, using windows built in utility, systeminfo.exe, before the last time I reinstalled hyper-v, when I ran systeminfo, all the parts that needed to be true in order to support hyper-v were marked as yes.

    update:

    Coreinfo v3.31 - Dump information on system CPU and memory topology
    Copyright (C) 2008-2014 Mark Russinovich
    Sysinternals - www.sysinternals.com
    Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz
    Intel64 Family 6 Model 30 Stepping 5, GenuineIntel
    Microcode signature: 00000007
    HYPERVISOR      -       Hypervisor is present
    VMX             *       Supports Intel hardware-assisted virtualization
    EPT             *       Supports Intel extended page tables (SLAT)

    from SYSTEMINFO.EXE :

    Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                               Virtualization Enabled In Firmware: Yes
                               Second Level Address Translation: Yes
                               Data Execution Prevention Available: Yes

    • Edited by Cybot Monday, August 17, 2015 1:17 AM
    Monday, August 17, 2015 12:55 AM
  • On Mon, 17 Aug 2015 00:55:13 +0000, Cybot wrote:

    yes it does. it's an i7. if it didn't I would not have been able to run hyper-v on 8.1 or xp mode using hw acceleration on windows 7

    Neither Hyper-V in 8.1 nor Virtual PC in Windows 7 required SLAT, Windows
    10 does, hence my question.


    Paul Adare - FIM CM MVP

    Monday, August 17, 2015 2:36 AM
  • Hi,

    Please also check Motherboard and BIOS edition to make sure both of them were upgrade to be latest.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, August 17, 2015 3:07 AM
    Moderator
  • bios version is the latest available for my PC

    I did run coreinfo without the -v and noticed that it said I had no numa nodes. is this normal? do I need these inorder to run hyper-v?

    • Edited by Cybot Monday, August 17, 2015 7:30 AM
    Monday, August 17, 2015 7:26 AM
  • On Mon, 17 Aug 2015 07:26:42 +0000, Cybot wrote:

    I did run coreinfo without the -v and noticed that it said I had no numa nodes. is this normal? do I need these inorder to run hyper-v?

    No, you do not need them.


    Paul Adare - FIM CM MVP

    Monday, August 17, 2015 2:23 PM
  • well, then I don't know what the heck is going on.

    all my specs say hyper-v will run, but hyper-v is clearly not running

    I am seeing at least once a windows session a message from hyper-v regarding remoteFX which makes no sense, since M$ says remoteFX is not included with windows 10 client Hyper-V

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          8/17/2015 5:46:34 PM
    Event ID:      32607
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      ChrisSolomon-PC
    Description:
    The required GPU resources could not be accessed. This server cannot run as a RemoteFX host without a GPU. Verify that the GPU is correctly installed.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
        <EventID>32607</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2015-08-18T00:46:34.622836400Z" />
        <EventRecordID>1334</EventRecordID>
        <Correlation />
        <Execution ProcessID="3208" ThreadID="3120" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>ChrisSolomon-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
      </EventData>
    </Event

    I'm also seeing this error pop-up sporadically, which also makes no sense as I do have a SLAT capable CPU:

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          8/16/2015 7:54:35 PM
    Event ID:      32616
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      ChrisSolomon-PC
    Description:
    Virtual machines configured with a 3D video adapter can only run on systems that have a SLAT capable CPU.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
        <EventID>32616</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2015-08-17T02:54:35.710112500Z" />
        <EventRecordID>1276</EventRecordID>
        <Correlation />
        <Execution ProcessID="3592" ThreadID="4372" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>ChrisSolomon-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
      </EventData>
    </Event>


    • Edited by Cybot Tuesday, August 18, 2015 6:42 AM
    Tuesday, August 18, 2015 5:25 AM
  • also found this error too

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          8/16/2015 7:54:36 PM
    Event ID:      15350
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      ChrisSolomon-PC
    Description:
    The virtualization infrastructure driver (VID) is not running.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
        <EventID>15350</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2015-08-17T02:54:36.094935200Z" />
        <EventRecordID>1295</EventRecordID>
        <Correlation />
        <Execution ProcessID="3592" ThreadID="3812" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>ChrisSolomon-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
        </VmlEventLog>
      </UserData>
    </Event>

    Tuesday, August 18, 2015 6:46 AM
  • Hi,

    I have the same problem but system was installed clean.

    CPU Intel core i7 2600k

    Video Nvidia GTX570

    Motherboard Gigabyte Gigabyte

    RAM 16GB

    Friday, August 21, 2015 11:31 AM
  • Hi,

    I have the same problem.

    But windows was clean installed.

    CPU Intel Core i7 2600K

    GPU Nvidia gtx570

    Motherboard Gigabyte H67A-UD3H-B3

    RAM 16GB

    Friday, August 21, 2015 11:36 AM
  • are you seeing errors related to remoteFX as well in your event viewer?

    application and services logs > Micorosoft > Windows > Hyper-V-VMMS > Admin

    P.S. try filtering the results to only show errors and warnings.

    Don't know if I listed it yet, but since others are I will too.

    CPU i7-720QM

    GPU GT330M

    Motherboard ??? (I don't know what motherboards To$hiba uses.)

    RAM 8Gb

    • Edited by Cybot Sunday, August 23, 2015 1:58 AM
    Saturday, August 22, 2015 3:19 AM
  • when ever I try to start any VM, even one with out a OS installed to it yet, I get a error message

    Maybe you should look at the "start any VM" aspect too.

    FWIW this is how I started with the W10 Preview

    http://blogs.technet.com/b/canitpro/archive/2014/10/02/step-by-step-creating-and-running-a-windows-10-vm-on-windows-8-1.aspx

    That same VM is still working in W10 RTM (mostly).  W10 seems to have inherited its connectivity problems but I have never seen the symptoms that you are reporting.



    Robert Aldwinckle
    ---

    Sunday, August 23, 2015 6:25 AM
  • Motherboard ??? (I don't know what motherboards To$hiba uses.)

    Check msinfo32.exe System Summary?  FWIW my Surface 2 Pro couldn't answer this question either:  BaseBoard Model Not Available

    <eg>



    Robert Aldwinckle
    ---

    Sunday, August 23, 2015 6:33 AM
  • found a solution to my issue, at the admin prompt type this command:

    net localgroup administrators SERVICE /delete

    if this does not fix the issue for you undo the command by typing this:

    net localgroup administrators SERVICE /add

    you will need to completely shutdown hyper-v after running the command before it will take effect.

    got the idea from here:

    https://social.technet.microsoft.com/Forums/systemcenter/en-US/0cbc8280-b612-4958-9a8b-229f183f1877/failed-to-initialize-event-3040?forum=virtualmachingmgrhyperv

    Sunday, August 23, 2015 5:35 PM
  • msinfo couldn't find the baseboard model on my laptop either

    Sunday, August 23, 2015 5:38 PM
  • before I found a solution I tried following M$'s step by step hyper-v directions for windows 10 and they did not work. the VM would not start I even took the time to d/l the win 8.1 enterprise eval as mentioned in the directions
    Sunday, August 23, 2015 5:40 PM
  • got the idea from here:

    https://social.technet.microsoft.com/Forums/systemcenter/en-US/0cbc8280-b612-4958-9a8b-229f183f1877/failed-to-initialize-event-3040?forum=virtualmachingmgrhyperv

    How did you manage to find that?  The Event id is completely different from what you were reporting.  Were you getting 3040 too?  Like the OP I am mystified as to how that could help.  ProcMon traces of both cases would be my approach to trying to find out.

    Talk about cryptic:

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.0&EvtID=3040&EvtSrc=Alerter&LCID=1033

    <quote>

    User Action

    Reorganize the replicated directories so that no path is more than 32 levels deep.

    </quote>

    So, apparently that is what you must have accomplished by getting rid of the account.   ; ]

    But this just made me realize that I didn't try the TechNet Event code search for your codes.  Turns out that would have been a waste of time because none of your codes are found that way.  One of them almost is

    https://social.technet.microsoft.com/Search/en-us/?query=15350&refinement=82&ac=2

    BTW sorry if I wasted your time with my comment about how I got started with W10 Preview.  I was only trying to point out that I was able to use a Hyper-V VM (of a particular kind) in W10 RTM.  I could have mentioned also that someone else found a way to avoid crashes involving Hyper-V by modifying the BCD, in case that is related.

    https://social.technet.microsoft.com/Forums/en-US/fbc37aac-509d-43b6-ac36-dde0b145147e/windows-10-x64-pro-boot-loop-with-hyperv-enabled?forum=win10itprovirt#73d20d8d-c3a2-4d0c-87e8-908a8305243b

    Thanks for sharing your resolution.



    Robert Aldwinckle
    ---

    Sunday, August 23, 2015 6:30 PM
  • the event ID that was in the link was showing upin the event viewer, but they were showing up in the HYPER-V-Worker event log not the HYPER-V-VMMS log. I don't remember exactly how I came across that posting, I think it was purely by chance during one of my countless googling sessions trying to find a fix. some of my best work oddly enough has happened that way. like transferring everything off my mom's really old palm treo 750 over to her new IPhone 5 despite the fact that Version said it was not possible. anyway like the one of the people in posted link said, I don't know why it worked. I also don't know if running that command will have any long term repercussions down the road.

    I also don't think those error ID links you posted are relevant as one was for replication, and the other was for SQL server, neither of which I have running or installed. but if the basis for the error I still the same, then do you think I should post something in the windows feedback log?

    also, why are only some users running into this issue. 

    just for reference this is the error I was seeing in the HYPER-V-Worker log:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
      <EventID>3040</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-08-16T00:51:27.889843900Z" />
      <EventRecordID>82</EventRecordID>
      <Correlation />
      <Execution ProcessID="6096" ThreadID="7876" />
      <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
      <Computer>ChrisSolomon-PC</Computer>
      <Security UserID="S-1-5-83-1-533163340-1253994001-3824508584-1912117294" />
      </System>
    - <UserData>
    - <VmInitialize
    xmlns
    ="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>New Virtual Machine</VmName>
      <VmId>1FC76D4C-6E11-4ABE-A85E-F5E32E98F871</VmId>
      </VmInitialize>
      </UserData>
      </Event>



    • Edited by Cybot Friday, September 4, 2015 2:40 AM
    Tuesday, August 25, 2015 9:48 PM
  • this issue appears to still be an issue even under Windows 10 Professional version 1511 (OS Build 10586.36) x64
    Thursday, December 24, 2015 1:32 AM
  • Same issue here, except it only happens when I try to run a VM from Server 2008 or 2012. Desktop OS's run fine, including Linux and Windows. Weird.
    Saturday, January 30, 2016 12:28 AM
  • I think this will help you

    http://techgenix.com/enabling-physical-gpus-hyper/

    Wednesday, December 26, 2018 7:51 PM