Every time I start VirtualBox Manager, I get a "VirtualBox - Warning" with the message about "image files not currently accessible". (See attached image.)
When I click the 'Check' button, I get a hierarchical list of GUIDs for each VM, with one of them highlighted. (See attached image.) There is no other information given.
How do I fix this problem? How can I find out what is wrong with the highlighted GUID file?
How to solve "image files not currently accessible" problem?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: How to solve "image files not currently accessible" prob
Click on the Optical Disk tab in your second screen shot and see what it is that is missing.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: How to solve "image files not currently accessible" prob
Quite often, the problem is that you updated the VirtualBox software while the old GAs was still mounted in a VM. VBox detects that the ISO has been overwritten: same name, different content. I'm pointing this out in case you're puzzled by seeing "VBoxGuestAdditions.iso" is the missing ISO, which is still present with the same name and path.
Re: How to solve "image files not currently accessible" prob
The 'Optical Disk' tab?! Why the ... Oh. It has a different icon. And I'm guessing that's not the standard 'optical disk' icon. I never would have caught that. I assumed the selected/highlighted item in the 'hard drives' tab was the culprit. (Why else would it be highlighted?)Perryg wrote:Click on the Optical Disk tab in your second screen shot and see what it is that is missing.
Thank you, Perryg, for setting me on the right track!
Re: How to solve "image files not currently accessible" prob
You were mostly right. It was an .iso for another software package I installed, and I never 'ejected' that disk.mpack wrote:Quite often, the problem is that you updated the VirtualBox software while the old GAs was still mounted in a VM. VBox detects that the ISO has been overwritten: same name, different content. I'm pointing this out in case you're puzzled by seeing "VBoxGuestAdditions.iso" is the missing ISO, which is still present with the same name and path.
Thanks for the insight.