VM Inaccessible

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Drachenfire
Posts: 2
Joined: 1. Oct 2012, 01:05

VM Inaccessible

Post by Drachenfire »

I was using my VM late last night and everything was fine. When I tried to open it today the VM manager said it was inaccessible, and gave the following details:

Runtime error opening 'C:\Users\Michael\VirtualBox VMs\Ubuntu Linux\Ubuntu Linux.vbox' for reading: -102 (File not found.).
D:\tinderbox\win-4.1\src\VBox\Main\src-server\MachineImpl.cpp[708] (Machine::registeredInit).
Result Code:
E_FAIL (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

I looked through a number of other posts but have yet to find a solution. Any ideas / suggestions would be greatly appreciated ( I don't want to lose several days of work...:).

Thanks
Drachenfire
Posts: 2
Joined: 1. Oct 2012, 01:05

Re: VM Inaccessible

Post by Drachenfire »

SOLVED: to resolve this I started a new VM and pointed it at \<username>\VirtualBox VMs\Ubuntu Linus\Ubuntu Linux.vdi. That's all it took.
Laurel
Posts: 1
Joined: 18. Oct 2012, 00:24

Re: VM Inaccessible

Post by Laurel »

How did you point to the old version when creating a new VM?
BillG
Volunteer
Posts: 5106
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: VM Inaccessible

Post by BillG »

When you get to the hard drive section you select "use an existing virtual hard drive file" and select your existing .vdi.
Bill
Post Reply