Symptoms
A Hyper-V virtual machine may fail to start, and you receive an error message that resembles the following:
An error occurred while attempting to start the selected virtual machine(s).
‘VMName’ failed to start.
Microsoft Emulated IDE Controller (Instance ID
{83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error ‘General
access denied error’
IDE/ATAPI Account does not have sufficient privilege to open attachment
‘E:\VMs\VMName\Disk0.vhd. Error: ‘General access denied error’
Account does not have sufficient privilege to open attachment
‘E:\VMs\VMName\Disk0.vhd. Error: ‘General access denied error’
If you click
See details in the message window, the following information is displayed:
‘VMName’ failed to start. (Virtual machine ID
5FC5C385-BD98-451F-B3F3-1E50E06EE663)
‘VMName’ Microsoft Emulated IDE Controller (Instance ID
{83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error ‘General
access denied error’ (0x80070005). (Virtual machine ID
5FC5C385-BD98-451F-B3F3-1E50E06EE663)
‘VMName’: IDE/ATAPI Account does not have sufficient privilege to open attachment
‘E:\VMs\VMName\Disk0.vhd. Error: ‘General access denied error’ (0x80070005). (Virtual
Machine ID 5FC5C385-BD98-451F-B3F3-1E50E06EE663)
‘VMName’: Account does not have sufficient privilege to open attachment
‘E:\VMs\VMName\Disk0.vhd. Error: ‘General access denied error’ (0x80070005). (Virtual
Machine ID 5FC5C385-BD98-451F-B3F3-1E50E06EE663)
Notes- This error message references either the Microsoft Emulated IDE Controller or the Microsoft Synthetic SCSI Controller.
- This error message references either a virtual hard disk (.vhd) file or a snapshot file (.avhd).
- The Virtual Machine ID is unique to every virtual machine.
Cause
This issue occurs if the permissions on the virtual hard disk (.vhd) file or the snapshot file (.avhd) are incorrect.
Every
Hyper-V virtual machines has a unique Virtual Machine ID (SID). If the
Virtual Machine SID is missing from the security permissions on the .vhd
or .avhd file, the virtual machine does not start, and you receive the
"‘General access denied error’ (0x80070005)" error message that is
mentioned in the "Symptoms" section.
Resolution
To resolve this issue, add the Virtual Machine SID to the virtual hard disk (.vhd) file or to the snapshot file (.avhd).
To add the Virtual Machine SID to a .vhd or .avhd file, follow these steps:
- Note the Virtual Machine ID that is listed in the "‘General access denied error’ (0x80070005)" error message.
For example, consider the following error message:
‘VMName’: IDE/ATAPI Account does not have sufficient privilege to open attachment
‘E:\VMs\VMName\Disk0.vhd. Error: ‘General access denied error’ (0x80070005). (Virtual
Machine ID 5FC5C385-BD98-451F-B3F3-1E50E06EE663)
In this example, the Virtual Machine ID is 5FC5C385-BD98-451F-B3F3-1E50E06EE663. - Open an elevated command prompt.
- To give the Virtual Machine ID (SID) access to the .vhd or .avhd file, type the following command, and then press Enter:
icacls <Path of .vhd or .avhd file> /grant "NT VIRTUAL MACHINE\ <Virtual Machine ID from step 1> ":(F)
For example, to use the Virtual Machine ID that you noted in step 1, type the following command, and then press Enter: icacls "E:\VMs\VMName\Disk0.vhd" /grant "NT VIRTUAL MACHINE\5FC5C385-BD98-451F-B3F3-1E50E06EE663":(F)
- Start the virtual machine.
More Information
If
permissions on the Hyper-V virtual machine configuration file (.xml
file) are incorrect, the virtual machine fails to start and returns the
following error message:
‘Unnamed VM’ failed to initialize.
An attempt to read or update the virtual machine configuration failed because access was denied.
If you click
See details in the message window, the following error message is displayed:
‘Unnamed VM’ failed to initialize. (Virtual machine 7E77503A-A26B-4BB5-9846-396F49A30141)
‘Unnamed
VM’ failed to read or update the virtual machine configuration because
access was denied: General access denied error (0×80070005). Check the
security settings on the folder in which the virtual machine is stored.
(Virtual machine 7E77503A-A26B-4BB5-9846-396F49A30141)
To
resolve this issue, perform the steps in the "Resolution" section to add
the Virtual Machine SID to the .xml file. For example, run the
following command:
icacls "E:\VMs\VMName\7E77503A-A26B-4BB5-9846-396F49A30141.xml" /grant "NT VIRTUAL MACHINE\7E77503A-A26B-4BB5
Article ID: 133, Created On: 1/9/2018, Modified: 1/9/2018