Machines Fail to Start and Initialize

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 384
    Window 10
    Thread Starter
       #21

    Kari said:
    warning   Warning
    The process below will remove all your virtual machines and they cannot be recovered. The virtual hard disks if copied to a safe location might be able to be used on new virtual machines later on.

    If you proceed you do it acknowledging this. I cannot be held responsible for the loss of your virtual machines.


    1. In Hyper-V Manager, delete all virtual machines (right click, select Delete)
    2. Close the Hyper-V Manager
    3. Manually delete the files remaining in C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
    4. Right click Start, select Programs and Features
    5. Select Turn Windows features on or off on the left pane
    6. Expand Hyper-V list item, unselect everything in it to disable Hyper-V
    7. Reboot
    8. Create new storage locations for virtual hard disks and virtual machines (configuration files) on another drive than C:, you can for example use the X:\Hyper-V\VHD and X:\Hyper-V\VM folders as I told in an earlier post of mine
    9. Co back to Windows features, this time re-enable everything Hyper-V related
    10. Reboot
    11. Launch Hyper-V Manager, change the default storage locations to those you created (see screenshot below this list)
    12. Create a new vm, run it, come back to tell if it started normally or not


    Change VHD & VM storage locations:
    I'll give it a try after I complete a cloning process for the boot drive. (Cloning is giving me fits saying at this point that it can't complete -- the cloning app from Samsung keeps failing....sigh...)

    UPDATE: I booted from an old Windows 7 disk and the disk cloning software is chugging away cloning the Windows 10 disk to my new SSD. This clone will allow me to test without permanent destruction to the existing VMs should something go wrong.

    Thanks again.
    Last edited by PJLLB; 07 Aug 2015 at 18:44.
      My Computer


  2. Posts : 384
    Window 10
    Thread Starter
       #22

    Kari, I was able to clone my production drive so that I could experiment without fear of hosing it. I then followed the instructions and attempted to start a new VM with the locations on a different drive. The machine would not start with the same errors as before.
      My Computer


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

    OK. At the moment I have no idea why this is happening. I will do some testing, trying to reproduce the issue and will come back to tell if I found something.
      My Computer


  4. Posts : 384
    Window 10
    Thread Starter
       #24

    Kari said:
    OK. At the moment I have no idea why this is happening. I will do some testing, trying to reproduce the issue and will come back to tell if I found something.
    Thank you VERY much for your on-going assistance!
      My Computer


  5. Posts : 3
    Windows 8.1
       #25

    I know the error message not telling you that you have insufficient permission.
    But it's worth a try..
    https://support.microsoft.com/en-us/kb/2249906

    You can make a quick test by giving the user "everyone" full access on the folder that holding all your vm's.
      My Computer


  6. Posts : 384
    Window 10
    Thread Starter
       #26

    Tomerello said:
    I know the error message not telling you that you have insufficient permission.
    But it's worth a try..
    https://support.microsoft.com/en-us/kb/2249906

    You can make a quick test by giving the user "everyone" full access on the folder that holding all your vm's.
    Thanks for the suggestion, but I had already reviewed this TechNet item and had already changed each and every related folder and file to add "Everyone" with full access rights. I went ahead and tried it again/checked existing permissions and for those for a newly-created VM and no success. Thanks for the suggestion.

    Does anyone know if I should be getting an XML file for each newly-created VM with the VM's SID as the file name? I'm not getting these...(?)
    Last edited by PJLLB; 09 Aug 2015 at 22:21.
      My Computer


  7. Posts : 384
    Window 10
    Thread Starter
       #27

    I never was able to complete all the troubleshooting I wanted to because somewhere along the line the Windows installation became corrupted. Windows would boot and get to the point where the sound driver loaded -- I could hear the speakers energize -- and the mouse became useable. But booting stopped at the black screen just prior to where the sign-in screen should have appeared. (If anyone has any thoughts on how to fix it I would appreciate hearing. I tried everything I could think of or find on the web with no luck.)

    So I bit the bullet and did a clean install on a new SSD drive. (I had to do an upgrade using my old Windows 8 activation key since I didn’t have a new Windows 10 key.) Hyper-V works correctly in all aspects. I was eventually able to add the old drive with the corrupted Windows image and retrieve all of my data, including the Hyper-V virtual drive files. I am able to attach them to the new virtual machines and they work great.

    The one last bit of troubleshooting I wanted to perform (but couldn't because of the Windows corruption on the old installation) was to uninstall Hyper-V services, delete the C:\ProgramData\Microsoft\Windows\Hyper-V folder and subfolders, reinstall Hyper-V services letting it recreate the tree, recreate VMs, and attach the old VM dive files to them. That might have worked but I'll never know.

    Thanks for everyone's help along the line.
      My Computer


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

    I am sorry that you had to reinstall, and sorry for not being able to help you. Your issue was very unique, I've not seen that before.

    I hope Hyper-V will work for you in the future as you'd like it to work :)
      My Computer


  9. Posts : 384
    Window 10
    Thread Starter
       #29

    Kari said:
    I am sorry that you had to reinstall, and sorry for not being able to help you. Your issue was very unique, I've not seen that before.

    I hope Hyper-V will work for you in the future as you'd like it to work :)
    Kari, I very much appreciate all of your efforts. Hyper-V is functioning flawlessly running my XP machine. And with Windows 10 it's running much faster.

    Cheers!
      My Computer


  10. Posts : 1
    Windows 10 x64
       #30

    Hello everyone
    I know that the thread is old, but I just want to say that I'm facing the same described error.
    And I can't go with a new system installation.
    My Windows 10 is a fresh install (not an upgrade from win 8)
    I have many apps installed on, and can't format my SSD
    I have vmware installed and it's the default virtual machine manager that I use
    thank you for your new suggestions
      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 00:33.
Find Us




Windows 10 Forums