Machines Fail to Start and Initialize

Page 1 of 4 123 ... LastLast

  1. Posts : 384
    Window 10
       #1

    Machines Fail to Start and Initialize


    My Windows 8.1 virtual machines worked fine. I just upgraded to Windows 10 and when I attempt to start the machines I get the error '(machine name)' failed to start. and '(machine name)' could not initialize. The same thing happens when I attempt to create a new virtual machine. Any thoughts on this would be very appreciated.
      My Computer


  2. Posts : 550
    Windows 10 Pro x86 and x64 dual boot
       #2

    I get the same on VMware player with xp vm, I get internal error. Player update needed?
      My Computers


  3. Posts : 384
    Window 10
    Thread Starter
       #3

    banger said:
    I get the same on VMware player with xp vm, I get internal error. Player update needed?
    I doubt it. I am using Windows Hyper-V. And it doesn't appear to depend on the OS of the VM -- I can create a new VM but when I try to start it I get the same error.
      My Computer


  4. Posts : 550
    Windows 10 Pro x86 and x64 dual boot
       #4

    Seems VMware player is fickle sometimes they will boot and sometimes not.
      My Computers


  5. Posts : 384
    Window 10
    Thread Starter
       #5

    banger said:
    Seems VMware player is fickle sometimes they will boot and sometimes not.
    I am not using VMware, I am using the built-in Windows Hyper-V virtual machine service.
      My Computer


  6. Posts : 384
    Window 10
    Thread Starter
       #6

    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...
      My Computer


  7. Posts : 11,247
    Windows / Linux : Arch Linux
       #7

    Hi there

    Kari is the expert on HYPER-V -- why not PM him for a suggestion.

    Cheers
    jimbo
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
       #8

    Try this, tell what if anything happens:

    Stop the Hyper-V service, then restart it:

    Machines Fail to Start and Initialize-2015-08-07_15h26_45.png

    When done, create a new vm and try to start it. If it does not start but gives an error message instead, post the screenshot of the expanded error message with all details, or post the full text of said error message.

    Kari
      My Computer


  9. Posts : 384
    Window 10
    Thread Starter
       #9

    Kari said:
    Try this, tell what if anything happens:

    Stop the Hyper-V service, then restart it:

    Machines Fail to Start and Initialize-2015-08-07_15h26_45.png

    When done, create a new vm and try to start it. If it does not start but gives an error message instead, post the screenshot of the expanded error message with all details, or post the full text of said error message.

    Kari
    I have already done this, many time, including restarting the PC. However, the error persists.
    These are the two errors I am now receiving:
    Machines Fail to Start and Initialize-error1.png
    Machines Fail to Start and Initialize-error2.png
    For public consumption, this is what I said in a PM to you. It summarizes everything, including fixing the virtualization errors. The two errors are the images above:
    My Windows 8.1 Hyper-V virtual machines worked fine. I just upgraded to Windows 10 (with the CPU virtualization turned off) and after turning virtualization back on when I attempted to start the machines (after enabling the hypervisor) I get errors hypervisor errors and "'(machine name)' failed to start." and "'(machine name)' could not initialize." errors. The same thing happened when I created a new virtual machine (which created successfully) and then start it. Initial event log errors for the Hypervisor errors have been solved. I was able to eliminate the Hypervisor issues by changing 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 only get the 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. Again, these error occur both with virtual machines that ran fine under Windows 8.1 and new ones created after the upgrade to Windows 10.

    I posted about this issue on the Windows 10 Community Forum and four other people indicated they had the same issue.
      My Computer


  10. Posts : 17,661
    Windows 10 Pro
       #10

    Could you please do as I asked. I am not interested in Event Viewer reports, I want to see the full error message when you start the vm. Usually these error messages have a Details link, I am mostly interested to see the detailed error description.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:52.
Find Us




Windows 10 Forums