Thanks Reign_Of_Freedom, reran the activator with the options as suggested by u, will c after 24 hrs if it stays at 180.
AutoKMS Run key does not launch AutoKMS. You need a scheduled task, which I used to use and need to go back to.
Codyqx4, was Masterdisasters own script suggestion no good in regards to the registry run key? If it works for him why can it not be ported to work for you? EDIT Here is the post
Even though I did as suggested by Reign_Of_Freedom, today when i checked again, its 179 days now. Dear Cody can u help me out with that please.
Whoops lol forgot to tell you that you also needed to set up the scheduled task. Go to start button, type in Task Scheduler click on that, then download my task scheduler on the right hand side of the "Task Scheduler" you'll see the box named "Actions" click import and import the attachment then you'll be set. I set mine up to run on every restart.
On the second tab of the toolkit it has an option to check the Activation status on the Office 2010 install. Just hit it and let it work
Hi, the tool works great, thanks. The auto activate works amazing in vista and seven, are there any news for that in xp?
@denzel: We're going to release the final 2.0 probably in 2 weeks if nothing unexpected appears. That version would come with the fix for XP.
I don't know about release date. Unless you have already gotten some of the stuff done, I don't quite see it that early. I am busy with midterms so I can't really work on it this week too much. I believe the only code fix is the task, the rest is the readme and re documenting the code.
What is the md5 (or Sha-1) for AutoKMS.exe v2, beta 3? Also what is the path to the associated keygen.exe, and what is it's md5 (or Sha-1)? TIA!
I don't have BETA 3 AutoKMS any longer, and the Keygen MD5 for BETA 4 is B3B9295385F4E74D023181E5A24F4D83. 2.0 final will probably drop soon enough to have a good AutoKMS. Also, the AutoKMS exe is not at fault, the Run key doesn't work and all you need is the task. PS: @Bosh I updated readme, and perhaps we can delay re-documenting the code until 2.0.1 as I'll be adding some new features and probably changing some things. So, all we need is that task for AutoKMS/AutoRearm, but I want to use the built in Windows API (TaskScheduler or something like that, but we gotta use stuff that is in XP).
Thanks for the quick response, although I didn't completely understand. 1. I wanted to make sure that the AutoKMS.exe installed in the Windows directory is indeed not a Trojan, and I needed the md5 for the beta 3 version to confirm. Anyone? 2. Also, Comodo Firewall is blocking keygen.exe, but I can not find it in the windows directory. I guess that it is copied/created temporarily? How can I find it and verify it's md5?
It is deleted after use. In BETA 4 you can disable this. You would go to settings, AutoKMS, uncheck Delete Keygen After Use, then hit save. You could also set that in global and use toolkit activate to make it appear. The keygen has not changed from BETA 3 to 4 so verify it with the hash I posted. Someone else is gonna have to come up with that BETA 3 MD5 for AutoKMS, as after changing code and recompiling I do not have that exe in exact form. I can guarantee you if you got the toolkit from this topic first post that it is safe.
1. I guess that is impossible to calculate the md5 for keygen.exe if it is immediately deleted (in beta 3)? 2. How do I install 2.0 final? Simply run it and it will overwrite beta 3? 3. Please supply the md5s for the final. Thxs!
I tested your EZ activator and found when checking the activation status it additionally gives me the grace period left for Office Starter which I installed a couple of weeks ago to see what it looks like and uninstalled again. Thus both the Starter and the Office Pro Plus status. It seems that that is staying there and steadily counting down to the last of the 60 days. It would be nice if your activator clean up the Office Starter left overs as well if someone updates from Office Starter to full Office. Thanks for your excellent activator!