In the last couple of days I've had some VM's that had a perfectly valid digital license go "Unactivated" and message from servers seems to be "No digital license found for this device". These VM's have been working for months without issues.
Not changed any hardware - all Windows systems 100% legal - so is this just me or have there been problems. Not changed or updated the HOST OS.
The only one I could activate was creating a Windows 11 Enterprise version for which I have a multi-activation VL license from Windows 7 Enterprise and that key worked - but I don't really want W11 Enterprise as my "Normal system" -- I want to get back to W11 Pro.
In the last couple of days I've had some VM's that had a perfectly valid digital license go "Unactivated" and message from servers seems to be "No digital license found for this device". These VM's have been working for months without issues.
1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
Hard Drives
1TB Samsung EVO 870 SSD
Internet Speed
50 Mbps
Browser
Edge, Firefox
Antivirus
Defender
Other Info
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.
My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
Operating System
Windows 11 Pro
Computer type
Laptop
Manufacturer/Model
Dell Latitude E4310
CPU
Intel® Core™ i5-520M
Motherboard
0T6M8G
Memory
8GB
Graphics card(s)
(integrated graphics) Intel HD Graphics
Screen Resolution
1366x768
Hard Drives
500GB Crucial MX500 SSD
Browser
Firefox, Edge
Antivirus
Defender
Other Info
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.
My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
Thanks for suggestion --
That didn't work and I got various errors such as "Running Non core version of Windows" etc etc .
So what I did was clear the product code entirely :
slmgr /upk
slmgr /cpky (clears from registry)
reboot computer
Then on activation request (activate now) I entered the original product code again -->next-->activate ->this copy of windows has been activated with digital license.
Not sure what the original problem was but problem solved -- might have been caused by updating the HOST OS to linux kernel 6 (was running with 5.xx series -- so Windows might have thought "Hardware change" or something. Marking as solved.
I keep this one as a "base reference" Windows 11 pro almost nothing installed so when things go bonkers with some updates and installs from dev / other insider previews I can "rebuild" from the base ref system.
The Wonders of Ms Windows !!!!! -- perhaps Ms has been learning from "Gandalf the Wizard" (Lord of the Rings) -- sometimes his logic seems more impeccible than Ms's.
Not sure what the original problem was but problem solved -- might have been caused by updating the HOST OS to linux kernel 6 (was running with 5.xx series -- so Windows might have thought "Hardware change" or something.
1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
Hard Drives
1TB Samsung EVO 870 SSD
Internet Speed
50 Mbps
Browser
Edge, Firefox
Antivirus
Defender
Other Info
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.
My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
Operating System
Windows 11 Pro
Computer type
Laptop
Manufacturer/Model
Dell Latitude E4310
CPU
Intel® Core™ i5-520M
Motherboard
0T6M8G
Memory
8GB
Graphics card(s)
(integrated graphics) Intel HD Graphics
Screen Resolution
1366x768
Hard Drives
500GB Crucial MX500 SSD
Browser
Firefox, Edge
Antivirus
Defender
Other Info
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.
My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
Once that was fixed all my other VM's (X 5) all were marked active with digital license.
I think the HOST Linux system with the quite significant changes between Kernel 5.xxx and 6.xxx including loads of firmware and driver changes must have presented itself to Windows as "New Hardware". KVM really flies now on kernel V6.0 and am getting nearly Native speed on (Activated) Windows VM's !!!!.
