Upgrade to 7.2.20 made several existing guests Inaccessible

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Old Newbie
Posts: 43
Joined: 31. Oct 2012, 05:08

Upgrade to 7.2.20 made several existing guests Inaccessible

Post by Old Newbie »

I returned to my winter residence and updated my Windows 11 host via MS Update after being away for 3 months. I then installed VB 7.2.20 over VB 7.2.10. This was followed by the installation of the 7.2.20 extension Pack. When I opened the VB Manager, 3 of my guest machines were OK, but the other 5 guests were marked Inaccessible.

See image.

Image

I have no idea if these guests can be recovered or even how to do it.

Any Help would be appreciated.

O.N.
Attachments
VirtualBox_4Qrf4mJc1I.png
VirtualBox_4Qrf4mJc1I.png (51.96 KiB) Viewed 9703 times
multiOS
Volunteer
Posts: 1772
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux, BSD
Location: United Kingdom

Re: Upgrade to 7.2.20 made several existing guests Inaccessible

Post by multiOS »

From the VM Icons in your screenshot, it appears that all of the failing Windows VMs are configured using a Linux Template which may be a clue to the cause of the startup problems.
Old Newbie
Posts: 43
Joined: 31. Oct 2012, 05:08

Re: [SOLVED] Upgrade to 7.2.20 made several existing guests Inaccessible

Post by Old Newbie »

I spent quite a bit of time with AI trying to solve my problem.

Turns out that the inaccessible machines all had a Guest Additions ISOs still mounted in the virtual CD drive. Their UUIDs differed from the 7.2.20 Guest Additions ISO, and the mismatch was making the guests inaccessible.

Editing the .vbox files and removing the Guest Additions entry, followed by using the VBOX Manager to remove the guest after the edit, was required. I then added the guest machine back, and it was now accessible.

Repeated the process for each Guest machine, and everything was restored to normal. Each one started, and after updating the guest additions and ensuring the virtual CD drive was empty, everything was restored.

I want to thank all of the members who took the time to read my post.

O.N.
Post Reply