There is so much gibberish in this thread, makes it hard to read. When anyone talks about blocks and non-genuine status etc., please very clearly separate these two issues, and say which of the two you are talking about: 1. Blocked KMS host key. Any attempt to activate online the system itself on which the key was used, fails. This is pretty normal, and is pretty quickly the case for every single leaked KMS host key. 2. Invalidated KMS host key. Any client becomes non-genuine when validating (not activating) online, where the client was activated against a KMS host with the invalidated key in question installed on it. This has only happened for some KMS host keys so far. Note that as far as we know Microsoft can't stop the activation of a client against a KMS host, even if the KMS host key has been blocked and invalidated.
Note that as far as we know Microsoft can't stop the activation of a client against a KMS host, even if the KMS host key has been blocked and invalidated.[/QUOTE] So, what I have said in page 25 (my set up) goes hand in hand with your quoted expression above ? Unless MS in any future or existing update/service pack injects a "program" to run calculations (I am speculating here) and determine that your system is being run/activated with a KMS Host server that you have and the key is now invalidated, then you will never have problems, as long you keep re activating every 6 months, internally with your KMS. Can we conclude, at this stage, with what we know that what I say has some validity ?
Hum... I am activated via KMS (ZWT) and all updates applied and everything seems to works fine for now....
everything is working perfectly even after update (windows 8 + office 2013 KMS activated with banned KMS host Key ) even on my another PC (windows 7 + office 2010 KMS activated with KMS Emulator (Cody's Toolkit)) I love MDL
Did you run a genuine validation or not? We KNOW it still activates and stays activated with updates. It just doesn't pass GENUINE VALIDATION. Try to see the difference.
So... they blacklist the key... but since KMS emulator doen't has real key attached to them... it still works?
The client knows no key. From what's visible in slmgr /dlv, the client stores only the Extended PID from the server, so that must be the piece they use to block. Can you show me Extended PID of the server on the client please? PM if necessary. I'm trying to confirm whether the KMS emulator I have here has a different one, since after a slmgr /rearm and activation with this emulator here, I'm still not genuine. I'm setting up the system from scratch and trying again. Edit: Maybe they are doing sanity checks on the ePID now since it contains e.g. the date the KMS server was activated on.
I'm just reinstalling from scratch and trying again with a local KMS emulator first without modifying that emulator.
Thanks but as a *IX guy I like my console programs with command line parameters. Yeah I know a regex when I see it. I will definitely generate a random ID for myself. I plan to at least raise the OS edition to 2008R2 niveau and randomise the activation date. There's much testing ahead. Edit: That's not really correct. It's region, not language. On an English Win7 with the region set to Germany, it's 1031.
Tested Win7 Pro in VM all results in non-genuine after validation online KMS machine extended PID Server 2012 kms host: Code: 05426-00206-152-252649-03-1049-9200.0000-3192012 Server 2008 kms host: Code: 55041-00206-152-252649-03-1033-6002.0000-3272012 ZWT (file name say emulator, inline window says keygen) + MTK: Code: 55041-00168-305-190595-03-1033-3790.0000-2692009
It looks like the ePID is really sensitive information. There's an endless number of people asking for help with their legit KMS installations on Google who post their ePIDs unscrambled. Just using one of those is 1) safe or 2) getting legit KMS installations into trouble. Unbelievable MS would do this to their legit customers. I'm not sure right now, but is it written anywhere that ePIDs are to be handled like secrets? Why are they visible to every client without admin rights? Think companies where every employee can basically get your KMS installation into trouble now.