Snapshot is not obvious in the main interface. It's buried just like simple Win10 settings. Click the sliders for the VM --> Snapshots --> RIGHT click the Current State --> Take, Everything is going Win10. Three dialogs deep just to change the screen saver. :rolleyes:
NewMelle
You can switch to the 'snapshots view' via clicking on the three blue dots rhs of the VM name and selecting 'Snapshots'. Afterwards you'll get dedicated buttons to taking / restoring snapshots etc. and also the snapshots tree in the center. Quite convenient... well, when it works I mean.
Thanks to the last hung snapshot this is what I was presented with when I fired up VB again. Machine inaccessible.
Machine UUID {8a98c12b-bebe-4758-8fb9-20783ba6d117} in 'X:\VirtualBox_VMs\Win11 Fresh\Win11 Fresh.vbox' doesn't match its UUID {65b6a911-d3cc-4605-8714-14c5544c09b2} in the registry file 'C:\Users\neal\.VirtualBox\VirtualBox.xml'.
NewMelle
I don't know your individual case but UUID problems usually occur when manually copying VM files instead of properly 'importing' the machines from the VBox GUI. There is a dedicated 'Machine -> Add' option for that. It should ask you whether you want to regenerate UUIDs if there is a conflict.
There is a 'central' file VirtualBox.xml that aggregates data about all the currently registered VMs, all their disks UUIDs (one per individual snapshot) and machines UUIDs, among other stuff. This data is also duplicated in the VM's .vbox file and should always match. If you want to manually move VM files around you should remove the machine (right click -> Remove) and then after doing all the manual changes (like recovering the older version from backup, etc.) re-add with 'Machine -> Add'. Also, each time you create a snapshot some new UUIDs are added in both places.
The option to 'clone' from the GUI should automatically re-create all the UUIDs to not to conflict with the original, so its not just copying the files verbatim.
You can also take a pick on what disks (and their differential images) are currently registered and to which VMs and snapshots they are attached via 'File -> Tools -> Virtual Media Manager'. It also allows for a lot of operations on these disks via its GUI.
If you are sure that your VM copies are consistent, conflict-free and self-contained (not referring outside their directory, like when you do a 'linked clone'), you can try removing (not deleting!) all the machines, removing all the settings for VBox and re-importing the .vbox files for your VMs and there should me no more conflicts.
Other than that, I can strongly recommend asking directly on the VBox forums, there is a really helpful and involved community that will try to help you for sure:
https://forums.virtualbox.org/index.phpThey helped me numerous times there. Should give much better results than just googling the answer, as your problems are
definitely not typical, especially the one with hanging snapshots. I've been using VirtualBox for over 10 years, I have currently over 50 different VMs of all sorts registered just on my current machine, with no conflicts and still:
never had any problem with snapshots like you do.
Fingers crossed!