Hyper-V Virtual Machines Fail to Start and Initialize after Windows 10 Upgrade from Windows 8.1

Anonymous
2015-08-01T20:24:10+00:00

My Windows 8.1 Hyper-V virtual machines worked fine. I just upgraded to Windows 10 (with the CPU hypervisor turned off) and when I attempt to start the machines (after enabling the hypervisor) I get the errors: "'(machine name)' failed to start." and "'(machine name)' could not initialize." The same thing happens when I attempt to create a new virtual machine and then start it. Any thoughts on this would be very appreciated.

UPDATE:  SEE MY UPDATE BELOW FOR MORE SOLUTION INFORMATION.

Windows Server High availability Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

22 answers

Sort by: Most helpful
  1. Anonymous
    2015-08-05T03:49:00+00:00

    when I upgraded from win7 I lost XP mode, so I got out my old XP disc and was going to setup a virtual machine running XP, but when I click the start button on the VM, I get the same error as the OP. I have the VM set as gen 1 so that isn't the issue.

    the only possible error message in my eventviewer is this one:

    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.

    **-** <Eventxmlns="**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-05T01:40:36.409812100Z" />


    <EventRecordID>351</EventRecordID>


    <Correlation />


    <Execution ProcessID="3196"ThreadID="908" />


    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>


    <Computer>ChrisSolomon-PC</Computer>


    <Security UserID="S-1-5-18" />

    **** </System>


    <EventData />

    ****</Event>

    there are no remotefx options anywhere in the vm or in hyper-v settings, so I am not sure how to fix this

    0 comments No comments
  2. Anonymous
    2015-08-06T20:19:13+00:00

    Some updates:  The problem persists.  Initial errors included Hypervisor error and machine start errors.  I was able to eliminate the Hypervisor issues by changeing the boot configuration data store file for the hypervisorlaunchtype to "Auto" from "Off."  Now when attempting to start a new Virtual Machine in Hyper-V Manager and start it I get event ID 3040 errors that the VM could not initialize and the event ID 15130 errors that the VM failed to start.  All other event log entries look normal.  Troubleshooting continues...

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-08-07T02:51:41+00:00

    I already had my VM set for manual launch so I wasn't running into that particular issue. Someone I talked to  suggested that the error might be caused by the fact that I was trying to use XP in the VM. This is not the cause. as the VM Is currently blank., I had selected the option 'install the guest os later" during VM setup.  The way the VM is setup now, if it ran, it would act like any computer that has no OS, The VM does not even launch to the point where it would access my optical drive where the disc is.

    further research has told me that remoteFX is only available on hyper-v on Server versions of Windows. I could not find any references saying the remoteFX was going to be available for Windows 10 Pro. which makes the error I found in my event viewer that much more strange.

    0 comments No comments
  4. Anonymous
    2015-08-11T06:30:14+00:00

    I setup a vm on win8.1.2 using the exact same settings I used on win10, and the vm started to boot (it did not totally boot beacuase there was no OS, but I got expected results) there is definitely an issue with win10 hyper-v. I did notice that disabling the hyper-v remotfx3d entry in device manager seems to allow the vm to boot further before erroring out with the same error as in OP

    0 comments No comments
  5. Anonymous
    2015-08-12T22:21:25+00:00

    to everyone who is experiencing this problem:

    look in your event viewer in this log: applications and services>Micorosoft>Hyper-V VMMS,

    now filter the log to show only errors and warnings.

    are you seeing this error?

    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.

    I'm not sure as to what this error means, my video card is installed and working. Windows 10 setup did upgrade my video drivers for me, so maybe that's the issue. I will try and install the latest driver package available for my video card and see if that helps. if you see the above error, please make a post confirming that your seeing it and list your video card.

    video card: Nvidia GTX300M

    0 comments No comments