[solved] Can't start VB, NS_ERROR_FAILURE (0x80004005)

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Androix
Posts: 8
Joined: 19. Jul 2016, 08:16
Primary OS: Linux other
VBox Version: OSE Debian
Guest OSses: Win10

[solved] Can't start VB, NS_ERROR_FAILURE (0x80004005)

Post by Androix »

Hello everyone

Currently I'm trying to start VB but it doesn't work. An hour ago I was able to start it but because of another issue (the network folders couldn't be opened and are still disconnected) I had to restart my system. I did it twice but nothing happend, so I also ended the VB-processes with the system monitor. Now the following error message occured:
The selected virtual machine is inaccessible. Please inspect the error message shown below and press the Refresh button if you want to repeat the accessibility check:

Runtime error opening '/media/drives/Windows 10/Windows 10.vbox' for reading: -138(Device or resource is busy.).
/home/vbox/vbox-5.0.2/src/VBox/Main/src-server/MachineImpl.cpp[736] (nsresult Machine::i_registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
What do I have to do to make it work again?

Regards
Last edited by Androix on 6. Jan 2017, 12:26, edited 1 time in total.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Can't start VB, NS_ERROR_FAILURE (0x80004005)

Post by socratis »

Androix wrote:'/media/drives/Windows 10/Windows 10.vbox' for reading: -138(Device or resource is busy.).
Reboot. Host and guest.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Androix
Posts: 8
Joined: 19. Jul 2016, 08:16
Primary OS: Linux other
VBox Version: OSE Debian
Guest OSses: Win10

Solution

Post by Androix »

Thank you for your help, socratis. Finally my boyfriend was able to solve the problem which was caused by a faulty network folder. By that I was also unable to connect the other network folders.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: [solved] Can't start VB, NS_ERROR_FAILURE (0x80004005)

Post by socratis »

That's not what the error was talking about, unless you have placed the VM in a network drive, in which case the networked .VBOX file could not be found. Yeah, that would make sense...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply