Page 1 of 1

Don't know were to start. Error 0x80004005

Posted: 1. Mar 2017, 13:57
by Obsolete
Hello need help

I suddenly ran out of disk space on desktop! and Win 10 froze in VM. I look at google but am far from knowledgeable using Linux or VirtualBox.
This is the error in full I got. I know I should have kept a backup I have got a shear folder but was silly and started to save data on desktop and C: drive

I did take a snapshot before but that don't seem to roll back!

Folder in VM Logs Snapshots WIN10.vbox WIN.vbox.prev WIN.vbox.xml-prev

In logs folder there four .log files
In Snapshots folder there a .vdi file

The selected virtual machine is inaccessible. Please inspect the error message show below and press the refresh button if you want to repeat the accessibility check
Have press the refresh button number time nothing happens.
Document is empty.
Location: '/home/ME/VirtualBox VMs/WIN10/WIN10.vbox', line 1 (0), column 1.
/build/virtualbox-mnp3zF/virtualbox-5.0.32-dfsg/src/VBox/Main/src-server/MachineImpl.cpp[740] (nsresult Machine::i_registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Can this be fixed?

Thanks

Re: Don't know were to start. Error 0x80004005

Posted: 1. Mar 2017, 15:33
by Perryg
Is "WIN10.vbox" empty? If so look at "WIN10.vbox-prev" and see if it has content. If so than delete the "WIN10.vbox" and rename "WIN10.vbox-prev" to "WIN10.vbox".

Re: Don't know were to start. Error 0x80004005

Posted: 1. Mar 2017, 15:59
by Obsolete
Perryg 8) 8)

Thanks didn't know could open them up look inside. And yes WIN10.vbox was blank no text how did you know?

Many Thanks Perryg

Re: Don't know were to start. Error 0x80004005

Posted: 1. Mar 2017, 16:07
by Perryg
Couple of things pointed to it being blank. First the way the guest was terminated which will cause it to be blank, but more importantly the "Document is empty." was the deciding factor.