New to this, but Win 7 Pro 32 seems to run in VirtualBox (5.1.10) fine. I understand Win 10 becomes tied to the hardware. How does this effect creating a VirtualBox on a different machine? Or, running Win 10 only as a virtual box?
Any insight will be appreciated.
Carl Lindner
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Windows activation has been 'tied to the hardware' for a long time, since XP if memory serves. Assuming you're not using OEM or volume licences, that is. Windows 10 is no different.
Running Windows 10 in a guest VM means it's tied to the virtual hardware in the VM including the virtual CPU ID. But you should be able to change things like the allocated memory, virtual disks and so forth without triggering a reactivation. If you do trigger one, it might re-activate online, it might require a call to Microsoft.
Because VMs can be cloned and copied you obviously can't have 20 VMs all using the same licence. However since the CPU ID will be different for each, it almost certainly wouldn't work anyway.
There is a discussion of it here:
http://www.tenforums.com/windows-insider/38992-question-about-licence-activa..."
Thanks Alan. It gets me started.
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Alan Bourke Sent: 12/02/2016 4:46 AM To: profoxtech@leafe.com Subject: Re: [NF] VirtualBox and Win 10
Windows activation has been 'tied to the hardware' for a long time, since XP if memory serves. Assuming you're not using OEM or volume licences, that is. Windows 10 is no different.
Running Windows 10 in a guest VM means it's tied to the virtual hardware in the VM including the virtual CPU ID. But you should be able to change things like the allocated memory, virtual disks and so forth without triggering a reactivation. If you do trigger one, it might re-activate online, it might require a call to Microsoft.
Because VMs can be cloned and copied you obviously can't have 20 VMs all using the same licence. However since the CPU ID will be different for each, it almost certainly wouldn't work anyway.
There is a discussion of it here:
http://www.tenforums.com/windows-insider/38992-question-about-licence-activa tion-vm.html"
-
Alan Bourke -
Carl Lindner