Virtualbox doesn't open - error VERR_VD_IMAGE_READ_ONLY


I had tried to install an OS named Veos with virtual box ,but when I had finished the installation ,I can not open the wirtual machine Veos ,and I had this output: Failed to open image 'C:\Users\Takfarinas\VirtualBox VMs\AristaFiles\vEOS-lab-4.16.6M.vmdk' for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY). Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY). PIIX3 cannot attach drive to the Primary Master (VERR_VD_IMAGE_READ_ONLY).

Code d'erreur : E_FAIL (0x80004005) Composant : ConsoleWrap Interface : IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

asked on Stack Overflow Jun 2, 2016 by Zaaf Lafalaise • edited Jul 27, 2020 by holzkohlengrill

5 Answers


Right click on the .vdi file . Click on properties . Just uncheck Read only . And start VirtualBox with administrator priviligies. This done the trick for me . :)

answered on Stack Overflow Nov 19, 2017 by Ivanp

It seems you use Windows OS, as Host OS. Try to run Virtualbox as Administrator. Right click on Virtualbox ICON and "run as Administrator". Or change the rights of Virtualbox. Hope it helps.

answered on Stack Overflow Jun 2, 2016 by Tech-IO

Error message:

Failed to open image 'C:\Windows XP Mode\VirtualXP.VHD' for writing due to wrong permissions

Things to try:

  1. ?? Grant "Full control" permission to the user (properties > security)
  2. ?? Run VirtualBox as administrator
  3. Solution: Unmount the virtual hard disk in your current OS (by clicking on "Eject")

How to unmount the virtual hard disk:

enter image description here

answered on Stack Overflow Apr 23, 2018 by Amirhossein Mehrvarzi • edited Dec 19, 2018 by JohnB

I have suffered from the same problem recently. I changed the permissions of my visual disk image.Then It works.

1.Right click your .vdi file.
2.Select property item in the popup menu.
3.Swith to security tab.Select users then click Edit button.
4.Check on full control.

answered on Stack Overflow Sep 12, 2016 by niaomingjian

This happens on our work airgap machine when someone forgets to shut down the virtual machine at the end of their session. Restarting the machine resolves the issue, for me.

answered on Stack Overflow Mar 30, 2017 by omikes

User contributions licensed under CC BY-SA 3.0