On 10/25/22 14:11, Greg Woods wrote:
A problem you could run into doing this is licensing. WIndows uses a
variety of methods to detect if a valid product key is being run on
multiple machines, which includes some checks on the hardware. Since a
virtual machine is never going to have virtual hardware that exactly
matches your PC, there's a good chance that, even if you succeed in
getting your native install to run under a hypervisor, Windows may well
consider it an unlicensed copy.
I recently had a Windows 10 VM that this happened to when I just
upgraded Virtual Box, didn't touch the Windows VM at all.
--Greg
Hi Greg,
My Windows 11 Pro VM is not licensed. It won't
let me set up a screen saver or alter my wallpaper.
I do not care. I only use it to research
things for customers. It is not a very nice
OS.
W11 pulled the same thing you talk about where
it only worked once with W10's key until I
changed some virtual hardware, which I do
all the time.
On the bright wide, teh customer has an non-oem
tag on the side of his computer.
But the age of the computer bars me from running
a VM anyway. And he readlly should get a new
computer for what he wants to do anyway.
-T
At last count, I have 13 VM's set up. Some of
them are for test ISO's and USB drives.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
