To resolve this issue, perform the steps in the "Resolution" section to add the Virtual Machine SID to the. Check the security settings on the folder in which the virtual machine is stored. 'Unnamed VM' failed to read or update the virtual machine configuration because access was denied: General access denied error (0×80070005). If you click See details in the message window, the following error message is displayed: 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:Īn attempt to read or update the virtual machine configuration failed because access was denied. avhd file, type the following command, and then press Enter: icacls /grant "NT VIRTUAL MACHINE\ ":(F)įor 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) To give the Virtual Machine ID (SID) access to the. Note the Virtual Machine ID that is listed in the error 0x80070005 (General access denied error).įor example, consider the following error message: To resolve this issue, add the Virtual Machine SID to the virtual hard disk (.vhd) file or to the snapshot file (.avhd). avhd file, the virtual machine does not start, and you receive the error 0x80070005 (General access denied error) that is mentioned in the Symptoms section. If the Virtual Machine SID is missing from the security permissions on the. This issue occurs if the permissions on the virtual hard disk (.vhd) file or the snapshot file (.avhd) are incorrect.Įvery Hyper-V virtual machine has a unique Virtual Machine ID (SID). The Virtual Machine ID is unique to every virtual machine.This error message references either a virtual hard disk (.vhd) file or a snapshot file (.avhd). ![]() This error message references either the Microsoft Emulated IDE Controller or the Synthetic SCSI Controller.'VMName': Account does not have sufficient privilege to open attachment Error: 'General access denied error' (0x80070005). 'VMName': IDE/ATAPI Account does not have sufficient privilege to open attachment ): Failed to Power on with Error 'GeneralĪccess denied error' (0x80070005). Microsoft Emulated IDE Controller (Instance ID Solution Do not use Unattend.This article helps fix the error 0x80070005 that occurs when a Hyper-V virtual machine fails to start.Īpplies to: Windows Server 2012 R2 Original KB number: 2249906 SymptomsĪ Hyper-V virtual machine may fail to start, and you receive an error message that resembles the following:Īn error occurred while attempting to start the selected virtual machine(s). ![]() In this situation, you may also be interested in how to properly upload a generalized VM. This issue is most often created while you are using sysprep with an on-premises VM to upload a generalized VM to Azure. In Azure, use the Enter System Out-of-Box Experience (OOBE) option in System Preparation tool GUI, or use sysprep /oobe rather than the Unattend.xml file. Sysprep /oobe /generalize /unattend: /shutdown Thus, this situation occurs when an image was prepared for use in Azure, but you specified a custom Unattend.xml file by using SYSPREP with a flag similar to the following command: The configuration options include instructions on how to partition disks, where to find the Windows image to be installed, product keys to apply, and other commands you would like to run.Īgain, custom answer files are not supported in Azure. The answer file is a special XML file that contains setting definitions and values for the configuration settings you want to automate during the installation of a Windows Server operating system installation. Custom answer files are not supported in Azure. The machine is attempting to do an initial boot of a generalized image, but encounters trouble due to a custom answer file (Unattend.xml) being processed. To install Windows, click "OK" to restart the computer, and then restart the installation. The computer restarted unexpectedly or encountered an unexpected error. When you use Boot diagnostics to view the screenshot of the VM, you'll see that the screenshot displays Windows installation failing with the following error: This article provides steps to resolve issues where the virtual machine (VM) experiences an unexpected restart or error while installing Windows.
0 Comments
Leave a Reply. |