Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).


  1. neel
    April 24, 2022 @ 2:22 pm

    thank you! the first method worked perfectly.


  2. Arash
    March 4, 2022 @ 3:19 pm

    Thank you so much … using method one saved me ton of time and frustration


  3. Rubén Herrera
    February 1, 2022 @ 6:11 am

    It is easier, just clone the virtual machine and open the new virtual machine (clone), if it rises without problem then delete the previous virtual machine and you are done. This worked for me.


  4. Bob Gezelter
    January 25, 2022 @ 3:17 am

    A small shortcoming in this article, there are situations which case 1 is not productive, but case 2 is gargantuan overkill.

    I recently encountered an example. While running a VirtualBox VM with the files located on an external eSATA drive, the eSATA cable unplugged. The VirtualBox VM failed. When the cable was reconnected, it did remount without intervention, yielding the 0x80004006 error.

    The remediation is straightforward, and with all due respect, should be included in this article.

    If simply reSTARTING the Virtual Machine does not work. The next steps should be:

    – Exit the VirtualBox Manager
    – Verify that the volumes with all of the Virtual Box files, including virtual disks, are mounted and available
    – Restart VirtualBox Manager
    – Use the VirtualBox Manager to restart the virtual machine.

    A much lower risk alternative to a re-installation.


  5. Alf
    December 6, 2021 @ 12:42 am

    Thank you so much, it worked


  6. Pawan
    August 25, 2021 @ 10:59 am

    Thanks it helped by just clicking on discard saved


Leave a Reply

Your email address will not be published. Required fields are marked *