i'll look at the PID but I know I screwed up key checking on XP, because I set the wrong path to Office 2010's pidgenx.dll.
OK I think I found the problem. I never updated AutoKMS/AutoRearm because they never changed, but I bumped up the Settings version to 2.2.1, meaning autoKMS has setting version 2.2. I do this version thing when I change the structure of the ini, to force old ini's to change. Basically if you use an INI that is not the same version, the app makes a default version of its ini. Note that the version != to the app version, as I only change it if needed (V2.2.2 will have V2.2.1 setting version). All I need to do is remake AutoKMS/AutoRearm with the new version setting. Your PID setting doesn't stick because AutoKMS runs, sees the mismatch, and makes a default, giving you the default (ZWT) PID.
It was never made to be a ID for the app, and if someone has a problem I tell them to try the latest. Latest stuff can be Id'd by file version, something I never updated in earlier releases.
so what am i gonna have to do when the next version comes out since i keep getting this error with 2.2.1: ------------------------------------ AutoKMS Ran At 7/27/2011 3:53:57 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. uninstall what i currently have and run the new V2.2.2 toolkit?
I think V2.2.2 will be the grand release. V2.2 was released but all these bugs have popped up and I've added little bits of keys. I think this next version will securely be the basis for my next app, and I won't have to worry about this until I finish the next. That and I've implemented just about all the features I've thought of. Any more things I thought of will be Network KMS, in the next KMS tool. Effectively, as new stuff comes out, I may slowly move to an AIO, as I have a lot of Windows code and will add the previously mentioned resource trick as versions of office come out. I hope MS keeps using SPP/WMI stuff, as it means almost all the code will apply. I'll still have to make office setup patches and add their keys/licenses which is a massive pain to get, because I have to DL+Patch all versions/channels. Eventually I'd just have a product selection popup that would dictate what product to apply on. I don't see a Windows customize setup tab, and a license adder only makes sense if I added OEM certs, so I'd probably hide those if on Windows. I'd still need to write my own windows backup/restore code but Activation and Product Key tabs already have windows code that works.
@CODY A small suggestion, use a "keys.ini" feature in the next version of the toolkit, so that user can easily add new KMS products and their GVLK keys; just like DAZ's loader
Figured I might but now I have so many KMS Keys there aren't much, and you can still use the Custom Key install.
I'd most likely go this route later, but not now. I may readd Retail keys for the common versions just for more successes though.
Ok Cody, installed the OTK 2.2.2 - no problem. The settings.ini and the c:\windows\AutoKMS.ini work as they must work: [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=False [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 [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=False [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 and the log is: ------------------------------------ AutoKMS Ran At 01/08/2011 18:55:54. 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. Thank you very much for all and good work!
Hi Cody, Thanks again for all your great work on this! Small point: Like patrik's post above, I also show ID=2.2.1 in the [SettingsID] section ... I'm guessing it should be 2.2.2? I will happily live with it if this is the final final! ciao!
@Bosh I'm experimenting with the resource files, trying to make them more responsible for some things we do, so swapping the file out helps. I have added two little buttons, that dictate whether functions apply to office or windows. Basically the next app is to create a Windows+Office Toolkit. I am adding constants and lists of stuff, so that I can make some code more generic, so later changes don't break things. Basically the code right now is written in mind that it would only work on office 2010, and it would not be well ready to combine later office support into it. My tricks with the resource files can try and fix that without having to rewrite the code. I'll get as far as I can, I doubt I will add OEM stuff but I may later down the line. For now the windows stuff will heavily be KMS dominated, but just about all code will have a windows equivalent. I will try and upload the source when I finish or hit a roadblock, but this is basically future-proofing right now.