Click on the Strat orb, paste "MsiExec.exe /X{B2544A03-10D0-4E5E-BA69-0362FFC20D18}" (without the quotes) in the run/search field and press enter. OGA will be removed and u will happy....... as OGA has nothing to do with Office 2010, as CODY said.....
--------------------------------------- Activating OfficeProPlus-KMS_Client <Product activation failed> --------------------------------------- - This doesn't work anymore i try every single method and it just won't work. =( maybe the keys are all reached to limit or blacklisted? - CODYQX4? can you please fix this? =( i really need MS office for school - your the best <3
Could you give more details about the error? We're not diviners As for a geneirc solution, use the "Remove all" from the "License Management", then add a Volume Pro Plus License, and then use the EZ activator again. If that doesn't solve the problem, you can give us more information to work with
Better he just use EZ-Activator as it will do all that, and assuming he hasn't converted/ran EZ-Activator already, it looks like his office is naturally VL so no need for license add. I always recommend the EZ-activator as it will do all that by default, so pretty much anything we used to ask is done and we see its results.
Btw.. how's the Restore function working in your tool?Is it perfect? Will it restore a MAK licence successfully,as I can't test it now,since none of the leaked MAK Keys have remaining activation count!!
So it means,I will not be able to restore tokens and get my activation back,when i do a format. Ok! thanks for your reply.
Just wondering. Would it be possible to change to 180 days..to say 1800 days..by that time Office 16 would be out
i have done all possible ways to cracking, using all methods from v2.0. after every time it says it is successfully activated, as soon as i open up MS Word 2010 (Pro Plus) or any other pro plus program, it tells me product license unactivated (as the tittle bar you know where it says MS Word 2010 -Document 1)
Problem Hello I have problems activating Office (tried both 64bit and 32bit) Prof. Plus. The Tool 2.0 seems to do the activation: 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. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. --------------------------------------- Attempting To Activate Office 2010 KMS Products. --------------------------------------- Installing AutoKMS. --------------------------------------- Office 2010 was succesfully activated. However, the check says: --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Grace Period Last 5 characters of installed product key: H3GVB REMAINING GRACE: 28 days (40116 minute(s) before expiring) --------------------------------------- I use Windows 7 64bit. Hope you can help me.
It didn't do the activation, this is a bug, which I have not had time to work on toolkit so its still broken. Try manual activation a few times to see if it works.
thanks for the quick reply. manual activation =Attempt office 2010 activation? the result is : Office 2010 failed to run activation! Here is a more detailed description about the error: Failed to start KMSEmulator.exe
AV is to blame. I see an opportunity to gather more info on why EZ-Activator failed. You can help me help you and others by doing the following. 1. Disable any AV (as failure to start KMSEmulator.exe almost certaintly means AV deleted it after it was written to disk) 2. Try EZ-Activator again with ALL security products that would interfere with KMSEmulator (AV firewall, etc, maybe even Windows Firewall) disabled. Show me the output, if EZ-Activator works, then its likely everyone with the EZ-Activator problem is having AV problems (and I'm failing to stop the code and throw error like manual activation did so it says successful (the successfully activated message is determined by the activation function in EZ-Activator NOT saying it failed, but if it never tried then it can't say it failed - something I need to change).
As a matter of fact, I removed my NIS exclusion and tried activation and can now get that error. Anyone with this error has AV interference (no wonder why I could not find a fault in detection of installed products). I plan to, so that EZ-Activator does not waste time failing in the middle, to make the first action of activation the KMSEmulator start, which would in case of AV failure harm nothing. @Everyone: I will do my part to eliminate the false success bug (and now I see it's a quick fix). however, note that it is triggered by AV, so disabling your AV or adding an exclusion (Which is a necessisity and I recommend the latter as I don't recommend a total shutdown of AV), so you need to resolve your AV configuration. Also I plan to make deletion of KMSEmulator automatically disabled by default (instead of enabled by default). this will help people who don't see it and then ask where it is (when its not there so it causes confusion). When I get the time (probably this weekend as I have a lot to take care of tomorrow and friday), I'll apply some changes and work on 2.0.1 (a minor release).
THANK YOU !!! It finally worked. I only deactivated AntiVir on the first times. Now having your hint to AV, I checked again and AVG was running too. Deinstalled AVG and it worked.
You had 2 AV? You do know that its bad practice to have 2 AV in general as they can fight each other and things go to hell as a result. Well good to see you got it and the issue that has eluded me is an easy fix (as a matter of fact some efficiency changes I plan soon (doing KMS Keygen first) would have inadvertantly fixed it without me realizing it).