Though I've seen that error once, I have not gotten it in BETA 4 Toolkit. It appears that I call the wrong function in AutoKMS though. I have a load default settings for toolkit and AutoKMS (AutoKMS has less settings) but I load all settings. AutoKMS could be crashing if it tries to load settings not in its ini file. I'll look at AutoKMS and reup BETA 4 with fixed AutoKMS. Also, I see AutoKMS is using defaults as it is trying to read settings.ini and not AutoKMS.ini. I believe I made the changes and forgot to save them. I myself am not crashing but its ignoring the fact I set logging to false.
@CODYQX4 Thanks for your tools. By the way, Can you do me a favor for telling me how I can activate manually ( I mean what command lines to enter ) Thanks in advance
I suggest you look at "Office Repo" manual activation. It lists some commands. The toolkit does it with WMI so you could not do it the same way (ospp.vbs does the WMI stuff, we cut it out as its a middleman to me). The ospp.vbs /act switch is activation but for KMS you would need to have keygen running and KMS host set to 127.0.0.1 (ospp.vbs uses the /sethst:127.0.0.1 switch for this).
@CODYQX4 Thanks for your hint. I'll give it a test. But I wonder the reason why KMS only lasts 180 days ..... Is there any ways that we can set up longer... or it will automatically reset after 180 days instead of doing it again ? Thanks in advance
Beta 4.1 gets it done. No AutoKMS crash with this one. Logging works now, too. 1st entry right after install; 2nd entry after system restart. Great work. Tks much.
Because MS coded it that way. KMS is intended for machines constantly connected to company network that can easily be reactivated (they retry every 7 days). Your best bet is AutoKMS which reactivates every boot (I assume you will reboot within a 6 month period). It is fixed in the reup'd beta and is one of the most effective KMS reactivators, as it only reactivates KMS, all the scheduled tasks that use /act will try to reactivate MAKs which is slow, burns down the count, etc. This makes AutoKMS way more efficient than a simple batch on a task.
Hi, I'm not sure if this helps or not, but I tried and it didn't work. Here is the info the Toolkit gave me: --------------------------------------- SKU ID: 42cbf3f6-4d5e-49c6-991a-0d99b8429a6d LICENSE NAME: Office 14, OfficeProPlusMSDN-Retail LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Grace Period Last 5 characters of installed product key: BBKQ8 REMAINING GRACE: 30 days (43122 minute(s) before expiring) --------------------------------------- Getting Office Configuration Information. --------------------------------------- Backing Up License Info In Case Of Failure. --------------------------------------- Changing any Unactivated MAK Keys to KMS Keys. --------------------------------------- If You Have Starter Subscription It Will Now Use Permanently Activated Key. --------------------------------------- Converting Unactivated, Trial, Or Subscription Retail Versions of Office Into VL. Converting Retail Professional Plus To VL Professional Plus. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. Removing Professional Plus Retail Key. --------------------------------------- Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Failed To Activate 10 Times. --------------------------------------- Attempting To Rearm. Microsoft Office rearm successful. --------------------------------------- Attempting To Activate Office 2010 KMS Products Again. Attempting To Activate Professional Plus. Failed To Activate 10 Times. --------------------------------------- Attempting To Reinstall License Files. Reinstalling License for Professional Plus VL. --------------------------------------- Attempting To Activate Office 2010 KMS Products Again. Attempting To Activate Professional Plus. Failed To Activate 10 Times. --------------------------------------- Attempting To Delete and Reinitialize License Files. Getting Office Configuration Information. Deleting License Info. Repairing Licensing Components. Reinstalling License for Professional Plus Retail. --------------------------------------- Have To Convert Retail To Volume Again As Repair Reversed The Changes. --------------------------------------- Converting Unactivated, Trial, Or Subscription Retail Versions of Office Into VL. Converting Retail Professional Plus To VL Professional Plus. --------------------------------------- Have To Remove Unactivated Retail Keys Again As Repair Reversed The Changes. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. Removing Professional Plus Retail Key. --------------------------------------- Attempting To Activate Office 2010 KMS Products One Last Time. Attempting To Activate Professional Plus. Failed To Activate 10 Times. --------------------------------------- Could Not Activate, Trying To Reverse EZ-Activator Changes (Using Backup). --------------------------------------- EZ-Activator Failed! Here is a more detailed description about the error: Office 2010 KMS Activation Failed! Office 2010 Rearm Fix Was Attempted Without Success. Office 2010 License Reinstall Fix Was Attempted Without Success. Office 2010 License Delete + Office Repair Fix Was Attempted Without Success Successfully Reversed All EZ-Activator Changes (Using Backup). If All Else Fails, Try Reinstalling Office.
I don't want to go through 105 pages to see if my question is answered so i gonna ask it. Will this get detected by antivirus apps? I used mini kms activator on a clean install of windows 7 + office 2010, and after i installed Norton 2011 it detected the kms as trojan and deleted its files. Someone who use Norton 2011 answer me please
Can you in the settings App set the attempts to 25, and make sure that when you rerun it, that the KMSEmulator.exe does run and host get set in the registry? KMSEmulator.exe goes in windows, try disabling AV/Firewall. Also, the "Repair" part is usually the deciding factor. After Settings activating attempts to 25 in settings, ensuring no AV interference will occur, and that KMSEmulator.exe runs, try it again. Also, disable Delete Host and Keygen After Use, it will allow you to confirm that they occurred as they won't be reversed after running. KMSEmulator should show up in TaskManager and in registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform there should be a value KMSServiceHostName set to 127.0.0.1.
Yes, it will. If it does not currenlty it will. The KMSEmulator.exe (The KMS Keygen) is the primary suspect which autoKMS and the toolkit copy. I recommend disable AV during activation and set C:\Windows\KMSEmulator.exe as exclusion (as with AutoKMS it does it before you could change AV.).
Thanks for your quick reply. So there's no way to activate manually ( I mean without KMS Keygen ), isn't it ?
Not unless you set the host to a real KMS server instead of 127.0.0.1, and real KMS servers usually don't activate unless they have 5 hosts wanting activation.
no way to activate them manually except connecting to a custom KMS server (while KMS keygen emulate the function of this) since they are KMS client key
Greetings to all. Just on a quick note..............Symantec Endpoint Security will also kill this. Six months ago was not the case. This later comments is related to the original ZWT keygen which still is great. So AV companies might be getting instructions to clean "us up"??????? One question if anyone knows the answer..................................I do have the 6.4Gigs Melinda Gates KMS but never bother to run such a beast so I take it that either ZWT or this one must be manually run every 6 months to give the next 180 days???? The fact that calls service to the loop back then never leaves frames out the RJ 45 connector. Has anyone run an automated process to make things easier? Thanks
Hi i am new here. I wonder if someone can help me, I want to intergrate my office activation backup i did using toolkit beta 4 into a office 2010 setup. Maybe it can be done by using Microsoft Office 2010 Customization Tool or config.xml or both. Thanks.
Shouldn't this be C:\Windows\AutoKMS.exe? Cause upon my testing I haven't seen a KMSEmulator.exe in the Windows directory.