This info still can be used when/if a Windows 8/Server 2012 KMS Host key leaks, until then this Hyper-V KMS vhd package can be useful to trying to understand KMS activation, ways to fake client CMID requests
We're going to have to wait until another VM activated with a 2012 host key is shared because any leaked host key will have its allowed activations instantly used up and will not be of much use.
not very useful, or not useful at all. If we could know what we are looking, that might be just a validation transaction or just random data with nothing but noice. How did you ended up with that?. Maybe that could really help. I was taking a look at the sppsvc service and there isnt much differences between this and 7, so technically should be the same algo with some modifications.
I agree with you. Everything is already "inside the box" ! just a algo modification. The main problem is the following: sppsvc.exe use ADVAPI32.dll (the windows crypto dll) & this dll have a lot of crypto functions
ADVAPI32.dll doesn't seem to be modified by the Hotfix Windows6.1-KB2691586-v9-x64 to include KMS Host support for Win8/Server2012 the files modified by the hotfix: For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2 File name File version File size Date Time Platform Service branch Pkeyconfig.xrm-ms Not applicable 1,024,080 30-Jun-2012 13:12 Not applicable Not applicable Sppobjs-spp-plugin-manifest-signed.xrm-ms Not applicable 11,758 30-Jun-2012 13:16 Not applicable AMD64_MICROSOFT-WINDOWS-S..Y-SP Sppobjs.dll 6.1.7601.22035 1,091,584 30-Jun-2012 12:53 x64 AMD64_MICROSOFT-WINDOWS-S..Y-SP Security-spp-ppdlic.xrm-ms Not applicable 3,787 30-Jun-2012 13:12 Not applicable AMD64_MICROSOFT-WINDOWS-SECURITY-SP Sppsvc.exe 6.1.7601.22035 3,930,112 30-Jun-2012 12:50 x64 AMD64_MICROSOFT-WINDOWS-SECURITY-SP
I am wondering how far along the CN are with an emulated KMS Server. The latest CN public KMS activates Win8 Pro/Ent but refuses to activate Win7 Pro. If the CN KMS Server was a legit server it should also activate Win7/Vista. I think I did see some posts mentioning Server2012 activation so it should be Channel C. Anybody got a Win7 Ent to test activation against the CN Public KMS?
I agree too but, what I mean is: The new sppsvc.exe, like the old one, depends of advapi32.dll. That mean that everything we search is : - Within the new sppsvc.exe or sppobjs.dll or - The new sppsvc.exe/sppobjs use a existing crypto function of advapi32.dll
Was over at macrohard and noticed they were talking about what re-arms do on activated windows 8 (apparently it disables them and gives them a new CMID) Code: It resets the activation state, you will not be activated after you run a ReArm, it also resets the CMID for VL to make it a unique instance So for home KMS players, might just need a looping re-arm script, which de-activates then re-activates the same machine via KMS, 25 times in a row.
Now that I think about it, an external powershell script from the host machine could handle all that without touching the VM. Figure at most 5 minutes per cycle, maybe 2 hours maximum run time. (but could be much less) VM would only need a startup script with -ato command , -dli to verify activation, then -rearm and reboot. Probably happen so fast the machine never shows the login screen. When the powershell script detects the reboot event, it +1's it's counter til 25 is hit. EDIT: I'm guess it could be written to be self aware and run from inside the VM as well, still knocking the idea around in my head. Probably just need to use a txt file or registry key to track the counter between reboots. Simple stuff. It'll be KISS enough that readers could just plop the script into their own VM's and that would be that for the client-end.