Has anyone still got the MD5 Sum for the 2.1.6 version? I will stick to this version for a little while longer since 2.2 has given me constant "virsus" warnings. I know that it is a false alarm, but 2.1.6 has given me none. I downloaded 2.1.6 from an unofficial source and need to verify whether the thing is real or "modified". Thanks in advance! ReaperBLN
V2.2.1 is up, don't bother with 2.1.6. I fixed the browsing and the key checker, also added new keys. Activation stuff hasn't changed so no need to update AutoKMS/AutoRearm.
I just downloaded 221 again and the hash does not match. The EXE within the archive has a hash of CB3DE9BC2CEF71670541D3131B90C6DC
@CODY Multipoint Server 2010 and 2011 share same KMS key, u should add this fact in the Product Selection tab!! @muhkka My result is same as urs
Sorry, screwed up the hash and didn't notice. CB3DE9BC2CEF71670541D3131B90C6DC is the right hash for 221. Updated it, must have made a clipboard mistake. The 2010-2011 thing I found out recently, and its because 2011 is basically a SP for 2010. Many change the selector to say 2010/2011 but I'm not going to update just for that, especially since MultiPoint users are few. The key updating is me getting closer to starting my next KMS app. Still waiting to make sure V2.2.1 is all good, so test and report.
Hashes for latest release: CRC32: 7409D4C3 MD5: CB3DE9BC2CEF71670541D3131B90C6DC SHA-1: 38275F5B0090B764ACDD53BBC65A9907972B65EF @Cody, First, thanks for this wonderful tool. I had a small question regarding its usage.... If I have taken a backup of my office 2010 license and activation status with v2.2, can i do a restore using v2.2.1 or do I need to stick with v2.2 only... Also, I have had a problem once before where the genuine key i was using had maxed out its allowed no. of activations. now i am using a different key, and taken a backup using your tool, but there is a problem with my office installation (thesaurus part is not working,and MS has no proper solution for me). if i do a full uninstall and thorough cleanout of the registry for office 2010 using the "fix-it" tool that MS provides to completely remove 2010, and then try to do a fresh install of office 2010, will restoring my license from your backup reactivate it fully as before, without affecting the activation count at MS servers ??? i will ofcourse reinstall on the same machine so no other hardware/software changes will be there. all i want to do is attempt an absolutely thorough wipe out of 2010, and then reinstall it on the same machine and reactivate it with the same key as before without affecting the activation status records on the MS servers and get my thesaurus problem fixed. will it work?
I have to go back to V2.1.6 V2.2.1 detecting as a Virus but actually it's not a virus, I'll wait for next Version hopefully will fix by then.
Hi Cody, I have a problem! /The first time from all previous versions. I am using the 2.2.1 version on Office 2010 x86 installed on Windows 7 Ultimate x64 All is ok (exclusions in Eset AV, firewall, settings, etc. etc.) But after 2 reboot I have this autokms log: ------------------------------------ AutoKMS Ran At 28/07/2011 10:50:29. 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. ------------------------------------ AutoKMS Ran At 28/07/2011 10:53:33. 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. But if a see the activation check in the OTK information Console I reed: --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c OID: 018040-105925-290433-565530-930012-003346-999964-380294-393131 LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated ERROR CODE: 0 as licensed Last 5 characters of installed product key: H3GVB REMAINING GRACE: 180 days (259181 minute(s) before expiring) --------------------------------------- What happens? Ty for the attention
It almost certainly won't be 'fixed'. Cody is focusing on enhancing the Toolkit where it really matters and for what it was meant to do... It wouldn't be practical for him to re-write the program everytime its been picked up by AV tools. Same applies to all related programs i.e. activators, key generators, loaders. Even Media Player Classic HC is being pickup by my AV tool for suspicious keylogging activity, so better get used to it
I'm still using v2.1.6 also because v2.2.x gets picked up easily, 2.1.6 was written to avoid AV detection in the first place, that was the whole point of v2.1.6 using the modded keygen & PID change, in v2.2 we have to go back to being detected again & i can't be bothered to add it to exclusions.