I just saved a snapshot and shut down VB. After re-booting the Mac on which VB is running, I launched VB and tried to go back to this Windows 10 VM. That's when this message came up. I did see this somewhat related post (viewtopic.php?f=6&t=62874&start=15), but it doesn't seem to be the same thing.Cannot attach medium '/Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso' {0731d047-34ef-4091-bb0c-6f607958b732}: medium is already associated with the current state of machine uuid {81d32831-0d07-4e86-9566-59c1e6389f40}!.
Result Code:
VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component:
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
I recently (in the last couple of days) updated Win10 to 1703 (the Creator Version or whatever it's called) and after that update I recall searching the VB forums because the VM guest could not find the bridged folders on the host. After I re-ran the GuestAdditions file, all was well – I thought. It's probable that I had never rebooted the VM after the one re-boot associated with the re-installation of GuestAdditions.
I've been using VB for several years, but I'm not a power user by any means. (I say that so you don't assume I'm sharper than I am when you offer help :) ).
Host: Mac 10.10.5 (Yosemite)
Guest: Win10 v. 1703
VirtualBox: 5.1.22 r115126
Thanks for any help you can offer.