If you want to create a copy of your virtual USB key and use the 2 vmdk files at the same time, then just convert the ".vmdk" file to the same format. However, by default, you can't use 2 virtual hard disks which have the same "uuid". If you open the "vmdk" file with Notepad ++ (for example), you will see that a unique identifier (called "uuid") is present in it. Note that the command only takes a fraction of a second.Ĩ. VixDiskLib: Failed to initialize PhoneHome library.
Vmware-vdiskmanager.exe -n "H:\Win 10 v2004 Pro 圆4\virt-usb-key.vmdk" "H:\Win 10 v2004 Pro 圆4\virt-usb-key-renamed.vmdk" Then, use the "-n" parameter of the "vmware-vdiskmanager.exe" program by specifying : To correctly rename a ".vmdk" file, open a command prompt and move back to the VMware Workstation folder :Ĭd "C:\Program Files (x86)\VMware\VMware Workstation" Indeed, as you can see, its name is also inside the ".vmdk" file. To rename a ".vmdk" file, you can't simply rename the file from the file explorer.
We generated the license without a problem.Īfter restarting the virtual machine, the free license no longer works as the original GUID (Registered GUID) has changed (Flash GUID) and now ends with "2D80E".
This will probably not be a problem in your case, but in our case, we wanted to test an evaluation software whose license is linked to the unique identifier (GUID) of the USB key where it's installed.Īs you can see, the identifier at 1st start ended with "ADFC5".
Go back to the same place and you will see that the value has changed. Shut down the virtual machine and restart it. Then, use the horizontal scroll bar and look at the hexadecimal value (a sequence of numbers and letters) at the end. In the "Details" tab, select the "Device instance path" item. To see this change, just launch the Windows Device Manager and open the properties of your virtual USB key. This can pose a problem in a specific case : if you are using a program whose license is linked to the unique identifier (GUID) of the USB key used. Automatic change of the virtual USB key identifier (GUID)Īlthough this is not a problem for the majority of you, be aware that the GUID of this virtual USB key will change each time you start your virtual machine.
The "Plop Boot Manager" boot manager appears and we select "USB" to boot from our virtual USB key.Īs expected, our virtual machine boots on our virtual bootable UBCD (Ultimate Boot CD) USB key.Ħ. However, in summary, our virtual machine is configured to use a standard BIOS (and not the EFI firmware which is not supported by UBCD) and we use the "Plop Boot Manager" boot manager in iso format since the boot on an USB key is not possible from the phoenix BIOS of VMware Workstation. To boot a VMware Workstation virtual machine on a (real) USB key, refer to our " VMware Workstation 16 / 15 - Boot on an USB key" tutorial.
The virtual bootable USB key has been created. The creation of the bootable USB key is done without problem. You can therefore for example test the creation of a bootable USB key in a virtual machine without having to buy a real USB key for your tests.įor the demonstration, we are going to create a bootable USB key from the "Ultimate Boot CD" live CD that many IT scientists know. Since the ".vmdk" file is plugged into the USB 2 controller of your virtual machine, programs that you will use in your virtual machine will see this ".vmdk" file as a real USB key.