No it does not run 24/7. It runs when you first login but then closes and doesn't run until reboot. You could adjust the schedule but I'd would not make the wait too long. A Week is fine but don't set it to 179 days and hope nothing can go wrong.
Thanks for the quick reply. I noticed it is no longer running in Services, so it must have been doing it's job when I checked, because I was twenty or so minutes past a restart at that point. I'm going to go ahead and assume that if it's running longer than three hours, there's a problem, so I adjusted the task to stop running after three hours and to only run once a week. This is better for me because my computer can go for weeks without a restart at times. And I'll have Outlook remind me to check it in 4 or 5 months just to be safe. Thanks for the great program. I was extremely happy when I got it to work for me. It puts the other efforts to shame.
Yeah 20 minutes may be possible (As it takes some minutes to start once you login) but definitely if it starts and then runs for 3 hours something is really wrong.
Yeah...I was totally wrong, actually. I kind of lose track of time when I'm using the computer, and when I checked my logs and saw my last log in had been 3 hours prior and that AutoKMS was still running - I brushed it off as a logging error because it felt like only twenty minutes. But my logs were right, AutoKMS had been running for three hours! A problem indeed. When you said it doesn't run 24/7, I checked the Task Manager, but I neglected to 'Show Processes from All Users' so it was still running but I just overlooked it. I looked at my clock at that point, saw that it was under 3 hours from when my system claimed to have last restarted, and even though I thought it was 20 minutes, I put 3 hours just in case. I realized my problem when I checked the status of my activation and it hadn't worked once since I actived nine days ago. Yikes...so further investigation revealed that my antivirus and firewall have been blocking it from running. But I fixed it. I had to go into my Norton Antivirus 2010 and put not just autokms.exe as an exclusion, which I had done already, but also the other file that gets created, KMSEmulator.exe. And I permanently added KMSEmulator to my Firewall Incoming Rules as 'Accept'. Then I ran my AutoKMS task, checked activation status again, and I was reset to 180. Now the programs works correctly in processes; it terminates after activation occurs, but there is one tiny fluke for which I have another question. Besides AutoKMS unpacking the KMSemulator into the Windows folder, a temp file is also created, for me it was called tmp0000004324c20d76d709bb00. Will this file always be by the same name so I can add that to the exclusion list as well? Stupid Norton seems to think it's Trojan.adh. If not, do you recommend excluding trojan.adh from known signatures? It seems like a hacktool rather than malware. Thanks again, and seriously awesome program.
Don't know what the tmp0000004324c20d76d709bb00 (or even if I make it, but maybe its the file before its written?) is but yeah AV interference can cause errors that I can't easily predict or fix. It doesn't seem to be mine, so unless its a natural part of C# to write it like that when writing an embedded resource file to disk, then it is not mine. The only tmp file I make is if you disable AutoKMS logging. Since I had logging so intertwined with the code to easily toggle it, I just dump all logging to tmp file and delete it when logging is disabled. Most of the time AV deletes Keygen, but if it kills it before it even ran, the app will recognize it failed to start and error. If it kills it then deletes it the app will either error out or simply do activation until the limit is reached (to prevent infinite loop). Still, since AV can modify environment (I heard someone claim AVG hooks into explorer and even if you add keygen to exceptions, if it already caught it it will mess with the keygen's execution and this really wrecks things beyond my control --- though I don't know if this about AVG is true.) I use NIS and I just add the KMSEmulator exclusions and it works fine. Adding the firewall rule I did as well (as otherwise I saw blocked popup at login) but the AV exclusion is the key. I don't quite know about disabling the whole Trojan.ADH, as I put the Keygen in same palce every time, and who knows what else gets detected by that signature. Another thing is while with NIS I consistently get Trojan.ADH, I once before ever seeing that had it come up as something else (I think keygen or hacktool). So if they change the sig without you knowing then it messes things up. Since I want to keep it is for the sake of compatibility and people not having to change their AV (but popular demand led me to name it KMSEmulator.exe and not Keygen.exe).
First, if anyone hasn't told you this, you're awesome. Second, I can answer my own question about the temp file by checking and seeing what name it is generated under the next time I run the activator. Whatever it is, it appears in C:\Windows\Temp when I run the AutoKMS. I suspect that it is related to the AutoKMS because when NIS blocked KMSEmulator, it claimed that too was Trojan.ADH - and the pop-up from NIS about blocking the temp file occurred within seconds of me launching the AutoKMS task. I'll make a note for myself to relay my results about the temp file to you when activator runs again next week. Thanks again for all of your help.
Well, my main problem doing all of this is, I have uninstalled Office 2010 (hoping to resolve issues by re-installing.) But when I try to re-install the program I get this error: "Microsoft Office Professional 2010 Trial encountered an error during setup. Error 25004. The product key you entered cannot be used on this machine. This is most likely due to previous Office 2010 trials being installed. (System error: -1073422308)" so now I cannot even install it back onto this computer. I've also tried using another key (from another trial signed up with a new email address)
So, when I click on EZ-Activator, I install AutoKMS program automatically which allows Office 2010 to be activated forever. Right? On XP Professional SP3, how do I make sure that the AutoKMS program is run every week? This program needs the Internet to work properly? THANKS BYE
That error seems to suggest that Office 2010 is really messed up and did not cleanly uninstall. Perhaps cleanup every office thing you can, and if that don't work I uges you'll have to nuke the PC, so in that case I'd DL Retail Office 2010 (not trial) and use leaked retail key to install or use Stannieman's channel changer to make the installer VL. Given that you have uninstalled and reinstalled several times things have probably gotten screwed beyond help.
hi, thanks for the reply. i am using windows 7 x64 and office 2010 x64. my av is nod32. here is the screen from activaton status, at the moment i have a volume office 2010 installed as i thought i would give that a try so i uninstalled retail and used channel switcher to make a volume file. --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Notifications Mode Last 5 characters of installed product key: H3GVB REMAINING GRACE: 0 days (0 minute(s) before expiring) ---------------------------------------
does anyone have any ideas with this? when i also use mini kms activator i also get an Error 0xC004F074 which states therer is no local running kms server that can be found on the computer. what can be causing kms not to work?
That error could be the KMS Host not getting set in the registry or the KMS Keygen for some reason not working as it should. Given you get issues with that mini-kms as well it seems to be a keygen problem. As you showed me your info, I isolated it from a toolkit code issue and it appears to be the Keygen. Are you sure there are no AV or firewalls or other apps messing with it? I heard some people say AVG can mess with Keygen even if whitelisted (which sounds hard to believe). Generally the error you get when Keygen works but KMS activation always fails is 800700D. This is when Keygen works but office is stuck and refuses KMS activation (this is what EZ-Activator tries to fix). This 8007000D error means Keygen was running fine. Another error when host is outright not set is a 8 something error (ends with a B I believe). This occurs when no KMS Host is set. Your error I see is when host is set but Keygen is not working. It would be like you set Office to connect to MDL to activate, which would not work as MDL is not a KMS Keygen or server (as in it sees the address exists but not a KMS server). So something is causing keygen to not run properly, so that activation does not work ever, another reason why a repair would fail, which is meant to fix the 800700D error but needs KMS Keygen running afterwards to actually activate.
it was a firewall issue. despite turning off windows 7 firewall it was still blocking kmsemulator.exe from operating. so this time i opened windows 7 firewall control which i use to monitor outbound connections and it then popped up that it was being blocked. sorry for wasting any time, i just assumed that if i turned windows 7 firewall off in control panel then the frontend application i use would not still block any connections! thanks for your help though.
OK I got an idea for you to see if Keygen is actually working. Easiest way to do this is to go into toolkit settings in global tab and disable 2 settings: Delete KMS Keygen After Run Delete KMS Host after Run Then run Activate (not EZ-Activator), it will set the KMS Host and write KMSEmulator.exe to windows folder. Activation will probably fail as usual. Now when it fails, close the toolkit and run the KMSEmulator.exe in windows so you see its window. Then open MS Word 2010. Since your Office 2010 failed to activate and is in notifications mode, it will try to activate by KMS itself. So open it and watch the KMS window. If it says it delivered a code Keygen is working, otherwise it is not, and all blame is on the Keygen as it is now operating on its own, not as part of the tool. Tell me if it delivered the code or not. I need to know this as if it does then mini-kms failed to do something, but if it does not, then something on your PC is screwing up the Keygen. Another thing to confirm after trying this is to go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform and see if a value called KeyManagementServiceName exists and is set to 127.0.0.1. Without this Office 2010 does not try to use Keygen.
works absolutely fine now. just strange that my firewall would still block something despite turning it off! does 5 reaarm attemps mean that you can have it for the 180 days after activation, followed by 180 days x 5 and then it will expire and need to be reinstalled, or do i have that wrong?
No need to rearm at all. KMS is for 180 days but there is no limit to reactivation. The AutoKMS feature in the toolkit installs a program that runs at boot, that resets the 180 day by reactivating. Once you get your first successful KMS activation (as some people have issues the first time) it works cleanly every time as long as you control AV. So AutoKMS would keep it from expiring (unless you go over 6 months without a restart, and even then it can still reactivate it after a restart).
The comodo firewall does the same when I close it, I have to disable the firewall first and then exit the application and still dont know why The rearms are for someone that can't use KMS activation, as AutoKMS will reactivate Office every time the computer starts, so every day you will get 180 days and the activation period will (in theory) never end.