Share via

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

22 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-09-08T19:49:45+00:00

    THANK YOU!!!

    I've been working on this for 2 hours and it FIXED my issue.

    ALL I NEEDED TO DO:

    1. STOP Hyper-V Service
    2. Open powershell / command prompt with Admin rights
    3. net localgroup administrators SERVICE /delete
    4. START Hyper-V Service
    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-09-09T22:05:46+00:00

    Glad your issue was solved.

    just out of curiosity, what build of windows 10 are you on?

    I don't use Hyper-V because I need a fully functioning XP mode. If your going to have a win7 or 8 guest, by all means, use Hyper-V. but if you need something older, like XP, use VMLite XPMode. It still works under the latest version of win10 (build 14393.105). I most recently installed a windows 3.1 Edu-tainment game (odell down under)  into XP mode and now, when ever I want to run it, I just go to the win10 start menu and start typing "odell" and the published entry comes right up. and the program opens when I select it as if it were running natively

    0 comments