virtualbox.org

I am getting this error that the machine is inaccessible, see detail below, tell me how to solve it.

Runtime error opening 'D:\VirtualBox VMs\Machine\Machine.vbox' for reading: -103(Path not found.).
F:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long __cdecl Machine::registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Khan296 wrote:I am getting this error that the machine is inaccessible, see detail below, tell me how to solve it.

Runtime error opening 'D:\VirtualBox VMs\Machine\Machine.vbox' for reading: -103(Path not found.).
F:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long __cdecl Machine::registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

The cause appears to be clear.

True but why path not found as I tried on friends computer and it worked but not working on my computer.

It isn't really relevant what paths exist on your friends computer. Does that path exist on yours? VirtualBox says not, in which case you need to correct it. So far you have not given me enough information to tell you how. I don't know what drive D is on your system (if anything), I don't know that the named path exist, and I don't know if the names files exist.

Most likely, your PC has different drive letter assignments. "D" quite often refers to a CD/DVD drive.

Thanks , by following your hint I copy the VM image on D drive and then it worked.
Problem solved.

I'm also facing the same problem, getting the following error. Please help me in resolving this.

Runtime error opening 'C:\Users\Arvind\AppData\Local\Temp\Rar$DIa0.745\CentOS.vbox' for reading: -103(Path not found.).
F:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long __cdecl Machine::registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

If you have the same problem then you can solve it by reviewing the above thread. What else needs to be said? Make the path exist, or correct it.

In that last question, how should the user "correct it"?

@raywood
Don't hijack and try to resurrect a dead thread. Instead open a new one. Where you clearly describe your problem, not isolate a tiny portion of it. We need for example to see the exact error, we need to hear the exact details of how you ended up getting this error (what you did or not).

So, please open a new thread with an appropriate title and a complete description, as I'm going to lock this one. It was already marked as [Solved]...