Cody's AutoKMS will run silent once exceptions are made in you AV or anti-malware as does his AutoRearm
Seems like a good argument for AutoRearm. Just note that AutoRearm doesn't need exclusions of any kind to its installation. If the user is installing Office for the first time (no reinstalling and getting the notifications mode), they could run the AutoRearm switch without worry. One could use EZ-Activator switch to fix that state, but then AV could come into play. The water gets a little muddy with AV now, as they may target the toolkit exe itself, not giving it a chance to install AutoRearm, but AutoRearm itself is AV proof. It has no KMSEmulator, no memory editing, and no memory execution. I don't know about the memory editing but the other two create AV issues. Most AV don't seem to complain about KMSEmulator until it is written, after all, I could encrypt and compress C# resources and they couldn't see that, but the memory execution has given more heat to AutoKMS and the toolkit exe's as most AV simply stopped them from starting KMSEmulator (one did long ago delete AutoKMS but I can't remember which). A major reason I haven't written a silent guide is due to AV issues, the fact that someone could start making prebundled office torrents (or sold copies), that later have the AV crap out without the user knowing what to do (if you DL "Preactivated" you may not know what is doing the activation, especially if the uploader didn't my tool or give instructions, and the tool would likely be embedded in a MSP). I kinda frown on silent office, especially those who were preinstalling a MAK and listing "Preactivated and "Permanent" in the title, and UL the torrent, the MAK dry up (and user had to activate before, which is not preactivation), just to upload with a new MAK to get more rep. PS: One could use an old toolkit that didn't have RAM Execution (2.1.6 doesn't), just so the toolkit itself is less likely to stop. AutoRearm hasn't had any significant changes since I made it. All I've changed is added logging and the INI structure changed twice. It is simpler than AutoKMS which has been changed, new features to reduce KMS failure, etc.. and does far less. There are just far less variables in cases where AutoRearm can be used.
Thanks for reply. I m learning the tool now, btw great tool. Why kms version of office does not have serial key installation screen? is there any way to add this feature so user can put the key and proceed the instalation?
lol...Did we just travel back to the "Theory" thread to investigate a new Office 2010 VL solution And at least we, and only we, gave the world an alternative to KMS if they want to use it
Btw, I was wondering (because I don't remember). To use a MAK key (for Office 2010 of course) is necesary to have a volume version? or I can just use the MAK key when the Retail installation asks for the key??
Yep you need VL for it to take a MAK, which the channel switcher can patch the installer into VL so you can use MAK (Of course it will just use KMS key and you install it later).
I used Windows 7 Ultimate 32-bit, use Office toolkit 2.2.3 and i get "Failed to inject memory!" error. I had already excluded C:\Windows\AutoKMS\AutoKMS.exe in ESET Smart Security 5 (and even disable the real time protection) So help!!!!!!
You ran as administrator the Ez-Activator? Before you reactivate the AV ESET, should go in the antivirus settings and add the AutoKMS List of exceptions, KMS self is saved in the Windows folder
Remember bro you can always find every edit in the first post So you can simply look at edits done to find the 2.1.6 DFH link
There is office uninstaller bug on 2.2.3. When i click, it nothing happen. only show open-close up command prompt.
Many thanks for this CODYQX4 and Bosh... excellent software, I've been using it for a few months now. There's just one problem that popped up today. All of a sudden I got the message "Office is not activated yet, you have 29 days left" in Office. This is happening after running it for months without a problem. The only thing that has changed was the most recent Windows update. I assume it has something to do with that - it's the only thing that makes sense. This is Win7 64bit. 1) I uninstalled AutoKMS and installed it again, then clicked "Activate" - got the following error back: 2) I uninstalled AutoKMS again and then went into the Main tab and ran EZ-Activator - it kept looping through "activation failed 10 times" etc. for a while until I terminated the program. I've searched the thread for this error and found a few things; tried to follow all the advice to the best of my understanding, to no avail. Office 2010 Toolkit.exe is added to the trusted files in Comodo as well as in Avira. I've also tried completely terminating Comodo and disabling the Avira Guard - nothing helped. Any ideas on this?