Wednesday, January 13, 2010 6:43 AM
Just as the title said. when I go to start a this vm in hyper-v manager, error "Unnamed VM' could not initialize." occured.
Event ID 3072 and 3040 occured.
'Unnamed VM' could not initialize. (Virtual machine ID 69B6E463-1F54-42FF-A160-C9247BACDF66)
'Unnamed VM' could not read or update the virtual machine configuration because access was denied: General access denied error (0x80070005). Check the security settings on the folder in which the virtual machine is stored. (Virtual machine ID 69B6E463-1F54-42FF-A160-C9247BACDF66)
Can any one help on this?
Wednesday, January 13, 2010 8:07 AMModerator
Have you get the same issue with other VMs?
Please navigate to the folder where the problematic located(such as d:\VMs\VM123), right click on the folder of the VM name > Properties > Security, please check whether you can find Virtual Machine in the list.
Wednesday, January 13, 2010 8:27 AMI can start other VM without any issue. this vm's xml file is also there. I have checked folder ACL for this problematic vm, I'am the owner and full control.
Thursday, January 14, 2010 7:39 AMModerator
On a file or a folder related to Hyper-V, there is another permission you have to noticed, as I mentioned in my last reply, please check whether you can find the “Virtual Machines” in the security tab on the problematic VM’s folder. Please take a screen shot and upload it to some place and then paste the link here.
By the way, please also check the symbolic link file related to this problematic VM in C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\(this folder is hidden by default), switch to Security tab on properties of the file. Please take a screen shot and upload it to some place and then paste the link here.
Note: Please navigate to the VM’s folder, such as D:\VMs\XXXX\ Virtual Machines\, you will be able to find a XML such as 57A83597-2729-41BE-AD0F-B7835A8DFCEB.XML, 57A83597-2729-41BE-AD0F-B7835A8DFCEB is the GUID of this VM. In C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\, you will be able to find a symbolic file associated with 57A83597-2729-41BE-AD0F-B7835A8DFCEB.XML.
In addition, did you have any antivirus software installed on the Hyper-V host computer? Did the problematic VM work properly before the issue occurred? Have you done something to the problematic VM?
- Marked As Answer by Vincent HuModerator Thursday, January 14, 2010 7:48 AM
Thursday, January 14, 2010 7:43 AMsorry for my careless not going to check the "Virtual Machines" entry in the ACL list.
Thanks for your help Vincent. I got the issue resolved.
Wednesday, November 10, 2010 3:22 PM
I have some problem too when I moved some VMs manually from a server with a hardware issues and I created a tool to fix this issue. The tool is called Hyper-V Unnamed VM Fix and is available FREE at http://ctxadmtools.musumeci.com.ar/HyperVHotFixes
Tuesday, December 14, 2010 9:28 PM
That tool does not work for me.
Altough the error message is the same as in this thread, but my problem started after installing Virtual Machine Manager 2008 R2.
Its really annoying how Microsoft creates its software: you deploy an MS application and all your business critical systems just die.
Friday, April 01, 2011 12:25 AMdid you ever figure this out, what did you do to fix it? i've had it happen twice, once do to storage migration and the other time to expanding a vhd
Friday, April 01, 2011 8:29 AM
Unfortunately I had to reinstall my whole system.
Thursday, May 10, 2012 2:13 PM
I am also experiencing the same issue. With no resolution posted here, I tried a few things and have a valid workaround at best:
Take note of your VM path, ex... D:\Virtual Machines\[VM Name Here]
1. In the Hyper V Manager, Right click on the virtual machine and click delete (this doesn't delete the VHD).
2. In Hyper V Manager, select "New" in the top right and then virtual machine.
3. Create a new VM with the same name as the old one. Make sure to select "store the virtual machine in a different location" and point it to the VM path ex... D:\Virtual Machines\[VM Name Here]
4. Give the VM ram, and connect it to a network
5. Connect the New VM to the Old VHD File.... should be located in D:\Virtual Machines Location\Virtual Machine Name\Virtual Hard Disks\VM Name.vhd
Have tested this on 3 machines with 100% success. I will also note that I did not have a "Virtual Machines" permisison group, and when I attempted to add it, the object did not exist either.
Hope this helps someone.
Friday, September 07, 2012 8:24 PM
Did you first try setting permissions on the highest folder in your VM hierarchy? While I am using only a lab/test environment, these errors disappear when you add the Authenticated Users group to the permissions of the top of the folder hierarchy, with the permission of Modify. That's a whole lot less painful if you do not have a Virtual Machines group, as I do not in a W2K8R2 SP1 workgroup environment for testing.
Hope this helps somebody.
- Proposed As Answer by MarkWheatley Friday, September 07, 2012 8:24 PM
Friday, September 14, 2012 7:20 AM
IT HELPS! I was near by panic but you are right: in my case were was no "Virtual Machines" object and is wasn't present in ACL as well, but adding Authenticated Users in root folder really solved the problem! Fanks a lot!!!
by the way, I've found "Virtual Machines" object. It's "built-in security principals" type of object related to the local machine,
- Edited by ElenM Friday, September 14, 2012 9:38 AM