It tells me this: Code: License Info Was Not Deleted! Here is a more detailed description about the error: Eccezione lanciata da un componente esterno. (I have an italian Windows 7 and Office 2010) Tomorrow I'll try installing from a Volume installer.
OK, good things happen when people provide sufficient information. A few people have pointed out this problem. I have observed that all of them converted from Retail to VL (or at least tried to). I have two possible theories. 1.VL License Install or Key Install Fails so that VL is not detected (Appears to be your case) 2.VL conversion succeeds but status does not update so it does not recognize VL. (Someone showed me a half converted Office but EZ-Activator didn't mention it). When I'm not busy I'll look into the code more, I have not been able to work on things with craploads of tests and homework so maybe this weekend.
Hi, I would like to thank CODYQX4 for this toolkit., it's just great. I did install it and it worked perfect for few days, after rebooting the computer, the AV ESET started to alert me about the KMSEmulator.exe, I was clicking the no action key, normally it will accept the file when I was clicking no action to, but it didn't, and ask me few times, than the installation failed, any idea, how to deal with it.
Thats the info from the Toolkit: 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. --------------------------------------- EZ-Activator Failed! Here is a more detailed description about the error: Failed to start KMSEmulator.exe
I've decided now the first thing I will do upon activation is start the KMSEmulator so AV doesn't make it fail halfway through. As you see all the stuff that could have occured before running keygen.
How do I use this tool to get rid of this MSDN licensing? I had KMS licensing, but removed it to add my retail HUP license/key. That worked, but I ALSO have this stubborn MSDN license. Office thinks the HUP one is activated but also wants me to activate the MSDN one, which is strange since I've never owned or even tried it. I see no mention of an MSDN license anywhere in Lic/Key Management. SKU ID: 42cbf3f6-4d5e-49c6-991a-0d99b8429a6d LICENSE NAME: Office 14, OfficeProPlusMSDN-Retail LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Notifications Mode Last 5 characters of installed product key: BBKQ8 REMAINING GRACE: 0 days (0 minute(s) before expiring
You could enter custom key and enter BBKQ8, or set the combo boxes in Key Management to Retail and Professional Plus then hit remove. If you do not currently have KMS license active, it will just reinstall that key, so make sure you have KMS license, if not, use EZ-Activator.
I did try "set the combo boxes in Key Management to Retail and Professional Plus then hit remove," but that only removes my valid retail HUP key, which is what I'm trying to transition to. However, now that you mention the key, and now that I've re-read the Readme, I see that Uninstall should work against just the key regardless of how the boxes are set. Hopefully when I do that, the mysterious MSDN one will go (I'll report back). I'm a little confused though by your mention of KMS. If KMS does come back automatically, I'm going to remove it, since HUP is retail. I've found that if KMS still exists, Office will not take a retail key. On this particular system, I'm actually trying to get back to a legit, retail Office. Strange, I know.
OK I understand, your retail is legit and you don't want KMS. Well then just remove that BBKQ8 by entering that in custom key and hit uninstall, then add your legit retail key using custom install (enter full key for retail). When you open office with new retail key it will probably ask for activation, just do it online if you haven't already.
Sorry but I'm a complete newbie at this sort of thing but since I've installed OFFICE 2010 and the EZ Activator I'm getting VBINJECT! trojan errors on a regular basis. Online these appear to be severe threats and I'm a little worried. This only began after I ran EZ Activator on Office 2010. Is this a false positive on the Microsoft Security Essentials or is there a genuine virus lurking in this app? I'd be grateful for any information or advice that any of you can give me
Joined on this forum just to reply to this; Since 2007 Thinstall (now ThinApp) has been around, which solves the "multiple Office Suite's installed side-by-side" issue. Basically it makes [almost] any program portable, outputs an .exe [now that VMware has bought it, sometime a .cab as well], then you just launch the exe, and you're done
In the end I managed to solve the problem without having to reinstall Office from a volume installer. It's hard to tell how exactly I solved the problem... I think the problem was that the retail license was somehow corrupt and so it was impossible to install a volume license or Delete All the licenses to "start from scratch". I think I solved by installing a retail key, by Deleting all the licenses and then by installing a volume license (although is hard to remember if I also deleted the retail key to be able to delete all the licenses without the error). After checking that the volume license was there, I managed to activate it and install AutoKMS. I hope this is helpful.
I would not recommend ThinApping 2010. It was easy to do 2003 or 2007 by just using a VL key (which didn't require activation or check PC HW). Since 2010 always requires activation, I doubt you could just ThinApp, move it, and it work on another PC forever.
I think he means that with thinapp he could get the office 2003 problem solved, instead of using registry tweaks.
Hi folks, just tried to d/load the EZ-Activator from the link on page 1, but I am getting 403 Forbidden error. Is there any problem or can someone give me a alternative d/load link? Thanks -VS