siinus
/
Microsoft-Activation-Scripts
mirror of https://github.com/massgravel/Microsoft-Activation-Scripts
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Open-source Windows and Office activator featuring HWID, Ohook, KMS38, and Online KMS activation methods, along with advanced troubleshooting.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26 Commits
2 Branches
18 Tags
12 MiB
 
Tree: a03754a676
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a03754a676'
${ noResults }
Microsoft-Activation-Scripts/MAS_1.2/Separate-Files-Version/Extras/KMS38_Protection
Windows_Addict d076838483
Initial commit 		5 years ago
..
Protect_Unprotect-KMS38.cmd Initial commit 5 years ago
ReadMe.txt Initial commit 5 years ago

ReadMe.txt 

====================================================================================================

   KMS38 Protection:

====================================================================================================



 - If you don't know what KMS38 is, then first check it in the Read Me.



 - By default, a KMS38 Activation is vulnerable to unintended overwriting/replacement and 

   neutralization by a 180-Day KMS Activator (non-KMS38 Activator).

   However, with a few tricks you can ensure that no alternative KMS Activator can replace KMS38 

   Activation by accident or even on purpose. This script demonstrate how to do/undo that.



 - Protect KMS38:

   - How does KMS38 Protection work?

     In the KMS activation method, the Windows Operating System first checks the KMS IP registered 

     as a specific KMS, and if that is not defined then it checks the Global KMS IP.

     Another fact is that if LocalHost (127.0.0.2) is defined as KMS IP in the Windows 8.1 and 10 OS's

     then Windows will not accept it as a valid KMS IP.

     This script simply utilizes the above facts to protect the KMS38 activation from being 

     overwritten by any alternative 'normal' 180-Day KMS Activation.



     Script steps-

     - Check if Windows is activated with KMS38, if yes,

     - Set that Windows edition specific KMS IP to LocalHost (127.0.0.2),

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\55c92734-d682-4d71-983e-d6ec3f16059f\XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

where X is Windows edition Activation ID.



     - Lock this Registry with Reg_takeownership snippet by @AveYo aka @BAU

       pastebin.com/XTPt0JSC

     - Done.



 - Unprotect KMS38:

   - Just undo above steps,

     - Give administrator full control of that mentioned registry key.

     - Delete that registry key.

     - Done.



====================================================================================================