I did, but it still shows this after a restart ------------------------------------ AutoKMS Ran At 8/23/2011 6:27:50 PM. Started KMSEmulator Attempting To Activate Office 2010. Successfully Set Office KMS Host To 127.0.0.1 Successfully Set Office KMS Port To 1688 Set KMS PID To: 55041-00168-305-190595-03-1033-3790.0000-2692009 Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Failed To Activate 10 Times. Stopped KMSEmulator. I guess I'm trying to understand what can make it fail so I can troubleshoot it. AV? Firewall? Office Version? I just built the computer, so I don't have a ton of stuff on it. I see where the KMSServer is running on the localhost IP (127.0.0.1).....Does it matter that I have that localhost IP listed in the HOSTS file to throw off Adobe Activation. Does anyone change this IP to their 192.168.1.XX address?....would it matter? Thanks for any help you can lend. LDN
Hosts is no issue. Be sure you are on latest version, as a older version may have issues. After making sure you have latest version, run EZ-Activator and post exactly what it says. I ask you to be sure you have the latest version as a 2.2 version (not 2.2.3) wasn't handling the PID right so EZ-Activator would work and not AutoKMS. This isn't giving the sign of an AV, as if you had an old enough version it would catch KMSEMulator.exe and AutoKMS log would indicate. A newer AutoKMS would more likely face AV issues in the form of AutoKMS.exe itself getting nuked. This looks like KMS is being done but a PID issue, and as I said a 2.2 version (but not the latest), had an issue with updating the PID in AutoKMS (this is why I want your version and EZ-Activator output, as I can tell by that). PS: Version is in file properties or in the title. Do not read version from any INI file.
The title says Office Toolkit 2.2.3 I ran EZ-Activator again and it states in console: --------------------------------------- Getting Office License 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 to VL. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. --------------------------------------- Getting Office License Configuration Information. --------------------------------------- Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Failed To Activate 10 Times. --------------------------------------- Changed PID to: --------------------------------------- Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Successfully activated after 2 attempts. --------------------------------------- Office 2010 was succesfully activated. --------------------------------------- The AutoKMS Log shows this (after restart) ------------------------------------ AutoKMS Ran At 8/23/2011 8:13:06 PM. Started KMSEmulator Attempting To Activate Office 2010. Successfully Set Office KMS Host To 127.0.0.1 Successfully Set Office KMS Port To 1688 Set KMS PID To: 55041-00168-305-190595-03-1033-3790.0000-2692009 Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Failed To Activate 10 Times. Stopped KMSEmulator.
Note how EZ-Activator has to set PID to blank to work, but the AutoKMS log shows it as the 55041. That is the problem. Uninstall AutoKMS (it's probably an older version), check settings and make sure the Office KMS PID there is set to blank (as in nothing, not the word), save settings, then install AutoKMS and try AutoKMS again.
The possibility of your AutoKMS being old tells me it may be a good idea to start including the version in the log...
To be honest I wish MS would make it impossible to convert. There is a lot of complexity in keeping the code and stuff for all versions, and it is a lot of extra stuff. Not having to take account of conversions would radically simplify things and reduce size. If MS wanted to detect a conversion it is stupid simple. Notice that when you do a license repair I know what is really installed? I simply check the Uninstall reg key to see if things are Office14.ProPlus or ProPlusR. The extra R means retail and if office is KMS activated it is converted. Conversion also doesn't work on C2R so that can be confusing. You can also look at the MSI codes in MSOCache and multiple places in the registry. If MS really cared they could OGA flag all that, though to get technical it would hardly help. Just install VL real version if that happens. This is why I always recommend VL install. Most retail need keys I don't have, and I had removed all retail keys to discourage this but found it just left people who needed a license repair up the creek without a paddle. So I support conversion, but probably never C2R. I can think of a theoretical way to convert a C2R app. The fault is the Registration key. A C2R'd office has none and won't look in the registry for it (the right entries under here is what allow office to use KMS on Retail. Given word is the same Retail or VL basically it just reads registration for what license to use. Those licenses also dictate behavior, like why you can't phone activate KMS and VL doesn't cripple itself in notifications). I haven't tried or care to currently, but C2R is just App-V, and I saw by googling a way to execute cmd inside the virtual setup, EX: Virtual Registry. If this virtual registry has a Registration key that is used by C2R office, I could edit it there simply by running my regedit commands inside the virtual store (I store in .reg files and import via cmd Regedit).
Here's screenshot of Office Toolkit 2.2.3 I assume you mean to edit the "settings.ini" that's in the same folder as "Office 2010 Toolkit.exe" and remove all of the bolded text below (before running it again). [SettingsID] ID=2.2.1 [Global] KMSServer=127.0.0.1 KMSPort=1688 KMSPIDOffice= KMSPIDWindows=55041-00168-305-190595-03-1033-3790.0000-2692009 ActAttempts=10 UseKMSEmulator=True AutoRemoveKMSHost=False VerboseCheckActivation=False ShowCMID=False [AutoKMS] Logging=True ActivateOffice=True ActivateWindows=True [AutoRearm] Retail2VL=True Logging=True [EZ-Activator] PIDAttempts=10 CMIDAttempts=10 InstallAutoKMS=True Retail2VL=True MAK2KMS=True StarterSub2Bypass=True RemoveRetailKeys=True ChangePID=True AutoLicRepairAll=True ChangeCMID=True AutoMakeRestoreBackup=True [Paths] AutoKMS=C:\Windows\AutoKMS AutoRearm=C:\Windows\AutoRearm By the way, if I hadn't said this before, thank you for the help! LDN
No I meant change settings via the built in settings button, but note that your Office one is blank. Did you reinstall AutoKMS and try again? An older toolkit had a AutoKMS bug where AutoKMS resets it's INI (which it has separate from OTK but OTK will change/update it if it is installed, and on install create based on OTK's settings.) Because it resets INI, it uses the default PID which you have seen, and your office just doesn't like that PID, but likes a blank one just fine. So hit uninstall for AutoKMS, then install, then run AutoKMS and check the log.
Thank you for the clarification......I uninstalled AutoKMS....I blanked out the PID...ran the install of AutoKMS again and I think that took care of it (the first log is right after the uninstall/reinstall and the other log is after a computer restart) ------------------------------------ AutoKMS Ran At 8/23/2011 8:55:04 PM. Started KMSEmulator Attempting To Activate Office 2010. Successfully Set Office KMS Host To 127.0.0.1 Successfully Set Office KMS Port To 1688 Set KMS PID To: NULL Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Successfully activated after 1 attempts. Stopped KMSEmulator. ------------------------------------ AutoKMS Ran At 8/23/2011 8:57:15 PM. Started KMSEmulator Attempting To Activate Office 2010. Successfully Set Office KMS Host To 127.0.0.1 Successfully Set Office KMS Port To 1688 Set KMS PID To: NULL Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Successfully activated after 3 attempts. Stopped KMSEmulator. Thank you for taking the time to help......I really appreciate it! LDN
I can confirm that i didnt delete install AutoKms i just removed the PIDS from the file,all is well,great app guys. This was for Windows 7 pos embedded
Hi CODYQX4 first thanks for amazing tools i just update to 2.2.3 and have several question : 1. on setting it seems AutoKMS always set windows7 activation by default, shouldn't it better disabled? i mean before using office, most people will already active their windows using retail product, winloader etc. shouldn't having it enable might cause conflict ? or it need to be enabled ? 2. cmiiw from what i see, 2.2.3 always schedule to run re-activation on startup if i want to change it, it seems i need to use AutoKMS custom task, right ? how i can set activation schedule to once a month or other setting ? EzActivator just working without problem, but it just me seeing that reactivation once a month is better than every startup thanks again
That setting means nothing unless you have a KMS key installed for windows. Older versions didn't check it but did try to activate anything if you did check it.
I am running Win7, with a quad core proc, 4gb ram This programme 'ToolKit' locks up on me every time I try running it, be it normally or as Admin, it just locks up and I get nowhere fast
What do you mean lock up? Does it run and freeze? What functions we're you using? Any more info would be helpful
As soon as I try to use EZ Activator it just freezes and locks up, I also tried activating office on the activator tab, same thing, freeze and lock. I cant close it without using Task Manager
What version of office? I know some (the crap trials) add lots of licenses and OSPPSVC runs at 99% cpu (not my fault) when it goes through. Try again and tell me if OSPPSVC is raping the CPU at high percentage. If so you may want to uninstall all office and use Pro Plus VL if not already. Note if in your case OSPPSVC is the culprit, it will eventually work, just take an absurd amount of time to do so.
Im using 2010 Pro Plus. Toolkit runs fine and is 'stable' untill I try any of the functions, it freezes and locks within 2 secs, it using no cpu at all and Ive left in open for over 2 hours, still froze and locked untill I use task manager to clear it