From bb82ea3e65ce76bd4e7f4bdff67455fdfaf11a8d Mon Sep 17 00:00:00 2001 From: DESKTOP-RBH716R\Admin Date: Wed, 10 Aug 2022 22:31:29 +0530 Subject: Checked with Grammarly --- _site/kms38.html | 80 +++++++++++++++++++++++++++----------------------------- 1 file changed, 39 insertions(+), 41 deletions(-) (limited to '_site/kms38.html') diff --git a/_site/kms38.html b/_site/kms38.html index f2ae40c..e28b037 100644 --- a/_site/kms38.html +++ b/_site/kms38.html @@ -403,7 +403,7 @@ div.tocify {

  • How to use it? Please find the instructions here.

  • This activation method activates Windows 10/11 and Windows Server -(14393 and later builds), until 19 january 2038 03:14:07 UTC.

    • +(14393 and later builds), until 19 January 2038 03:14:07 UTC.

  • This activation method does not store any files on the system.

  • This activation method works offline.

    • @@ -424,10 +424,10 @@ href="(https://github.com/abbodi1406/KMS_VL_ALL_AIO)">KMS_VL_ALL by abbodi1406

    MAS (Online KMS option)

    -

  • Any KMS Activator which is not compatible with KMS38, may +

  • Any KMS Activator which is not compatible with KMS38 may overwrite the KMS38 activation for Windows with its own 180 days activation, thereby destroying the KMS38 activation for Windows. To -prevent this accidental overwriting, you can select KMS38 protection +prevent this accidental overwriting, you can select the KMS38 protection option.

    • @@ -437,27 +437,27 @@ option.

    Q: Can Microsoft block this kind of activation?
    A: Not directly. They could only update Clipup to allow -for a maximum activation period of 180 days. Not much beside that can be -done on their part. The tickets are not sent to Microsoft at all, so +for a maximum activation period of 180 days. Not much besides that can +be done on their part. The tickets are not sent to Microsoft at all, so they can’t block them or take action directly.

    @@ -714,8 +714,7 @@ activated.

    versions.

  • ServerRdsh edition does not officially -support activation on non-azure systems. However on all builds except in -range of 22000 will activate Windows.

    • +support activation on non-azure systems.

    @@ -729,21 +728,20 @@ href="(https://github.com/abbodi1406/KMS_VL_ALL_AIO)">KMS_VL_ALL by abbodi1406 or MAS (Online KMS option) for Office activation, then you don’t need to enable this protection.

    -

  • However, with a few tricks you can ensure that no alternative KMS -Activator can replace KMS38 Activation by accident or even on purpose. -below is the explanation for how to do/undo that.

    • -

  • In the KMS activation method, the Windows first checks the KMS IP +

  • However, with a few tricks, you can ensure that no alternative +KMS Activator can replace KMS38 Activation by accident or even on +purpose. below is the explanation for how to do/undo that.

    • +

  • In the KMS activation method, Windows 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 (IP range -127.0.0.0/8) is defined as KMS IP in the Windows 8 and later 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 and at -the same time that KMS activator can be used for Office -activation.

    • +127.0.0.0/8) is defined as KMS IP in Windows 8 and later OS 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 and at the same time +that KMS activator can be used for Office activation.

  • Script steps-

    @@ -900,9 +898,9 @@ command.

    • Setup Preactivate
    -- cgit v1.2.3