Windows 10: Machines Fail to Start and Initialize Solved

Page 4 of 4 FirstFirst ... 234
  1.    12 Jun 2016 #31

    Solution


    PJLLB said: View Post
    I have already done this, many time, including restarting the PC. However, the error persists.
    These are the two errors I am now receiving:
    Attachment 29218
    Attachment 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.
    The problem you had seems to happen when Windows 10 is installed while virtualization is disabled in BIOS. Enabling virtualization afterwards causes Hyper-V to malfunction. Removing Hyper-V and reinstalling it will not fix it. Unfortunately, the only solution I know is to enable virtualization in BIOS before installing Windows 10. This seems to be a bug in Windows 10. I have reproduced this problem on two separate computers. This is why you were finally successful when you enabled virtualization before reinstalling Windows 10.
      My System SpecsSystem Spec

  2.    01 Nov 2016 #32

    Same Issue - Tried all the Troubleshooting methods listed


    I am having the same issue with the same vague error.

    I've unsinstalled/reinstalled Hyper-V. Changed the directory. There is no SERVICE account in the administrators group, so that's not the issue.

    I am at a total loss here. The server instance simply will not start.

    I didn't see any overt local policies that could be blocking it.

    Any other ideas as to why this won't start up?
      My System SpecsSystem Spec

  3.    15 Nov 2016 #33

    Hansa said: View Post
    The problem you had seems to happen when Windows 10 is installed while virtualization is disabled in BIOS. Enabling virtualization afterwards causes Hyper-V to malfunction. Removing Hyper-V and reinstalling it will not fix it. Unfortunately, the only solution I know is to enable virtualization in BIOS before installing Windows 10. This seems to be a bug in Windows 10. I have reproduced this problem on two separate computers. This is why you were finally successful when you enabled virtualization before reinstalling Windows 10.
    Thank you for saying that.

    After reading that, it explains exactly my situation. I created on image on a PC that did not have VT, and now when I put that image on other PCs with VT, VMs do not work.

    ****.
      My System SpecsSystem Spec


 
Page 4 of 4 FirstFirst ... 234

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 01:46.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums