Phazor gave CODYQX4 a modded Keygen.exe, it doesn't have the fix for the CMID, it just has less false positives than the original.
And this is the localhost.dll that is normally launched by his lhstlnch.exe. The localhost.dll is really an exe.
KMS CMID Explained - Part 2 This part is gonna act as an FAQ to answer some common questions. ======================================================================================= Q. Does my office have a KMS CMID? A. That depends. If no KMS activation is attempted then you don't have one. It is being generated the moment you try your first KMS activation attempt. But remember that if you use VOLUME_KMSCLIENT channel then office will try to activate every once in a while automatically. Q. Is there a way to null my KMS CMID? A. Yes, but unless you have a backup of when activation was not attempted then you have to use a rearm. Q. Is having a KMS CMID good or bad? A. Having a null KMS CMID is kinda better! Because you have the chance to backup your office licensing store in this state for further usage. Q. Why is it good to have a null KMS CMID? A. Because ZWT's KMS keygen has some bug and doesn't work for some specific KMS CMID's. Having a null CMID means that you have the chance to get a good CMID. ======================================================================================= Note: This is final part coz I think enough info on KMS CMID is posted till now.
OK guys. I am going to put up a post soon that answers the following questions: Why does ZWT keygen fail to activate sometimes and does the job at other times? Why does ZWT keygen produce persistent 8007000D error? Is the modified keygen capable of solving the problem? If there is a situation where both original and modified keygens persist on 8007000D error, Is there a way to circumvent the problem? After I share this info with you, persistent 8007000D error should be gone for good. But sorry, the post is gonna be a bit technical so some people may have to wait till CODYQX4 and Bosh to implement it in their activator.
@letsgoawayhell Thing is, if he has 174 days that means he successfully activated once (and the persistent 80007000D only applies to initial activation, as in reactivation never fails 10+ times unless KMSEmulator/Hostname or such reasons are messed up). And the only ways to change CMID are rearm or repair, which remove activation. @patrik confirm AutoKMS is installed, make sure it is logging, post the log, you can trigger it by the task. My suspect is AV/Firewall, though if somehow AutoKMS didn't install proper, it isn't running (I check install by the task, not by the file, since the file can now be anywhere). Confirm launching the task manually runs AutoKMS.exe and find the exe, and check the log when the AutoKMS closes. Close your toolkit window, delete settings.ini, uninstall AutoKMS, and reinstall it. There was an issue with 2.1.2 where I don't handle the ini properly from older editions and can screw up AutoKMS path. That issue is because I enforce an INI ID (equivalent to the lowest toolkit version which the ini format hasn't changed. Adding paths changed some things, and my next version changes them again). I haven't confirmed the paths issue in the wild but 2.1.3 testing got it, as I am supposed to create a default INI, not a new one (I subtract filename from path to get path, but doing new ini vs default subtracts from it again, breaking the path).
Good to know, though I wonder if your "solution" differs from mine, because I have an idea planned to use the backup+blank cmid method as I have hinted at, but hopefully something more elegant/faster surfaces.
Here everything is working fine with Office 2010 Toolkit 2.1.2 on Windows 7 Ultimate x64 PT-BR and on XP Professional x86 PT-BR (in VirtualBox 4.0.4). I can install EZ-Activater, install and uninstall AutoKMS, Active (Attempt Office 2010 Activaction) and all works perpectly.
@patrik, so that I can tell if it is toolkit or keygen, do the following. Use 2.1.2, open settings, go to EZ-Activator, disable everything and have attempts set to 10. Now run EZ-Activator. Does it fail? Do the same for 2.1, if EZ-Activator works on 2.1 and not 2.1.2, something with the new keygen is causing a problem. Because between 2.1 and 2.1.2 nothing changed except new keygen and a fix for making ISO files via Customize Setup tab. So any issue would be the new Keygen. Also your tests confirm AutoKMS is running/installed fine, one user said their AutoKMS didn't install right but I can't replicate that issue.