I am curious how license on a Win 7 VHD Native boot would work? Especially when the goal is to be able to move the VHD to different hardware easily. How do Naitve boot VHD Activations get done/ stored? Is it hardware attached or VHD attached?
I wonder if users with oem activated Win7 machines will get a new serial or have to somehow submit the serial from the coa sticker. since all the daz loader people don't have coa stickers they won't be able to use this offer
Not changing the protocol at all would mean to give it away for free from the beginning . That would be new.
In my opinion, that fact that this build utilizes the GVLKs posted by MS directly and activates against existing KMSv6 protocol seems to be a good indication that they have not made significant changes with respect to KMS activation for Windows 10
There is no KMSv7. U can simply decompile the KMS Host Update and see what happens. U will not find an updated Proto.
Afaik the gVLK change the Licensing Channel and ActivationID of a SKU and are not directly involved in activation itself . For that reason generated keys work likewise, since there is no approval.
No I dont think MS will do that. Designing a new KMS protocol is not hard to do. but a new protocol is surely hard to decrypt, so they'll happily implement it, and laugh at us while we are suffering.
Right. The logic that I am using for this assumes that this build (10176) is an RTM candidate. Am I wrong in assuming that RTM candidate builds would include any/all new activation mechanisms? The whole point of an RTM candidate would be that it includes everything as it would be in the "signed-off" version of Windows, no? What good would it be testing a build for RTM and then injecting something new (like new activation mechanisms) before signing off. Surely the new activation mechanisms would be included as a part of the test process for RTM candidate builds. If this build is not an RTM candidate, then my entire basis for this would be wrong. It honestly makes little difference to me - I am just really curious about the inner-workings of this process.
When recalling the hard process of the cracks here to reverse KMS v5 and v6 (what involved to understand encryption and obfuscation) ... i hardly doubt you see the changes at first look .
With older versions of Windows even the RTM candidates didn't include updated KMS protocols AFAIK. It was only the final RTM version that included the changes. If Microsoft don't update the protocol then consider yourself lucky, but there's nothing stopping Microsoft from pushing out an update after RTM and you might not be able to opt out either.
Still remember how long it needed after the (relatively early) RTM Leak of Win 8 to develop an Emulator for v5. Till that appearance all activation solutions based off a slimmed down Qemu KMS Host by heldigard. Weird good ol' times.