I have tried both EZ-Activator and the Toolkit. Both work with the VL version of Office created using the Office Conversion Program. When using the EZ-Activator version, Microsoft Security Essentials reports "HackTool:Win32/Keygen. I understand that this is normal and is not a threat. However when I use the new Beta Toolkit it reports the Keygen issue and also reports "Trojan:Win32/Meredrop" Looking up "Meredrop" finds that it is a rather nasty Trojan. Is this something to be concerned about in the Beta version of the Tookit? Neither the Raz0r activator nor the origional EZ-Activator report the Meredrop threat.
The activator won't work. I think it's because it can't get access to C:Windows\Setup\Keygen.exe I've changed the permissions to allow full control for everyone but that didn't help. EDIT: It was AVG. Even if you add the Keygen.exe to the exception list and turn it off it still won't get access. Once it's detected the first time EDIT: It activated great, thanks.
Finally, after several attempts, it already converted to and activated the KMS. Thanks guys! Keep it up
That's strange, I haven't switched the keygen between BETA. Perhaps MS is getting more aggressive with the keygen. I assume you got the activator from here. If so I guarantee it is safe. Otherwise somebody may have screwed with it.
Just to inform, we'll be uploading a new Beta 2.1 ASAP, it has a fix related with Office 64-bit and other minor UI fixes. Thanks to everyone for the feedback and interest in the project
The download is from the first message link here. I went back and downloaded from the first three locations in the link for the first message with exactly the same results. I am running Win 7 Ultimate 64 and the 64 bit version of Microsoft Security Essentials and have loaded the 32 bit VL version of Office. Perhaps when you do the next update the "meredrop" issue will disappear. It is odd that this issue does not appear when I use the older EZ-Activator or the Activator published by Raz0r. Attached above is a pic of the result I am seeing. I expect, as you say this is benign, but thought that I would mention it for your consideration....
I've added the AutoKMS as a startup entry in the registry and deleted the scheduled task. Is this a wise move or should I leave it as it is?
does successfully using the EZ-Activator mean that Office 2010 is permanently activated? and non of those 180-day things? also, scenario: freshly installed Office 2010, click EZ-Activator right away? will it work just like that? simply clicking the button and hope that activation will be successful?
It's basically the same but in the task scheduler you can change how often the AutoKMS runs, with that entry in the registry you can't. Once it's activated I set it to once a week.
The "180 days thing" it's something that you can't avoid (at least for now you can't), besides the AutoKMS will run at every startup (if you leave the scheduled task as it's set) and you will not have to worry about the 180 days. And yes, clean Office installation will work with EZ-Activator right away, if you have any problems feel free to ask here
alright, thanks to the guy/s who made this, got mine to 180 days. so it will auto-activate on it's own from now on? i could just sit back and just assume that everything is automatic? btw i just clicked the EZ-Activator button, nothing else. took me the second try.
In the first post you can find a "Credits" section, there are the names of the developers. You can find AutoKMS.exe inside the Windows installation directory, by default it's "C:\Windows\", and yes, you can asume that from now on it's automatic
I ran the EZ Activator a while ago, my Office is at 180 days still. So, it appears to be working. My question, if I understand this correctly, there is suppose to be a Task that runs everyday at startup. How does one view this task? (Using Win 7 x64). How could I change it to run 1 per week? Thanks
If your curious you can test the task by clicking run for the "AutoKMS" task in the right side of task Scheduler Just for fun of course...lol