[SOLVED] E_FAIL (0x80004005) / runtime (-102) on Win7 Host

[Abhishek]

Setup Details:
Host: Windows 7
Guest: Windows XP
VB Version: 3.2.6

I just experienced a weird error with VIrtualBox on a client's network. They are on Windows 7 but they have a printer that requires XP because their type of printer doesn't work on Vista or 7 (not the brand, the actual type from any manufacturer...which is stupid)

When I saw the issue it said "Inaccessible" as the status of VM and the following error was provided on the right side of the program.

Code: Select all   Expand viewCollapse view

Runtime error opening 'C:\Users\COMPUTER_NAME\.VirtualBox\Machines\VM_NAME\VM_NAME.xml' for reading: -102 (File not found.).
D:\tinderbox\win-3.2\src\VBox\Main\MachineImpl.cpp[665] (Machine::registeredInit).
Result Code:
E_FAIL (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

My Solution:
I went into the folder "C:\Users\COMPUTER_NAME\.VirtualBox\Machines\VM_NAME\" and saw two xml files but for some reason they both had suffixes.
1. VM_NAME.xml-prev
2. VM_NAME.xml-tmp
So it simply just couldn't find "VM_NAME.xml" because it technically didn't exist.
I made a copy of the "VM_NAME.xml-prev" file and renamed the copy to "VM_NAME.xml"
Restarted VirtualBox and it worked just fine.

Hope this helps anyone with the same issue.

Thanks .. Your solution has saved my lot of time..
Thanks again Cheers..

[mpack]

Actually, you should use the ".tmp" file if it exists, as that is the newest version of the settings file. As the name implies, the "xxx-prev" file is supposed to be the previous version. This problem happens if VBox crashes before completing the name juggling which it does when writing out an updated settings file.

Btw, VirtualBox stopped using the ".xml" extension for VM settings files back in v4.0.0. Settings files are still xml files, but the ".vbox" extension is now used so that VBox xml files can be easily identified by the host (so e.g. it can be launched by double clicking). In that case the equivalent to the files discussed will be ".vbox-prev" and ".vbox-tmp".

[jaegerj]

I had to find a different solution.

Back Story
I am running windows 7 64bit which shutdown overnight for updates.. in the morning I received this error for one of my virtual machines:
Runtime error opening 'C:\Users\jaegerj\VirtualBox VMs\quickSilver2\quickSilver2.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 did some googling and tried a few different proposed solutions including renaming the virtualmachinename.vbox-prev to virtualmachinename.vbox to no avail.

The Solution
1) Right click the virtual machine and choose to Remove it (if given the option, don't remove the files)

Note: at this point going to Machine>Add and navigating to my virtual machine folder did not help because VirtualBox Manager could not see the .vbox file (even though Windows could see it).. when I pasted the exact address of the .vbox file virtualbox manager told me it did not exist.

2) In windows right-click the .vbox file and choose to open with VirtualBox Manager

3) Now we are so happy we do the dance of joy! (<- why yes, that is an 80's sitcom allusion)

[manjana]

THANKS! YOU SAVE A LOT OF MY JOB.

THANKS THANKS THANKS

[TRAXVP]

Tried the .vbox-prev to .vbox option and no dice!!!! Still got the same error.

Suspecting that this problem was a result of my attempt to export the vm (a 45Gb vmdk) using the "Export Appliance" option on VBox 4.2.18; I decided to try creating a clone of the vmdk to vhd using the Virtual Media Manager and clicking Copy on the vmdk. I chose vhd for kicks. I then changed the VM settings to switch the old .vmdk hard drive for the new .vhd drive and it booted up perfectly, no more E_FAIL 0x80004005 errors.

I don't think its a matter of the file format. Just that the cloning tool cleared up the error with the virtual disk file.

[haytham.med]

I got this:

A differencing image of snapshot {c9e15a55-4722-4a72-9988-44138c191586} could not be found. Could not find an open hard disk with UUID {9f5f6518-7bd7-44d2-9b15-e72132ef4809}.
Result Code:
E_FAIL (0x80004005)
Component:
SnapshotMachine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

What i done:
deleted vbox additions and problem was solved

What i was doing:
attached a swap partition to 2 vbox machines, and i got usb drive error next, windows offered to automatically scan and fix, then i got the problem

[mpack]

I'm not too sure what "vbox additions" might refer to, but neither of the things it might be have anything at all to do with snapshots or hard disks.