My host OS is Linux. In VirtualBox, there are two OSes: Windows 10 64-bit and Windows 10 32-bit. "64-bit" has been activated, but "32-bit" has not. If I activate "32-bit", will "64-bit" be deactivated? I have only one valid product key.
The license is linked to the Machine UUID which is held in .vbox file typically in the$HOME/VirtualBox\ VMs/<VM name>/<VM name>.vbox
You can (in the same VM) remove the Virtual disk (in Settings > Storage), create a new one, install 32 bit and it will activate. This is analogous to swapping a physical disk in a real machine. You can then swap these virtual disks back and forth.
If you use 2 separate VMs they will have separate Machine UUID (as VirtualBox will not let you have 2 VMs with the same Machine UUID) so you would need 2 licenses.
Last edited by lx07; 18 Jun 2019 at 06:48. Reason: file suffix is .vbox not .vhdx
Do you mean I cannot have both 32-bit and 64-bit activated in the same VirtualBox?
If so, can I switch between them?
Hi folks
I'm not sure if you can run 2 VM's with the same uuidd at the same time -- however with vmware if you move / copy a VM to another machine / directory at first boot of the VM say I MOVED IT rather than I COPIED it when you see the inital prompt. This preseves Windows activation etc. In VBOX you might have to manually edit the uuidd in a config file --I'm not a VBOX user but I imagine it's similar in principle.
The EULA (Windows) also restricts you to ONE Windows copy per machine so using 2 concurrently (assuming they work) would be illegal under the EULA license -- however I doubt whether Ms would bother in this case as you have an original Windows license and are not trying to create or sell Pirate software.
Cheers
jimbo
Hi there
I'm not a VBOX user -- so I would address that question to VBOX users -- however I can't see any problem with running a VM of a 32 bit windows system and a 64 bit windows system if it's in the same retail package -- not sure why you would want to but people do all sorts of things with their systems so not for me to say other than unless you are running really onld legacy hardware there doesn't seem any point on running 32 bit windows any more.
with VMware you get the prompt at first boot of a moved / copied VM so the case doesn't arise --howver there must be some uuidd / guuid info in some configuration file somewhere.
in vmware it's in the config.vmx file : (ON THE HOST -- not within the VM itself or the Virtual hard disks).
it's a text file so you can open with notepad etc.
It's good to know this as you can also configure the VM with all sorts of extra options that don't appear in the standard "Virtual Machine" wizard or menu screens.
......................................
ethernet0.present = "TRUE"
serial0.present = "TRUE"
extendedConfigFile = "CentOS 7 64-bit.vmxf"
floppy0.present = "FALSE"
gui.lastPoweredViewMode = "fullscreen"
uuid.bios = "xxxxxxxxxxx"
uuid.location = "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"
---------------------------------------
you need to look for that type of string of numbers somewhere - note these are unique to each VM -- your machine will generate a valid uuid for its mobo bios and os.
cheers
jimbo
Last edited by jimbo45; 18 Jun 2019 at 07:33.
I found the following in this file "Windows 10 Version 1809.vbox-prev".
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.15-linux">
<Machine uuid="{xxxxxxxx-xxxx-4ad4-882c-9c8053ddd8e7}" name="Windows 10 Version 1809" OSType="Windows10_64" snapshotFolder="Snapshots" lastStateChange="2019-06-18T09:14:50Z"> <MediaRegistry>
<HardDisks>
<HardDisk uuid="{xxxxxxx-xxxx-4497-bea5-cb6beaaf2cfb}" location="Windows 10 Version 1809.vdi" format="VDI" type="Normal"/>
</HardDisks>
------------------------------------------------------------------------------------------------------
I found the following in this file "Windows 10 Version 1809 (32-bit).vbox-prev".
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.15-linux">
<Machine uuid="{xxxxxxxx-xxxxxx-4180-ad23-a63ae65b26cc}" name="Windows 10 Version 1809 (32-bit)" OSType="Windows10" snapshotFolder="Snapshots" lastStateChange="2019-06-17T14:22:29Z">
<MediaRegistry>
<HardDisks>
<HardDisk uuid="{xxxxxx-xxxx-4ef1-bfcf-67b8d6777664}" location="Windows 10 Version 1809 (32-bit).vdi" format="VDI" type="Normal"/>
</HardDisks>
The.vbox-previf just an old version of.vboxit keeps as a backup in case something goes wrong and you want to revert. If you right click on the.vboxwhich is the blue cube in your picture you should be able to open it in a text editor
(or usenano ~/VirtualBox\ VMs/Windows\ 10\ 1803\ 64\ bit/Windows\ 10\ 1803\ 64\ bit.vbox)
The digital license is based on the Machine uuid you found in the .vbox-prev
64 bit<Machine uuid="{4xxxxxx-xxxxxxxx"
32 bit<Machine uuid="{2xxxxxx-xxxxxxxx}"
I suggest you edit out of your post the full UUID as this can be used to activate a Virtualbox VM and your license may be blocked.
If one is licensed and one not you can just always use the licensed VM and change the attached disk through Settings > Storage.
If you do this and look at the.vboxfile you'll see theHardDisk uuidchange but not theMachine uuidwhen you do this. The VM can run with either disk attached and it will be activated (although not at the same time obviously as it is impossible to simultaneously boot from 2 disks).
This is like swapping disks in a real PC whereas using 2 VMs is like to separate PCs that you need separate licenses for.
You could even attach both disks to the same VM at the same time and dual boot as you would on a physical PC. You would then choose at boot time which disk to boot.
Last edited by lx07; 18 Jun 2019 at 06:47.
Quote
