XPost: alt.comp.os.windows-11
On Mon, 2/24/2025 5:30 PM, candycanearter07 wrote:
rbowman <bowman@montana.com> wrote at 04:35 this Sunday (GMT):
On Sat, 22 Feb 2025 14:48:07 -0500, Joel wrote:
Admittedly, though, they didn't lie about 10 being the last real version >>> ever. Because a (previously upgraded) 7 key will install 11 on cutting
edge hardware or a VM.
When I was on the Insiders channel they pushed out a 'Windows Next'
update. It wouldn't install and they quickly reverted it. That was over a
year ago and I haven't heard any more about a 'next' or 12.
I think they're too busy chasing the AI unicorn through the fields of
clover at the moment.
I honestly wouldn't be too suprised if MS started making Windows itself
a subsciption that got continuously updated.
Back in 2015, WaaS was posited as the endpoint for the ecosystem.
It is now 2025, and we're still floating that balloon ?
How long does it take to do frog boiling (a critter that does
not escape a boiling pot if the temperature is raised gradually,
instead it croaks rather than hop out) ? Let's find out.
https://en.wikipedia.org/wiki/Boiling_frog
Maybe they've figured out that the pot would be empty if they did that. Although it's true that some people will pay for almost anything
shoved through their letterbox.
*******
And you don't install just any old key on a VM. Microsoft Tech Support
do not support maintenance issues for VM-linked keys. There is a
specific product you're supposed to be buying, if wishing to
license the OS while it runs in a VM. You can't just take the
license key off the back of a cereal box and enter that -- the
reason is, if the key is "lost", the Tech Support person
will give their rendition of "tough Beanz". They won't do a
thing for you. With the correct key (no idea what Enterprise
product that would be), then you will get a better response from
them. Someone here lost a key in a VM already, and they recount the
response they got when trying to restore it. It's sufficient to
modify some identifier used in the VM to upset the activation
of the key -- making a VM "more brittle" than bricks&mortar
real computers with their NIC MAC address and other hardware
details.
An example of a key, would be a "Retail SKU" where the price is
double the normal OEM key, but you get the right to "move" the
license from one machine to another. Such a key could be put
on a VM where the identifier got modified by accident or
abuse. The key when re-applied to the VM, would
"look like it was being moved". Whereas the more normal OEM
keys floating around, are unlikely to have that property (can't
be moved).
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)