Hi When I try to activate from cmd, officetoolkit.exe /ez-activator I get following error.... but when I activate from software it runs nice adn it works. Is there something I can do??? Regards Getting Office License Configuration Information. --------------------------------------- Backing Up License Info In Case Of Failure. License Backup Failed! Here is a more detailed description about the error: Could not find a part of the path '\Microsoft\OfficeSoftwareProtectionPlatform\t okens.dat'. --------------------------------------- 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 to VL. Converting Retail Professional Plus To VL Professional Plus. Microsoft Office License install failed! Here is a more detailed description about the error: The system cannot find the file specified --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. Removing Professional Plus Retail Key. <Product key uninstall successful> --------------------------------------- Getting Office License Configuration Information. --------------------------------------- Attempting To Activate Office 2010 KMS Products. --------------------------------------- No KMS products detected.
Try using the latest version. Seems like it might not set variables right in cmd. Testing console stuff in private MTK now. I plan to add a few more switches, for MultiKMS and Backup/Restore. PS: Me and JC got things 100% undetected on VirusTotal for all OTK/MTK products. That one FP for AutoKMS was because they are actually calling it a virus because it had "AutoKMS" in the file description. Change/remove it (even add single quotes to the text) on the same file and that FP is gone. That is a really lame technique of crap Fortinet to use.
Sadly AV will still be an issue. I got a cooked up build that sets no flags at all. MTK runs fine, AutoKMS runs fine, AutoRearm runs fine, but NIS 2012 flags my new tool MultiKMS, when it runs. Note that it does this when it executes and it scans the behavior, so all the obsfucation/compression/the way I added reflection to call CMemoryExecute on the fly from base64 don't help there. It seems I have made my NIS 2012 more agressive, as now it just killed AutoKMS, which it has tolerated for quite awhile. @JC any chance my CMemoryExecute trick and/or the SA have pissed off the heuristics of my AV? I'd recommend people stick to business as usual. Expect problems, and plan accordingly with exclusions, and you'll never get screwed over by your AV. Really, I wonder why the AV hate KMSEmulator so much. The code I've added to hide/edit it may be a flag but they wouldn't be used if AV didn't act like nazis when KMSEmulator.exe runs, and it clearly not being a virus. Wish I had C# code of KMSEmulator, would make a lot of things I use unneeded and I could try to change the code directly. Something tells me ZWT coded it funny, possibly on purpose, to make it harder to reverse or just done in a way AV don't like.
If your new tool not write kmsemulator in the HDD, works fine ... SA Obfuscate all assemblies, generating unreadable by AV of the signatures ...
Hi. I've used this activator for some weeks now and my office works nice. My AVG FREE went crazy about the AUTOKMS.exe, but i just added it to exceptions and everything was fine. However, there is one thing i dont understand about the activator. Does it autoactivate after the 180days?? or do i have to manually reactivate it, and then how do i do that? Thanks for answer!
AutoKMS effectively runs daily, keeping activated. If you needed to manually activate, just rerun EZ-Activator.
Yep, pretty much can tell funny things are happening, as that memory process injection code eventually has to execute and can be analyzed. I'm not getting any detects until it runs, though that could change. A lot of AV now have "trust" based scanning, as in AutoKMS is a virus because a few stupid people say it is and the companies say it is. You saw how cheaply Fortinet operates.
@Bosh I made a new way to switch the toolkit. I start it in a smaller window (basically remove tab control and move everything else up). Then the user presses a little Office or Windows button. This adds the tabcontrol and puts everything else back down. You can press either button and it changes the tab control, title and icon on the fly. This means just one window. I find Selector is annoying when I'm debugging builds, as I forget to close it and a rebuild fails as a result.
Yeah, at no point did I ever plan to make it have 2. I change things on the Form and it redraws to change. I change the window title, icon, and tabs, and it remains the same exe and process.