A common misconception. As long as your KMS server is available, nothing has to be redone. Furthermore, your OS will even pass validation. So how is it a non-permanent solution? If anything, a loader is a less permanent solution and certainly a less reliable one. Not to mention it's a hackish binary that comes with no source code and, since it's executed before any protection comes online, is allowed to do anything to your system without being noticed. ;-)
KMS and SLP are based on two totally different principles. A direct comparison is therefore a bit like comparing apples and oranges, however, i would have to agree that technically KMS is the cleaner and therefore superior solution as it involves no tampering whatsoever with the system itself. • You install a publically available GVLK included with every Win7 DVD • You redirect the KMS HostMachineName to your own loopback • You tell Windows to activate • The Host tells Windows what it wants to hear and Windows complies Thats it, Windows is activated, meaning it requires no hardware patching, no software patching, no memory patching, no leaked PKeys, no leaked Certs, no fake SLICs, no special master boot records, no files of any sort constantly residing on the harddrive, nothing. The only 'trickery' involved is simply that the Host is lying to Windows when it replies "Yes, we are 25 properly licensed PCs here so lets all activate". Technically this makes a KMS activation no different from a Retail activation via a Microsoft activation server because technically it is just as genuine. The same can of course not be said about faked SLPs. But, of course thats only the technical part. Then there is of course the practical part, which is where the preference factor comes into play. Would i rather renew the activation twice a year since i prefer an untouched system or would i rather accept a little 'touching' since i prefer not having to deal with renewals? Could i live better with the fact that the renewal request might require a retry in case the KMS Host throws an error in my face or could i live better with the possibility that i will need to dig up a new BIOS Mod or Loader in case an update/service pack/whatever kills the one currently in use? Obviously these kinds of questions cannot be answered in a global manner. Clearly there are pros and cons to both methods, but which ones ultimately outweigh the others is something everyone has to determine for themselves. In the end there is no definitive winner from a practical POV, which means both methods have a right to exist even if the technical superiority clearly goes to the (hardware-independent) KMS method...
I agree Phazor, KMS is a clean method depending on how you set it up but arguably my "preserve boot code" option then modifies nothing at all which is on par with KMS. As I said though, the only reason I commented on the post was because prodigy was trying to say it's "hackerish", "less permanent" and then talked about it as though it's infecting users. All I have to say to that is that it doesn't modify files, theres a source and it doesn't exactly fake a SLIC, it injects a SLIC but Windows can't tell the different at all. It's just an insult for anyone to say such a thing without having any understanding as to how the loader actually works and how much time we put into the project.
I wouldnt worry, Daz. You have refined the SLP method like probably no other and your work is certainly nothing to be ashamed of. More to the contrary, so just keep up the good work.
My os windows server 2008 R2 standart 2 days plase activations ballon.. your KMS Activator 5.0.exe testing finished message tkenx.
Please reupload KMS Activator 5.0.exe, dead link! @ Phazor When I downloaded KMS Activator 5.0 from the link you provided I found this... So please re-upload the file, thanks a lot.
There are mirrors a couple of posts below the release post, these should still be up. The test/alpha version is incomplete (no keys, no machine name setting etc.) and should therefore not be used by anyone except testers. EDIT: Replaced original download link in release post with link to post with mirrors...
Windows 7 Enterprise 32 bit Hi. I have the 90 day trial of the full version of Windows 7 Enterprise 32 bit OS. Now, I wanted to know how can I keep it activated forever w/full access to updates when the trial is over. I haven't installed this yet because of this and the key is embedded in the thing. So I guess that once I install it and run it, it will automatically activate online once connected to the internet. I was thinking maybe there's a way to change the key to a full version key before I install it. Can this be done? Is it possible? Or should I just use the loader or the RemoveWAT 2.2.5.? How much does this thing cost anyway? Is it better than Ultimate? What's the difference between this one and the others? Is there a 64 bit of this? Thanks.
1) Effectively Enterprise and Ultimate are the same thing only with a different name and a different type of activation. 2) There are only 3 types of keys for Enterprise, and these are EVAL, MAK and GVLK. The simplest way to turn your EVAL into a 'full-version' is to remove the evaluation/trial packages with DISM and then use KMSA 5.0 to install the GVLK and activate. If you need any help with any of this just tell us what you need to know.
MAK key retrieval Is there any way to retrieve the MAK key from a Win 7 Enterprise legally activated with a volume MAK ? I know that neither EVEREST or Belarc work. I there any alternative ? Or is it an impossible task ?
Friend, Would you send me KMS-Activator-5.0 on this e-mail because I can't download it tsvyatko.kotsev @gmail.com Thanks
Code: slmgr /cpky Will remove information about the key so it can't be extracted for the express purpose of preventing people from jacking work's MAK. If you don't get anything useful from a key finder, or indeed if "slmgr /dlv" returns a partial key of "BBBBB" that's most likely what happened.