Yes, I'm also eager to know what's wrong with it... I didn't do anything special when installing it, that's why I'm wondering... btw.: Not only Office, but also Windows 8.1 (x64) suffers from the same strange 0x80070002 error. What I found out regarding SWbemObjectEx is, that it should reside in the Wbemdisp.dll, which is there in the folder c:\windows\system32\wbem\ So dunno... A positive feedback for such a great work is the least any user should do / give. So absolutely no thanks needed. Keep up the good work. Regarding your edit: I also had already tried version "KMS-QADhooker_for_V5-V6_Localhost_O15-Select_Abbodi1406_Way_28.Mar.2014", with the exact same result. Or did you mean another version I should try?
Did you uninstall KMSpico 9.2.3 fully before running KMS-QADhooker? KMS-QADhooker does not have the function of KillProcessOnPort if there was another Emulator in place. Only KMS-QADhooker running on my machine: Code: Activating Windows(R), Enterprise edition (81671aaf-79d1-4eb1-b004-8cbbe173afea) ... Product activated successfully. Name: Windows(R), Enterprise edition Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel Partial Product Key: DRQ3H License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 05426-00206-271-587804-03-1028-9200.0000-0162014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeAccessVL_KMS_Client edition (6ee7622c-18d8-4005-9fb7 -92db644a279b) ... Product activated successfully. Name: Office 15, OfficeAccessVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: 4JM2D License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 05426-00206-234-364885-03-1028-9200.0000-1222014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeExcelVL_KMS_Client edition (f7461d52-7c2b-43b2-8744- ea958e0bd09a) ... Product activated successfully. Name: Office 15, OfficeExcelVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: BG7GB License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 05426-00206-234-308550-03-1028-9200.0000-0602014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeInfoPathVL_KMS_Client edition (a30b8040-d68a-423f-b0 b5-9ce292ea5a8f) ... Product activated successfully. Name: Office 15, OfficeInfoPathVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: F8894 License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 05426-00206-234-798790-03-1028-9200.0000-1192014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeLyncVL_KMS_Client edition (1b9f11e3-c85c-4e1b-bb29-8 79ad2c909e3) ... Product activated successfully. Name: Office 15, OfficeLyncVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: TCK7R License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 06401-00206-234-547158-03-1028-9600.0000-3042013 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeOneNoteVL_KMS_Client edition (efe1f3e6-aea2-4144-a20 8-32aa872b6545) ... Product activated successfully. Name: Office 15, OfficeOneNoteVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: P34VW License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 55041-00206-234-243249-03-1028-7601.0000-0362014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeOutlookVL_KMS_Client edition (771c3afa-50c5-443f-b15 1-ff2546d863a0) ... Product activated successfully. Name: Office 15, OfficeOutlookVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: 2PMBT License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 06401-00206-234-594766-03-1028-9600.0000-0382014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficePowerPointVL_KMS_Client edition (8c762649-97d1-4953- ad27-b7e2c25b972e) ... Product activated successfully. Name: Office 15, OfficePowerPointVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: 4RD4F License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 06401-00206-234-218320-03-1028-9600.0000-3432013 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficePublisherVL_KMS_Client edition (00c79ff1-6850-443d-b f61-71cde0de305f) ... Product activated successfully. Name: Office 15, OfficePublisherVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: FCXK4 License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 06401-00206-234-931608-03-1028-9600.0000-0732014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Activating Office 15, OfficeWordVL_KMS_Client edition (d9f5b1c6-5386-495a-88f9-9 ad6b41ac9b3) ... Product activated successfully. Name: Office 15, OfficeWordVL_KMS_Client edition Description: Office 15, VOLUME_KMSCLIENT channel Partial Product Key: 4GBJ7 License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: KMS Most recent activation information: Key Management Service client information Client Machine ID (CMID): f2c22437-b086-4798-b096-2c293988211f Registered KMS machine name: 192.168.1.255:1688 KMS machine IP address: 192.168.1.255 KMS machine extended PID: 55041-00206-234-812446-03-1028-7601.0000-0752014 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching is enabled Press any key to continue . . .
I'm 100% sure, that I've never run anything else than KMS-QadHooker before. As I've said... I only tried KMSpico 9.2.3 after this script failed (and this happened for the first time) - so no way anything could interfere. Furthermore I've only used the portable version of KMSpico, because I don't like to pollute the system too much.
I have been testing continuously on all available devices, but failed to reproduce the issue. (Unless the CTR was incompletely uninstalled on my end.)
I think the errorcode indicates that your system cannot find the hooker.exe at the specified path. I guess there is a mismatch between the file path specified under the Debugger registry setting and that of hooker.exe file on the disk.
Would you please do KMS-QADhooker manually: View attachment For-Helfritz.7z Step 1. Uninstall KMS tools. Step 2. Copy For-Helfritz\KMS-QADhooker\32or64\System32\KMS-QADhooker.dll and KMS-QADhooker.exe to X:\Windows\ or X:\Windows\System32\ Step 3. Import SppExtComObj.reg by Double-click Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe] "Debugger"="KMS-QADhooker.exe" Step 4. Import KMS-Parameters.reg by Double-click Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform] "VLRenewalInterval"=dword:00002760 "VLActivationInterval"=dword:00000078 "KeyManagementServiceName"="192.168.1.255" "KeyManagementServicePort"="1688" "DisableKeyManagementServiceHostCaching"=dword:00000000 "VLActivationType"=dword:00000002 "Windows"="Random" "Office2013"="Random" Step 5. slmgr /ato (Optional - Because VOLUME_KMSCLIENT Windows and Office 2013 will auto-activate) These (step 2, 3 and 4) are all elements of KMS-QADhooker for activating VOLUME_KMSCLIENT Windows 8/8.1/Server 2012/2012 R2 and Office 2013 if installed on them.
@xinso: Yep, this worked like a charm. Both Windows and Office activated without any problems. I then additionally tried to execute "uninstall.cmd" (I moved the kms* files to c:\windows\ to be able to have success) followed by a "install and forget.cmd", but this still fails with the exact same error as before. I also checked if the path variable had been correctly set, but there does not seem to be any mistake. I even tried to turn off the Windows Firewall... not using any Antivirus app and I've disabled Windows Defender. That's pretty much all relevant part that comes into my mind... Nevertheless... although it's strange... If I'm the only one, we really should not care that much... EDIT: Wah... laughing my ass off... I guess there's something really broken with my SppExtComObj.exe. I tried to call that file now and guess what: Code: C:\Windows\system32>SppExtComObj.Exe The system cannot find the file C:\Windows\system32\SppExtComObj.Exe. C:\Windows\system32>
Preventing AV to detect and delete KMS solutions as threads. It's well know AV firms are working to M$ in this respect as seen with MTK, KMSpico, etc. Therefore, are/is there any files/folders to exclude your solutions from AV eyes? I've been using $oem$ folders from the following solutions: KMS-QADhooker_for_V5-V6_Localhost_O15-Select_Abbodi1406_Way_28.Mar.2014 KMS-QADhooker_Localhost_V5-V6_O15-RTM-CTR-Slipstream_Cypher85-Way_05.05.2014_00.44
@xinso I guess any further releases of yours will be uncompressed by UPX just like these ones, right?
More than the development advances, the less I understand handling to be followed lol Is it possible to have images or other to reproduce handling correctly ? Please