Nothing I can do about AV, just exclude it. As far as the zero sometimes the backup involved in this screws up and therefore doesn't count, causing sometimes it to say zero. It's intermittant and timing related so it may work fine later. This is one known bug I think V2.1 has fixed.
My version of Avast doesn't allow whitelisting files, but only directories. In other words, I won't add the whole Windows directory to my ignore list. Although, I'm not complaining, I will just active manually.
For Avast Free edition select the Real Time Shields, Behavior Shield, Expert Settings and add AutoKMS and KMSEmulator to the Trusted Processes option. Make sure that Avast hasn't moved one or both of them to the Virus Chest. If so, then restore them. You can run Autokms manually to make sure your settings work with Avast.
Maybe I'll be able to add different directory and uninstall by looking at where the task is pointed to. That being said, AV's with this kind of limitation is stupid. Something that annoys me in NIS in in 18.5 update they actually removed the ability to exclude an item from scanning that didn't exist, meaning you have to first exclude it from AutoProtect, create it, then exclude it from manual scan so the background scan doesn't run god knows when and delete it. Easiest way would be me to make an AutoKMS folder inside windows folder like I do with AutoRearm.
Hopefully that will work for him. I know some AV (AVG sucks) create hell with doing things. With AVG I find I have to totally disable AV first to be able to create the files to exclude them at all (else they get destroyed immediately). Nobody should have to 100% disable protection to exclude something they know is safe. AV makers are damn nazis, because I know they make this purposely hard to discourage this kind of thing.
Been waiting months for this. Finally an activator that keeps the 180 day activation. Kudos to all. Installed and activated my VL edition with no problems. Using MSE as my AV program. Turn off Real-time protection before installing. When you turn it back on it will pick up 2 false positive viruses. Choose to Allow them. Thanks to Developers: CODYQX4 Bosh And Thanks to: letsgoawayhell, ZWT, and other contributors.
Thanks for the feedback, I know that it is a false positive, but I wonder if I need to allow it to pass through the firewall?
To cmdrbond and all others who use Norton and do not find trusted area. 1: "Disable Antivirus Auto-Protection" for 15 minutes, or 1 hour you find that if u click on taskbar norton icon with right mouse button. 2: Run the "Office 2010 Toolkit" and use "EZ-Activator" 3: Open norton and hit tab "Settings" 4: Now open "Computer Settings" tab (it is mostly by default first one what is open 5: Find a line called "Items to Exclude from Scans" and hit behind it "Configure [+]" and add 2 paths to there Code: C:\Windows\AutoKMS.exe C:\Windows\KMSEmulator.exe 6: Find a line called "Items to Exclude from Auto-Protection and SONAR" and hit behind it "Configure [+]" and add again next 2 paths Code: C:\Windows\AutoKMS.exe C:\Windows\KMSEmulator.exe 7: Now your can wait till 15 minutes are over or "Enable Antivirus Auto-Protection" manually Good testing
This tool works great but, to keep on subject and I am just offering an idea trying to keep down the false positives on most of the AV programs. Why can't you just hide the two programs like everyone does with root kits. No, I do not know how to make a root kit but, I am sure someone will hopefully know of a way to hide them and keep the files from being scanned.
Activation steps help Hello, Thanks for all the great work. This is how far I got: OUTPUT ON USING EZ-ACTIVATOR: 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. Successfully activated after 1 attempts. --------------------------------------- Installing AutoKMS. --------------------------------------- Office 2010 was succesfully activated. OUTPUT ON CLICKING "CHECK OFFICE 2010 ACTIVATION STATUS" --------------------------------------- SKU ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX7e0c LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated Last 5 characters of installed product key: H3GVB REMAINING GRACE: 180 days (259195 minute(s) before expiring) --------------------------------------- OUTPUT ON CHECKING REARMS AVAILABLE: You have 5 Available Rearms --------------------------------------- Do I have anything else to do? Thanks!
That's easier said than done. We are trying to load the KMSEmulator from RAM so it doesn't get to disk to get detected like Phazor does but there is no easy to do this and we outright cannot make progress with it. You are activated but you need to make sure AV excludes AutoKMs.exe and KMSEmulator.exe.
Hi, New laptop came with office starter which was removed, then the uninstaller in your tool was run. The uninstaller mentioned that it detected "legacy products" or something, which would not be removed. Installed Stardard VL 2010, a clean copy, but when trying to autoRearm it the tool just keeps loading (for 30+ mins) without confirming or putting up an error. AutoKMS works fine, but why would AutoRearm have issues? TA
There is a rare bug during the backup involving IO timing that causes it to freeze. It only happens at certain times. I believe it has to do with the fact I copy the whole tokens directory and OSPPSVC makes .bak files but removes them. I set V2.1 to only backup by files needed and so far I have not had the backup bugs reported. But it is hard to tell if it's fixed until BETA allows more reporting.