Windows 10: Machines Fail to Start and Initialize Solved

Page 1 of 4 123 ... LastLast
  1.    01 Aug 2015 #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 ComputerSystem Spec


  2. Posts : 339
    Windows 10 Pro x86 and x64 dual boot
       01 Aug 2015 #2

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

  3.    01 Aug 2015 #3

    banger said: View Post
    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 ComputerSystem Spec


  4. Posts : 339
    Windows 10 Pro x86 and x64 dual boot
       03 Aug 2015 #4

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

  5.    03 Aug 2015 #5

    banger said: View Post
    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 ComputerSystem Spec

  6.    06 Aug 2015 #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 ComputerSystem Spec

  7.    07 Aug 2015 #7

    Hi there

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

    Cheers
    jimbo
      My ComputerSystem Spec


  8. Posts : 11,229
    Windows 10 Pro
       07 Aug 2015 #8

    Try this, tell what if anything happens:

    Stop the Hyper-V service, then restart it:

    Click image for larger version. 

Name:	2015-08-07_15h26_45.png 
Views:	9 
Size:	72.1 KB 
ID:	29182

    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 ComputerSystem Spec

  9.    07 Aug 2015 #9

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

    Stop the Hyper-V service, then restart it:

    Click image for larger version. 

Name:	2015-08-07_15h26_45.png 
Views:	9 
Size:	72.1 KB 
ID:	29182

    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:
    Click image for larger version. 

Name:	Error1.png 
Views:	8 
Size:	59.0 KB 
ID:	29218
    Click image for larger version. 

Name:	Error2.png 
Views:	5 
Size:	63.0 KB 
ID:	29219
    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 ComputerSystem Spec


  10. Posts : 11,229
    Windows 10 Pro
       07 Aug 2015 #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 ComputerSystem Spec


 
Page 1 of 4 123 ... LastLast

Related Threads
Hi, after upgrading to Win 10 I can't figure out how to open my XP - Mode (Virtual PC) Machines. I need them for work as a developer for certain legacy apps. Please tell me there is a way to get this back please. Thank you for your help, ...
I work on a desktop with multiple users changing frequently, and like to switch users rapidly and easily. I used to have a taskbar shortcut to tsdiscon.exe (in System32) which worked fine in Win 8. In Win 10 I've had to reinstall tsdiscon.exe, but...
MS recently revealed Windows Hello, which uses biometric information to authenticate users. I am interested in this feature (and am starting to look around at new laptops since mine is dying). Now, Windows Hello will require hardware that can read...
Hi, This is unrelated to Win 10 so thought this area might be best I put the VMWare Player on my PC to use Win 10 and would also like to now try putting XP on it for a bit of nostalgia, no networking with host but would like internet on it ...
Hi there W10 still seems to have some type of networking problem - OUTGOING is OK -- W10 CAN see W7 HDD's and access them. W7 CAN see W10 computer but cannot access any HDD's. W7 CAN access W10 if you specify the actual IP address for example...
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 22:54.
Find Us