did anyone try this again? cscript c:\windows\system32\slmgr.vbs -skms kms.cc.columbia.edu cscript c:\windows\system32\slmgr.vbs -ato there is no ping but maybe activation can be done. It was a nice server afaic remember
Code: Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>cscript c:\windows\system32\slmgr.vbs -skms kms.cc.columbia. edu Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Key Management Service machine name set to kms.cc.columbia.edu successfully. C:\WINDOWS\system32>cscript c:\windows\system32\slmgr.vbs -ato Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Activating Windows(R), Enterprise edition (81671aaf-79d1-4eb1-b004-8cbbe173afea) ... Error: 0xC004F074 The Software Licensing Service reported that the computer coul d not be activated. No Key Management Service (KMS) could be contacted. Please s ee the Application Event Log for additional information. C:\WINDOWS\system32>
Have you figured out the "catastrophic" error? I'm getting the same error here.. View attachment 24830
Only happens with the 58.173.xx.xxx server for me, just use the 140.119.xx.xx one when it comes back online
Successfully activated from command line using this server 5 minutes ago. slmgr -skms host slmgr -ato First activated two days using KMSPico and Taiwanese server, changed server to this one and I'm back to 180 days
Is it possible for someone to find the Registry keys form a activated Pc Windows 8.1, so we could use them with the backup tokens, for offline activation ? NOTE: I have made a backup of my activated Pc (Windows 8.1 Enterprise) without using Sysprep, and using imagex.exe, Now i have a activated install.wim (from 26/10/2013 for 6 months), keeping my activation and user name and settings and setup. After installing the activated install.wim online OR offline, The system is ACTIVATED. So the activation keys must be in the Registry as well as the Tokens.
I bet this server actually runs CODY's KMS Server Service & for some days redirects to the Taiwanese KMS server. The "catastrophic" error occurs when an KMS V6 product receives KMS V5 request from a server/emulator.