He never said i have created super keygen for Windows 8 and 8.1. Just implied some other clever guys. So i rather call him noob who is fooled by others. I don't think he is doing this for attention. He have more than enough attention for his leaks for long time. No need to rediscover America.
No. Just no. His keygen generates a key, but there's no way to activate it. The activation process is much different than the key generation process. Leaking iso files that MS hands you is much different than an MS engineer giving you the algorithm for phone activation confirmation id generation. He obviously has a connection with an OEM, not MS.
The issue as I see it is that he's posting about it as if it's something new and different that he might release, as if he's trying to take credit for it. He even called it a "keygen" in his own post, even though it doesn't generate valid keys. That plus we don't want people posting fake keys because then we can't easily tell which ones are real. We might end up having to create a new rule so that nobody can post or link to any keys unless you're a trusted known leaker.
no harm with that, well except those with the footprint on their forehead. It's tough out there, go hard or go home I say
Yeah, I suppose you have a point, but I still sympathize with those that helped him get to where he is now and essentially got stabbed in the back. Oh well.
That's corporate politics, you are not mean, and you are dead. ....... doesn't mean you won't die if you were mean or very mean.
Watermark gone !!! I have installed MICROSOFT.WINDOWS.8.1.UPDATE.2014.WITH.BING.X64.PRE-RELEASE.CORECONNECTED.ENGLISH.DVD-WZT and thats the screenshot of desktop. Watermark is gone
Yes, since reverse engineering the publickey of the actconfigid to find the correct secrets hashes that can be used for activation, will take dozen times multiplied by the age of the universe. As the secret is very different for each pkey, and seems to be signed by hmac/sha256. To get it sooner you need to leak the lookup table of the activation server or the phone center, which is very unlikely to ever happen.
To be fair, I doubt Wzor has much understanding of the keygen - I remember him asking for one initially and suspect someone must have sent him that without explaining it fully... This is the one time I hope he does not release something
So Here is a Quick Guide for Offline Integration of Windows 8.1-2014 Update to Windows 8.1 RTM or GA Prequistie Updates : **************** 1) Rollup-A GA Updates (KB2894179, KB2883200, KB2894029) 2) Rollup-B Updates (KB2884846, KB2898742) 3) Rollup-C Updates (KB2903939, KB2911134) 4) Rollup-D Updates (KB2911106, KB2914218) 5) Rollup-E Updates (KB2887595-v2, KB2898514, KB2901101, KB2906956, KB2908174) 6) Rollup-F (April 2014) Updates (KB2919442, KB2919442-1, KB2919355, KB2932046) Bug & Fix : ********* The x86 version Rollup-F (April 2014) Update KB2919442 & KB2919442-1 is wrongly named because the KB2919442 is newer than KB2919442-1. So the Updates KB2919442 & KB2919442-1 has to be integrated in reverse order Procedure : ********* 1) Mount the Boot, Install & WinRE WIM Image of Windows 8.1 / Server 2012 R2 (RTM/GA) 2) Integrate Rollup-A GA Updates to WIM Image in these order KB2894179 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2883200 (Applies to Install.wim) KB2894029 (Applies to Install.wim) Note : This Step is not necessary for Windows 8.1 or Server 2012 R2 (GA) 3) Integrate Rollup-B Updates to Install.wim in these order KB2884846 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2898742 (Applies to Install.wim) 4) Integrate Rollup-C Updates to Install.wim in these order KB2903939 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2911134 (Applies to Install.wim) 5) Integrate Rollup-D Updates to Install.wim in these order KB2911106 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2914218 (Applies to Install.wim) 6) Integrate Rollup-E Updates to Install.wim in these order KB2887595-v2 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2898514 (Applies to Install.wim) KB2901101 (Applies to Install.wim) KB2906956 (Applies to Install.wim) KB2908174 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) 7) Integrate Rollup-F Updates to Install.wim in these order KB2919442 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2919442-1 (Applies to Boot.wim [Index:1,2], Install.wim, WinRE.wim) KB2919355 (Applies to Boot.wim [Index:1], Install.wim, WinRE.wim) KB2932046 (Applies to Boot.wim [Index:1], Install.wim, WinRE.wim) 8) Commit & UnMount Boot WIM Image (Both Index 1,2) 9) Re-Build Boot WIM Image 8) Commit & UnMount WinRE WIM Image 9) Re-Build WinRE WIM Image 10) Commit & UnMount Install WIM Image 11) Re-Build Install WIM Image 12) Finish If there is any change in the final RTM version of spring 2014 updates, then the above will change too, if anyone interested in a converter for Windows 8.1 / Server 2012 R2 RTM/GA to Spring Update 2014 ISO, let me know, I will release the script that I have finished as it's working perfectly... Now, the interesting thing is In the recently leaked Windows 8.1 Core Connected with Bing Edition, when windows update is run it just shows just two Rollup Updates (KB2883200 & KB2887595-v2) to be installed. Where when you just integrate the Spring 2014 Update to the Normal Windows 8.1 / Server 2012 R2 RTM GA it shows all the above Rollup Updates. One More strange thing is When the Spring 2014 Update is applied on the Windows 8.1 Core Connected with Bing Edition, The first two updates (KB2919442, KB2919442-1) wont get applied while the third update gets & fourth updates (KB2919355, KB2932046) gets applied, but upon boot the fourth update KB2932046 will corrupt the OS and it boots into Automatic OS Recovery Mode. Isn't the Windows 8.1 Core Connected with Bing Edition should contain the Spring 2014 Update along with it??