Inaccessible - Everything greyed out.

[DrOctavius]

Hi, so my virtual box has been working fine but today i woke up and opened it up and first thing i see is that it's listed as 'inaccessible', although my other vms are working fine, it's just this particular one which i use everyday, i don't really use the others at all. Anyways i don't remember doing much, all i remember is that i powered it off and i might have clicked the x button and closed it again.
I've attached a picture of the error, i really do need urgent assistance as i have work that needs completing that i must access on the vm today. Thank you.

[socratis]

Did you read the error? Where it says "File not found"? I think it's pretty obvious what's going on: the file isn't there.

Can you check for its existence? Is there a "virtualmachine1.vbox" or a "vbox-prev" file in that location?

[DrOctavius]

I'm not sure why the error is stating the F: drive? Yes those two files are there, i'm assuming the virtualbox application is for some reason trying to access the wrong drive? i don't even have F: i think.

[andyp73]

Rename the .vbox-prev file to .vbox

The reference to drive F: in the error dialog is from the VirtualBox build process not your VM.

-Andy.

[DrOctavius]

Ok seems i've fixed the error. i simply changed the file name to what the error was stating and deleted the "-prev" at the end of the file name and it's now working. Thank you for your assistance, my bad i did not think hard enough.
edit: just read your comment, atleast my brain started working before i got spoonfed by you

[mpack]

Ignore the line with the F:\ path, that indicates where in the build tree is the source file which generated the error. The only path you need to care about is the one to your .vbox file.

Speaking of which, I see no "virtualmachine1.vbox" file in that folder. Shut down VirtualBox, go to the folder and rename "virtualmachine1.vbox-tmp" to "virtualmachine1.vbox". This problem indicates that the front end crashed last time before saving changed settings.

[mpack]

Ah. Too late. Renaming .vbox-tmp would have been better as that's the more up to date instance. Renaming .vbox-prev usually works, it depends on what (if any) settings were changed in the last run.

[andyp73]

This might also be a prudent time to remind you of the importance of having backups of both important files within the guest and also the guest itself. Not everything is this easy to solve and when your vm contains urgent work that needs completing you don't want to take the risk...

...but then you knew that already, didn't you!

-Andy.