I don't know exactly, but so far only those 3 IPs are used for check i never included the firewall block rule in my scripts because so far i see that this check is a side effect, doesn't harm activation status and if microsoft decided to deactivate us, they can find ways beyound simple 3 IPs
@abbodi sir, when win 8.1 is installed it auto downloads these KBs viz 2895219, 2894179, 2894029, 2889543 AND 2883200. Do these KBs have anything to do with activation or just for the smooth working of the o/s as claimed by MS for some KBs ? ( i have not gone through the purpose for which these updates are released). Thanx
I am using KMS_VL_ALL-SppExtComObjPatcher-kms. Running KMS_VL_ALL results in failed activation. However, running 1-SppExtComObjPatcher then 2-Activate-Local results in successful activation. After that I run 1-SppExtComObjPatcher again to remove the SppExtComObjPatcher. Then I tried KMS_VL_ALL, surprisingly now it works. And I thought it is all done but the strange stuff is running KMS_VL_ALL the second time will result in failed activation again. The workaround still work though. It's just me? I didn't change any system intrusive softwares like AV // Firewall. I did windows update though. EDIT Multi run of KMS_VL_ALL from KMS_VL_ALL-SECOInjectorV242 works just fine. I think I will stick with this one because once KMS_VL_ALL-SppExtComObjPatcher-kms failed, all your script (other package, tap, seco) will fail too.
Okay, I have taken a look at the readme file, but I am rather confused: are both methods for permanent activation, or are they just for 180 days? I am not too sure what the difference is between "standalone" and "auto renewal" activation, aside from the fact that they are not opposites of one another. All activation should be for auto-renewal, no? If not, what purpose would it serve?
KMS activation mechanism is based on 180 days, not permanent. standalone means it activates your products once and doesn't keep any files or registry tracks in your system, so you will need to use it once again when the 180 days expires. auto renewal installs two files in the system and adds some registry settings so it can make use of the internal kms renewal engine, thus the activation is renewed automatically every 7 days (the default period if you didn't change it).
KMSAuto Net Console v1.0.4 and KMS Server Service v1.1.2 by Ratiborus New KMSAuto Net Console v1.0.4 and KMS Server Service v1.1.2. DL here. New KMSSS.exe integrated into KMSAuto Net Console.exe file with appropriate HWID and ePID (55041-00206-109-000005-03-1033-7601.0000-2822013). Both from a genuine M$ KMS Server.
I ran test on different systems using different keyboard/mouse so click should not be fast. Still on 2.06 i encountered same error. made changes on servicec.cmd in 2.05 and 2.06 REM @echo off on 1st line and captured output. attaching capture of both 2.05 and 2.06 when executed on same system.
KMS Server, KMS Server Service, KMS Client and KMSAuto Net Console by Ratiborus KMS Server, KMS Server Service, KMS Client and KMSAuto Net Console by Ratiborus These are intended for advanced users only. KMS Server v1.1.1 File : KMS_Server_v1.1.1.zip Size : 147.37 KB CRC32 : 7d8e5af0 MD5 : c15613e865cd2425b4045ee2224afe0b SHA1 : 3c3cd99c77fdb02c830c64e1c841727aef727d1d KMS Server Service v1.1.2 File : KMS Server Service v1.1.2.zip Size : 146.10 KB CRC32 : 9fef1a45 MD5 : 5ecb8f2489ea36921edd8ceb947963a5 SHA1 : de47312beb090a0cfe46f4eb201eea5ba63f7dd3 KMS Client v1.1.1 File : KMS_Client_v1.1.1.zip Size : 96.74 KB CRC32 : e1e19565 MD5 : 589624377576b1015b13e362be9d3b20 SHA1 : 0bce076aadce2480a33c348488cd6511228f54c6 KMSAuto Net Console v1.0.5 - the Management Console for KMSSS.exe - Runs on Windows XP, 7, 8, 8.1 - .Net Framework 4.0 required. File : KMSAuto Net Console v1.0.5.zip Size : 241.19 KB CRC32 : 489de1e0 MD5 : ee06a3c1f816807076adc596bc40ffcf SHA1 : 532e57fe399166ee9ecc522014807885c7d29fc4 Changelog: Spoiler KMSAuto Net Console v1.0.4 - New KMSSS.exe integrated into KMSAuto Net Console.exe file with appropriate HWID and ePID (55041-00206-109-000005-03-1033-7601.0000-2822013). Both from a genuine M$ KMS Server. KMS Server Service v1.1.2 - appropriate HWID v1.1.1 KMSSS, KMSS - improved IP addresses filtering on the client computer. KMSC - just cleaned up the code. v1.1.0 CMD line parameters can be specified in any sequence. Command Line Parameters: -Port <Port Value> - KMS Port. Range from 1 to 65535 -PWin <PID> - Windows PID -PO14 <PID> - Office 2010 PID -PO15 <PID> - Office 2013 PID -AI <Interval> - Activation Interval. Range from 15 to 43200 minutes -RI <Interval> - Renewall Interval. Range from 15 to 43200 minutes KillProcessOnPort - Force open the KMS Port if this is present. -Log - Log file Enabled. -IP - Show IP adress Clients Computers. -IPFiltrOFF - No IP Filtrs.
Code: netsh advfirewall firewall add rule name="Key Management Services 1" protocol=TCP dir=out localport=443 remoteip=65.52.98.231 action=block netsh advfirewall firewall add rule name="Key Management Services 2" protocol=TCP dir=out localport=443 remoteip=65.52.98.232 action=block netsh advfirewall firewall add rule name="Key Management Services 3" protocol=TCP dir=out localport=443 remoteip=65.52.98.233 action=block So far these three IPs have been involved. No, the commands are only for Windows Firewall, for third-party firewalls you need to do it manually.
KMS Server, KMS Server Service, KMS Client, KMSAuto Net Console and KMS Server Info KMS Server, KMS Server Service, KMS Client, KMSAuto Net Console and KMS Server Info by Ratiborus These are intended for advanced users only. KMS Server v1.1.1 File : KMS_Server_v1.1.1.zip Size : 147.37 KB CRC32 : 7d8e5af0 MD5 : c15613e865cd2425b4045ee2224afe0b SHA1 : 3c3cd99c77fdb02c830c64e1c841727aef727d1d KMS Server Service v1.1.5 File : KMS Server Service v1.1.5.zip Size : 157.40 KB CRC32 : 523ea972 MD5 : 6bfcfea0024da46e2a96d0b0f982447c SHA1 : 974c376b9e7f9baa6767ca2089be822cc505cb7a KMS Client v1.1.1 File : KMS_Client_v1.1.1.zip Size : 96.74 KB CRC32 : e1e19565 MD5 : 589624377576b1015b13e362be9d3b20 SHA1 : 0bce076aadce2480a33c348488cd6511228f54c6 KMSAuto Net Console v1.0.5 - the Management Console for KMSSS.exe - Runs on Windows XP, 7, 8, 8.1 - .Net Framework 4.0 required. File : KMSAuto Net Console v1.0.5.zip Size : 241.19 KB CRC32 : 489de1e0 MD5 : ee06a3c1f816807076adc596bc40ffcf SHA1 : 532e57fe399166ee9ecc522014807885c7d29fc4 KMS Server Info v1.0.1 File : KMS Server Info v1.0.1.zip Size : 118.33 KB CRC32 : 52bc4595 MD5 : 8d5b6c786fe54aceae4fec2e4d2b6a4f SHA1 : 830f7945284c1b06d67418f36747102b983c314c
I've just installed the new Windows 8.1 leak (Win8.1 9600.16596.WINBLUES14_GDR_LEAN.140114-0237 in x64) and have successfully activated it with KMS Dashboard but Office 2013 will not activate. I've also tried using KMSpico and on installing it throws up an error to say its stopped working. Can anyone suggest an alternative kms method to activate office 2013 on Win8.1 9600.16596.WINBLUES14_GDR_LEAN.140114-0237 in x64 Thanks in advance