Q: What does KMS-QADhooker do to my System? A: 1. Detect Windows CurrentBuild. If less than 9200, exit. Else set CB = CurrentBuild. 2. Detect Windows Channel. And If VOLUME_KMSCLIENT, detect/install KMS-QADhooker, activate/display. If TIMEBASED_EVAL, display. If permanently activated, display. If not permanently activated, or if key missed unexpectedly, call %CB% (9200/9600), detect Edition (e.g. Enterprise), install corresponding KMS key, detect/install KMS-QADhooker, activate/display. 3. Detect Office 2013 Channel. And If VOLUME_KMSCLIENT, detect/install KMS-QADhooker, activate/display. If permanently activated, display. If not permanently activated, detect Edition (e.g. ProPlus), install corresponding KMS certificates/key, uninstall Non-KMS key, detect/install KMS-QADhooker, activate/display. Q: What does KMS-QADhooker install to my KMS Client System? A: 1. Copy KMS-QADhooker.dll and KMS-QADhooker.exe into System Root (X:\Windows). 2. Import registry of KMS-QADhooker.exe (injector that injects KMS-QADhooker.dll into SppExtComObj.exe on activation demand) Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe] "Debugger"="KMS-QADhooker.exe" 3. Import registry of KMS-QADhooker.dll (KMS Server emulator integrated with IP Redirector) Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform]"VLRenewalInterval"=dword:00002760 "VLActivationInterval"=dword:00000078 "DisableKeyManagementServiceHostCaching"=dword:00000000 "VLActivationType"=dword:00000002 "KeyManagementServicePort"="1688" "KeyManagementServiceName"="192.168.1.255" "Windows"="55041-00206-271-777383-03-1028-7601.0000-3412013" "Office2013"="Random" Q: Where must KMS-QADhooker files be located in? A: Tested OK to be in the following places as Path listed. C:\Windows C:\Windows\System32 C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0 Code: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "Path"="C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\"
Hey mate, in times you might feel underappreciated always remember that a lot of us started here as complete noobs and look how far this led us . I'm frequently checking in here for some inspiration as i know i will find (mostly i'm fast enough before you delete your posts ). And i know i'm not the only one. Please do us the favour to not delete your posts ... see them the way they are ... a work log. And btw check guide doggies signature . Regards my friend
Q: In times you might feel underappreciated. A: No. I have no time for begging/expecting for thanks. On the contrary, I care if my post is useful. Or delete if useless/off-topic/out-dated/fulfilled to keep forum clean. Q: To not delete your posts for a work log. A: Yes. I hear and obey if my post is useful.
And kmspico has not been uninstalled from Windows 8.1 ProWMC before KMS-QADhooker applied? Install_and_Forget.cmd or $OEM$? Thanks.
Didn't try with the previous version. I can say, by the way, that if i unistall the Office 2013 through the windows unistaller it works good. If i try to unistall it with the Microsoft Toolkit i'll get another error: "class not valid" Normal unistall/install again doesn't fix the problem. The Office 2013 version is the x64 proplus 2013
kmspico uninstalled,Install_and_Forget.cmd, and to clarify, I think my activation service is messed up, perhaps there is no problem with your application. thank u.
nechrist has the same issue, but he is with Microsoft Toolkit. I'll try to see if there's anything I can do about it. Please allow me some time. Thank you.
Got it. Thank you for your feedback. If you need my hand on KMS-QADhooker, feel free to call me anytime.