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
    2015-08-25T21:54:52+00:00

    found a solution to the 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

    13 people found this answer helpful.
    0 comments
  2. Anonymous
    2016-02-20T06:50:47+00:00

    I had these error #s in event viewer: 32670 (or was it 32617... something like that) and the 15130 error that these guys had.

    FIX:

    1. in admin powershell / command prompt: 
      1. net localgroup administrators SERVICE /add
    2. uninstall hyper-V
    3. install Hyper-V
    4. in admin powershell / command prompt:
      1. net localgroup administrators SERVICE /delete

    Not sure if the commands are necessary, but if a reinstall doesn't work, try that.

    0 comments
  3. Anonymous
    2016-03-31T01:30:23+00:00

    this worked for me - thanks Cybot.

    I just stopped the hyper-v service.  removed the service account in an administrative prompt, started the hyper-v service and then the guest started properly.

    0 comments
  4. Anonymous
    2016-04-01T05:31:46+00:00

    I had these error #s in event viewer: 32670 (or was it 32617... something like that) and the 15130 error that these guys had.

    FIX:

    1. in admin powershell / command prompt: 
      1. net localgroup administrators SERVICE /add
    2. uninstall hyper-V
    3. install Hyper-V
    4. in admin powershell / command prompt:
      1. net localgroup administrators SERVICE /delete

    Not sure if the commands are necessary, but if a reinstall doesn't work, try that.

    this fix has already been posted, but thank you for your post

    0 comments
  5. Anonymous
    2016-04-01T05:43:30+00:00

    great to hear it. I hope hyper v works out for you. Hyper V did not provide for my needs, which was XP mode or something like it. I ended up installing VMLite XP Mode, which has the exact same functions as windows 7 XP Mode and can even use the VHD provided by XP Mode. XP mode remains activated, and no adjustments to the virtual machine or the PC was necessary. I needed XP mode along with hardware pass through, but hyper-v does not support usb in the virtual machine like XP mode did. I need it in order to use a canon scanner that does not have any 64-bit drivers, (or drivers for any os past XP for that matter)

    0 comments