Page 2 of 4 FirstFirst 1234 LastLast
  1.    07 Aug 2015 #11
    Join Date : Sep 2014
    Posts : 340
    Window 10
    Thread Starter

    Quote Originally Posted by Kari View Post
    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.
    Sorry, I thought I did as you asked. When clicking on the "details" tab this is a what the XML view is for the 3040 error (with extra line returns deleted). The error 15130 error XML error output follows it.
    2040 Error:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
    <EventID>3040</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-07T18:08:18.707154700Z" />
    <EventRecordID>224</EventRecordID>
    <Correlation />
    <Execution ProcessID="6300" ThreadID="7024" />
    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
    <Computer>i5-Win8-1</Computer>
    <Security UserID="S-1-5-83-1-3049452786-1304491133-4189872545-898222336" />
    </System>
    - <UserData>
    - <VmInitialize
    xmlns
    ="http://www.microsoft.com/Windows/Virtualization/Events">
    <VmName>Friday Test 2</VmName>
    <VmId>B5C2F4F2-F47D-4DC0-A161-BCF900C98935</VmId>
    </VmInitialize>

    </UserData>
    </Event>

    The 15130 error:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />

    <EventID>15130</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2015-08-07T18:08:19.212255100Z" />

    <EventRecordID>2001</EventRecordID>

    <Correlation />


    <Execution ProcessID="2784" ThreadID="4720" />


    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>i5-Win8-1</Computer>

    <Security UserID="S-1-5-18" />

    </System>


    - <UserData>
    - <VmlEventLog
    xmlns
    ="http://www.microsoft.com/Windows/Virtualization/Events">
    <VmName>Friday Test 2</VmName>

    <VmId>B5C2F4F2-F47D-4DC0-A161-BCF900C98935</VmId>


    </VmlEventLog>


    </UserData>


    </Event>


      My ComputerSystem Spec
  2.    07 Aug 2015 #12
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,116
    Windows 10 Pro

    Sometimes this is difficult! Those are from the Event Viewer, not the error messages from Hyper-V. As such the event ID is useless because with it, to restart the service is about the only advice which can be found.

    Here's an example of a Hyper-V error message. Clicking Show details additional information is shown, which can often help to pinpoint the cause of the error:

    Click image for larger version. 

Name:	2015-08-07_20h44_13.png 
Views:	60 
Size:	33.2 KB 
ID:	29262
      My ComputerSystem Spec
  3.    07 Aug 2015 #13
    Join Date : Sep 2014
    Posts : 340
    Window 10
    Thread Starter

    Quote Originally Posted by Kari View Post
    Sometimes this is difficult! Those are from the Event Viewer, not the error messages from Hyper-V. As such the event ID is useless because with it, to restart the service is about the only advice which can be found.

    Here's an example of a Hyper-V error message. Clicking Show details additional information is shown, which can often help to pinpoint the cause of the error:

    Click image for larger version. 

Name:	2015-08-07_20h44_13.png 
Views:	60 
Size:	33.2 KB 
ID:	29262
    Sorry, I was focused on the even log entries because the popup when I try to start the VM doesn't say much. Here it is:Click image for larger version. 

Name:	Error3.png 
Views:	13 
Size:	84.1 KB 
ID:	29267
      My ComputerSystem Spec
  4.    07 Aug 2015 #14
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,116
    Windows 10 Pro

    OK in this case the additional info in the error message really does not reveal anything.

    Do you store the virtual hard disks and configuration files on default places? VHD files in C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks, and the configuration files in C:\ProgramData\Microsoft\Windows\Hyper-V? If so you could try this and tell if you could create and run a vm:

    • Create a folder Hyper-V on root of any drive than C:
    • On that folder create a subfolder, name it as VHD, and another with a name VM
    • Create a new VM
    • In New Virtual Machine Wizard, step Specify name and location, select Store the virtual machine in a different location, browse to the Hyper-V\VM folder you created and select it as the location
    • In New Virtual Machine Wizard, step Connect Virtual Hard Disk, click the Browse button next to Location, browse to the Hyper-V\VHD folder you created and select it
    • Finish the setup, launch the vm
      My ComputerSystem Spec
  5.    07 Aug 2015 #15
    Join Date : Sep 2014
    Posts : 340
    Window 10
    Thread Starter

    Quote Originally Posted by Kari View Post
    OK in this case the additional info in the error message really does not reveal anything.

    Do you store the virtual hard disks and configuration files on default places? VHD files in C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks, and the configuration files in C:\ProgramData\Microsoft\Windows\Hyper-V? If so you could try this and tell if you could create and run a vm:

    • Create a folder Hyper-V on root of any drive than C:
    • On that folder create a subfolder, name it as VHD, and another with a name VM
    • Create a new VM
    • In New Virtual Machine Wizard, step Specify name and location, select Store the virtual machine in a different location, browse to the Hyper-V\VM folder you created and select it as the location
    • In New Virtual Machine Wizard, step Connect Virtual Hard Disk, click the Browse button next to Location, browse to the Hyper-V\VHD folder you created and select it
    • Finish the setup, launch the vm
    I followed the instructions precisely. Checking the Event Log it shows that the VM was created successfully.
    I get the exact same error detail for the new machine as I posted earlier.
      My ComputerSystem Spec
  6.    07 Aug 2015 #16
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,116
    Windows 10 Pro

    OK, that last one was to test that we do not have any permissions issues; if you get the same error message even when everything is located in a folder you created, it's not a permissions issue.

    The last vm you created, please open its settings and take a screenshot of it, post here. An example of what I want to see, settings of a vm:

    Click image for larger version. 

Name:	2015-08-07_22h30_03.png 
Views:	6 
Size:	46.5 KB 
ID:	29283

    Additionally, please answer the following questions:
    • What kind of user account you are signed in (admin user MS or local, standard user MS or local)?
    • The amount of RAM on your host?
    • Last time before the upgrade when you used a Hyper-V vm, did it open without issues?
    • After the upgrade, has a Hyper-V virtual machine ever worked and started normally or did this start already the first time after the upgrade when you tried to launch a vm?
      My ComputerSystem Spec
  7.    07 Aug 2015 #17
    Join Date : Sep 2014
    Posts : 340
    Window 10
    Thread Starter

    Quote Originally Posted by Kari View Post
    OK, that last one was to test that we do not have any permissions issues; if you get the same error message even when everything is located in a folder you created, it's not a permissions issue.

    The last vm you created, please open its settings and take a screenshot of it, post here. An example of what I want to see, settings of a vm:

    Click image for larger version. 

Name:	2015-08-07_22h30_03.png 
Views:	6 
Size:	46.5 KB 
ID:	29283

    Additionally, please answer the following questions:
    • What kind of user account you are signed in (admin user MS or local, standard user MS or local)?
    • The amount of RAM on your host?
    • Last time before the upgrade when you used a Hyper-V vm, did it open without issues?
    • After the upgrade, has a Hyper-V virtual machine ever worked and started normally or did this start already the first time after the upgrade when you tried to launch a vm?
    Here is the screen shot:
    Click image for larger version. 

Name:	Error4.png 
Views:	3 
Size:	153.8 KB 
ID:	29286
    And for your questions:
    What kind of user account you are signed in (admin user MS or local, standard user MS or local)? I am an administrator and get the same errors when I use the built-in Administrator account.
    The amount of RAM on your host? 8GB
    Last time before the upgrade when you used a Hyper-V vm, did it open without issues? Yes
    After the upgrade, has a Hyper-V virtual machine ever worked and started normally or did this start already the first time after the upgrade when you tried to launch a vm? A VM has never worked since the upgrade. The VMs only worked pre-upgrade.

    Thanks for you ongoing help!
      My ComputerSystem Spec
  8.    07 Aug 2015 #18
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,116
    Windows 10 Pro

    How important are the pre-upgrade virtual machines to you? Would it be acceptable to lose them in order to get this fixed? I would like to suggest something but if you follow that suggestion, the virtual machines are lost. They might be reusable by first copying the vhd files to a safe location, then if we get this fixed use them as existing vhd when creating new virtual machines, but I cannot guarantee that.
      My ComputerSystem Spec
  9.    07 Aug 2015 #19
    Join Date : Sep 2014
    Posts : 340
    Window 10
    Thread Starter

    Quote Originally Posted by Kari View Post
    How important are the pre-upgrade virtual machines to you? Would it be acceptable to lose them in order to get this fixed? I would like to suggest something but if you follow that suggestion, the virtual machines are lost. They might be reusable by first copying the vhd files to a safe location, then if we get this fixed use them as existing vhd when creating new virtual machines, but I cannot guarantee that.
    Only one of the VMs is important. When I started troubleshooting I backed up the VHD files for the VMs. What is the process please?
      My ComputerSystem Spec
  10.    07 Aug 2015 #20
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,116
    Windows 10 Pro

    Quote Originally Posted by PJLLB View Post
    Only one of the VMs is important. When I started troubleshooting I backed up the VHD files for the VMs. What is the process please?
    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:

    Click image for larger version. 

Name:	2015-08-07_23h33_48.png 
Views:	5 
Size:	113.5 KB 
ID:	29298
      My ComputerSystem Spec

 
Page 2 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
How to open my XP mode machines
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, ...
Virtualization
Switch User - at least 2 methods fail (Start menu, tsdiscon.exe)
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...
User Accounts and Family Safety
Windows Hello (any machines with right hardware)
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...
Drivers and Hardware
Virtual Machines/Virus Software
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 ...
Virtualization
Cannot access W7 machines FROM W10
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...
Virtualization
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 18:53.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums