current mint 18 inacessable?

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
jbsone

current mint 18 inacessable?

Post by jbsone »

Hello - All,
Runtime error opening 'C:\Users\jbsone\VirtualBox VMs\mint 18\mint 18.vbox' for reading: -102 (File not found.).
F:\tinderbox\win-5.2\src\VBox\Main\src-server\MachineImpl.cpp[741] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
This has stumped me completely...I've been running mint for months...Never hadthis problem...Is this a virtualbox error or mint.. I'm t hinking it might be vb?
Thanks for help/suggestions,
John in Dallas
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
ajgringo619

Re: current mint 18 inacessable?

Post by ajgringo619 »

Looks like a VB error, but the 'file not found' error could mean something else. Did you recently upgrade the system/VB software? What version of Windows is your host? My Linux repo just upgraded me to 5.2.18 today.
jbsone

Re: current mint 18 inacessable?

Post by jbsone »

Thanks for your response,
running win 7-64...Upgraded vb when it said new version available..no other software installations. vb upgrade went very well and this mint version ran perfectly for months.l..I'll try and reinstall vb perhaps that will help..
User avatar
JerryF
Level 16
Level 16
Posts: 6571
Joined: Mon Jun 08, 2015 1:23 pm
Location: Rhode Island, USA

Re: current mint 18 inacessable?

Post by JerryF »

You may need to update the extension pack of VB also.
gm10

Re: current mint 18 inacessable?

Post by gm10 »

jbsone wrote: Wed Aug 15, 2018 2:13 pm Runtime error opening 'C:\Users\jbsone\VirtualBox VMs\mint 18\mint 18.vbox' for reading: -102 (File not found.).
Surprised nobody pointed to the obvious explanation though: That file is actually missing (check in explorer).
Locked

Return to “Installation & Boot”