I have do perform a Rollback (using Rollback RX) yesterday night. The VMs are located in F: drive which is not affected by Rollback.
I have opened the VirtualBox, clicked machine > add and then I have tried to select one of the VMs (IE11 - Win7.vbox)
I get the following error message:
Failed to open virtual machine located in F:/Virtual Machine/IE11 - Win7/IE11 - Win7.vbox
A differencing image of snapshot {41941d27-917f-4882-a368-049cae701f3d} could not be found. Could not find an open hard disk with UUID {bde68043-8ff1-492b-a27d-b1134367a3a2}.
veg wrote:The VMs are located in F: drive which is not affected by Rollback.
You mean that you don't take a backup of the VMs with Rollback, right?
veg wrote:I have opened the VirtualBox, clicked machine > add
Why did you try to "Add" a VM? Wasn't that VM already present/registered with VirtualBox?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
veg wrote:I'm currently installing everything again...
That won't change the situation...
I need to see the following as a first step:
The file "C:\Users\<you>\.VirtualBox\VirtualBox.xml". Note the period in the ".VirtualBox".
The output of the following command when run from the Command Prompt:
dir /s "F:/Virtual Machine/"
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Of course, it will... it worked.
Before doing that, I managed to fix the cyber ops VM using this guide http://blog.htxiong.com/2013/06/resolve ... -open.html
Then I wanted to apply the same method on the Win7 VMs but those had snapshots... so I tried to create a new UUID for the hard disk and for each snapshot. I have updated it but it didn't work. So I have deployed 2 new VMs.
Last edited by socratis on 30. Sep 2019, 23:06, edited 1 time in total.
Reason:Removed unnecessary verbatim quote of the whole previous message.
I have no clue what you're describing here, only that you linked to a 6-year old blog post...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:I have no clue what you're describing here, only that you linked to a 6-year old blog post...
The solution of this 6-year old solved the issue with the Cyberops VM.
As for the Win7 VMs - I have created a new UUID for the virtual hard disk and for each snapshot and then I edited the file, but it didn't work.
Here is an example:
cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe internalcommands sethduuid "D:\NewVM\myDisk1.vdi" >>> you will get a new UUID for the vdi file (hard disk / snapshot)
