@CODYQX4 Hi guy, I have a big problem with your Activator. (Sorry for my bad English) After 5 minutes from the boot of the PC, 3 processes - cmd, Keygen.exe and OSPPSVC.EXE - that starts automatically and burns up a lot of CPU: so I have to kill manually this processes. I'm on Windows 7 x64, with Office x64 and the activation is in good status. So I ask you some way to completly uninstall your activator... Thx a lot! Bye Adriano from Sorrento (ITA)
I've activated my office rtm x64 yesterday with EZ-Activator 1.3.0.0. Is it better to reactivate with EZ-Activator 1.3.5.0?
i saw this and try using toolkit(1350) to change EZ-Activator(1300). First i choose 1 to uninstall autokms and then reboot, the file under c:/windows is still there<---uninstall not working? then i run x64 EZ-Activator(1350) to replace autokms, and after processing autokms is still old one(1300)<---doesn’t replace? therefore i choose 1 to uninstall and manual delete it, after reboot using toolkit(1350) to install it again, then it shows autokms was not installed<---why can’t install? Finally I only can use x64 EZ-Activator to run again, and it’s working (autokms under c:/windows is new one) So the toolkit can’t uninstall autokms which use EZ-Activator installed? A lots of problem confuse me……but It's still a great work Thanks CODYQX4
If already activated then leave it as is. I am not sure why it didn't delete when using option 1 (You should not need to reboot to install/remove) but the EZ-Activator will not overwrite AutoKMS if it is in Windows already so that is why you had 1.3.0 (There is no real difference other than 1.3.5 has ospp.vbs included so it will work regardless of where office is installed). OSPPSVC will run on its own as it is office protection. The keygen and cmd are AutoKMS which should not eat up lots of CPU. You can't uninstall the changes made by EZ-Activator but you can use the toolkit to remove AutoKMS which is what is running the keygen. Though you will be better off with it. I find the thing likely to spike is OSPPSVC which only does so for a few seconds therefore it shouldn't cause a slowdown and you will have to activate manually without AutoKMS. Removing AutoKMS will not stop OSPPSVC from running as it is office that runs it.
I'm testing out 1.3.5.0 with my new installation of Office 2010 VL x64 and I keep getting this error whenever I "Attempt to active" (option 2): Code: --------------------------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel Last 5 characters of installed product key: H3GVB ERROR CODE: 0x8007000D ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x8007000D --------------------------------------------------------- --------------------------------------------------------- Try To Activate Again? (Y/N) I also tried EZ-Activator64 1.3.5.0 and it runs til completion but Office 2010 is still not activated. Does anybody know what I'm doing wrong?
The KMS activation isn't working. Sometimes it takes multiple tries. If you have tried a ridiculous number of times it helps to delete all license info, get office to repair itself by starting an office app and try again. I may make a tool to delete all license info.
If KMS activation does not work, what does your Toolkit do then? Why would it take multiple tries, there must be an underlining reason why it doesn't work the first time and that you have to retry an arbitrary number of times in order for it to work. I'll try your suggestion and also try to figure out how to delete license info.
Well it may fail as the keygen sometimes gives invalid data and work after a few more tries. Sometimes however office just gets into a state where it seems to never accept the keygen code. I usually delete the license info and try to get office to reset itself (I posted how to a few pages back). SMorgan posted somewhere that using VAMT 2.0 with keygen running and it set in the registry to use 127.0.0.1(My tools delete this key after use) may help but I have never tried this.
That is quite correct as I never really trusted the MINI-KMS activator and used VAMT 2.0 and activated office 2010 with it when keygen.exe was running along side of it. However the Keygen.exe is not perfect it may fail a few times thats why you might have to try it a couple of times. Also last but not least the 127.0.0.1 is the default so it should already be in the VAMT 2.0 thing....
I found a notice, that Windows 7 KMS activation requires a BIOS slic in general. Could that make the difference in Office activation, causing it to fail on systems without slic? Unfortunately my counter isn't high enough to post the link
Win7 KMS Activation does not require a special bios, just run and you are activated. Who told you that you need a special bios? Any bios will work
I got it dude. Review my reply. I just doubt they will require it or everyone will just use OEM instead of KMS. KMS was designed to activate thousands of computers for corporations. That is why they do revalidation checks every 180 days.
OK Version 1.4 Is Up. The Toolkit Now Has a Delete License Data Function (Last Resort For People who can't activate). The EZ-Activator will update AutoKMS if its already installed and has changed Messages. AutoKMS will now warn you with a messagebox if it fails 25 times that there are problems rather than running in an infinite loop. Concerning making a GUI, I would like V2 to be a GUI of the tools, but I don't simply want to wrap a GUI around a batch file as it looks sloppy. Rather, I'd like to turn the batch code into a C++ GUI app but have very limited C++ skills.
Very minor toolkit update:You can now use license injector to add Standard Retail License. No Other Tools changed. I could use some retail stuff (Keys, Installers, etc) to enable addition of more licenses.
@CODYQX4 Your Tools Kit Update so much recently. I appreciate that, but you never note what have change or improve from the last version.. Hope you will provide Change Log for the next version.
Just upgraded the links on the repo and also put a link to the thread that should do the trick... Much thanks for the work on this Multi-tool thou!!!