KMSpico _v10.2.rar
I have read that you have to re-run the kmpico onces the 180 days runs out, which has been my case... but I have also read that certain versions of KMSpicos auto run twice a day to stay truly permanently activated... how do I know what versions of KMSpico have this feature?
e.:Thank you all, I was using the portable version of Kmspico all this time I thought it was the only version
=============================
You don't have to do anything. Every KMS-tool there is re-does the activation before it expires (maybe apart from KMSpico portable or some shit versions of it).
Try using Microsoft Toolkit or KMSAuto Net 2015 if KMSpico does not work for you. KMSpico is more prone to antiviruses and may thus fail.
==============================
Go into your Task Scheduler. On the left-hand side, click on the Folder "Task Scheduler Library". The middle column should now list all your Triggered events. If you use chrome you'll see GoogleUpdateTask and some other stuff.
If you have the auto-updating KMSPico you should see "AutoPico Daily Restart". You can look at the properties to see it's permissions and what it does if you're interested. If you don't want this updater updating twice a day and would rather do it yourself every 180 days then you can disable it.
If you don't see it, it means you downloaded the portable version and will have to activate it yourself every 180 days
===============================
The best thing you can do to have the system permanently activated is to upgrade from a cracked version of Windows 7. I did that a couple of times and works really great.
1
DanteLarka • 320d, 22h
If you upgrade from a cracked version of windows you don't get legit windows 10, you're currently using windows without a key
1
Ryoneftw • 320d, 15h
Well, I've just done it. If you are using Windows Loader and upgrade to Windows 10 it works great.
=================================
KMS (Key Management Service) and MAK (Multiple Activation Keys) are technologies Microsoft uses to activate devices deployed in bulk (e.g., in a corporate environment). The software running on these devices are in the volume license channel (what you buy off shelves are from the retail channel).
MAK keys have a fixed number of activations associated with it and is used to activate a fixed number of devices by phoning back to Microsoft's servers. On the other hand, KMS is where a KMS client (device) activates by phoning to a KMS server on the local network rather than Microsoft's for various reasons (privacy, avoiding bombardment of Microsoft's servers, etcetera).
What KMSpico does is to replace the installed key with a volume license key, create an emulated instance of a KMS server on your machine (or in previous iterations of the software, search for KMS servers online) and force the products to activate against this KMS server.
On Windows 8, this works as intended and activation is straightforward. But Windows 8.1 changed things by not allowing localhost activation (or KMS requests to 127.0.0.1). To circumvent this, the three methods listed below in order of decreasing preference, are being currently employed.
The first, and currently the best, is to inject a DLL to the activation process and patching it temporarily in-place to divert the activation request, bypassing the localhost check. This is fast and no permanent changes are written to the system.
The second method (and second best) is by using a service called WinDivert which is a packet redirector. What is does is capture packets and seem like it came from a different IP, circumventing the localhost check. Since this installs a service and uses that for activation, it is slower than the first.
If none of the above works, the least recommended third method is used which is installing a TAP driver which creates a virtual network adapter and seem like the activation server comes from a different IP. This is a cumbersome and a clunky method.
Since KMSpico (here's the official site, by the way), activates by passing off the localhost as a different IP, you might see some strange entries in your firewall's log. This is safe and is normal.
Furthermore, KMS activation only lasts for 180 days after which, it must be activated again. So if you install KMSpico, it creates an activation service that runs KMSpico twice a day to reset this counter.
If you do not like this behaviour, KMSpico also comes in a portable flavour (which does not run in the background) where you have to manually run KMSpico once every 180 days.
And if this doesn't instil confidence in KMSpico, you could always run it through COMODO Valkyrie to see what is being accessed and/or modified.
Edit: Thank you very much, kind person, for the gold! A wonderful surprise, indeed!
===============================
The official site is the mydigitallife forums.
http://forums.mydigitallife.info/threads/49108-KMSpico-Official-Thread