From 11e4fd98988e0fd7f56d45afbec989a2ddcaa260 Mon Sep 17 00:00:00 2001 From: DESKTOP-RBH716R\Admin Date: Mon, 25 Jul 2022 22:26:46 +0530 Subject: MAS 1.6 --- _site/readme-hwid.html | 256 ------------------------------------------------- 1 file changed, 256 deletions(-) delete mode 100644 _site/readme-hwid.html (limited to '_site/readme-hwid.html') diff --git a/_site/readme-hwid.html b/_site/readme-hwid.html deleted file mode 100644 index 3e3aa70..0000000 --- a/_site/readme-hwid.html +++ /dev/null @@ -1,256 +0,0 @@ - -ReadMe - HWID - - - - - -
-
-====================================================================================================
-   [HWID] Digital License Activation:
-====================================================================================================
-
- - This activation is supported for Windows 10/11 ONLY.
- - This activation does not store any files in your system.
- - This activation is a permanent activation for your system Hardware.
-
- - On a system, this activation can be created for all the supported editions, and all can be 
-   linked to Microsoft account without any issues.
-
- - Once a system is activated, this activation cannot be removed. (Because the license is stored in 
-   the Microsoft servers and not in the user's system.)
-
- - Any significant changes in the Hardware (such as a motherboard) may deactivate the system. 
-   It is possible to reactivate a system that was deactivated because of significant hardware
-   changes, IF your activation, was linked to an online Microsoft account.
-
- - For activation to succeed, the Windows Update Service and internet connectivity must be enabled.
-   If you are trying to activate without these conditions being met, then the system will auto-
-   activate later when the conditions are met.
-
- - Auto activation scenario after the Windows reinstall:
-   - The Internet is required. (Only at the time of activation)
-   - The system will auto-activate if Retail (Consumer) media was used for the installation.
-   - The system will NOT auto-activate if VL (Business) media was used for the installation.
-     In this case, the user will have to insert that windows edition Retail/OEM key (find keys below
-     in this page) to activate, if the user doesn't wish to activate again using this script.
-
- - Possible reasons for activation failure:
-   - The Internet is not connected.
-   - Windows update service is disabled.
-   - Use of a VPN, and/or a privacy-based hosts file, firewall rules.
-   - Corrupt system files.
-   - Microsoft servers block the activation request from some countries such as Iran.
-   - Rarely, Microsoft's activation servers are the problem.
-   - Some machines are not able to generate GenuineTicket.xml file using gatherosstate.exe
-     The reason is unknown (to me). Please contact me if it happens to you.
-
-   * Check Troubleshoot Script in the "Extras" section if you are facing issues with activation.
-
- - Check Extract OEM option in the "Extras" section if you want pre-activated Windows installation.
-
- - Further read on how it HWID activation works: https://massgrave.dev/readme-activation-faq.html
-
-====================================================================================================
-   Downlevel and Lockbox Ticket for HWID:
-====================================================================================================
-
-   Downlevel = downlevelGTkey
-   Lockbox   = clientLockboxKey
-
-   Downlevel Method:
-   It creates downlevelGTkey ticket for activation with simplest process.
-   
-   LockBox Method:
-   It creates clientLockboxKey ticket which better mimics genuine activation,
-   But requires more steps such as,
-   - Cleaning ClipSVC licences
-   - Deleting a volatile and protected registry key by taking ownership
-   HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ClipSVC\Volatile\PersistedSystemState
-   - System may need a restart for succesfull activation
-   - Microsoft Account and Store Apps may need relogin-restart in the system
-
-   Further read: https://massgrave.dev/readme-activation-faq.html
-
-   Note:
-   Microsoft accepts both types of tickets and that's unlikely to change.
-   If you are not sure what to choose then select default Downlevel Method.
-
-====================================================================================================
-   Supported Products:
-====================================================================================================
-
-   Windows 10/11:
-
-   XGVPP-NMH47-7TTHJ-W3FW7-8HV2C   Enterprise
-   3V6Q6-NQXCX-V8YXR-9QCYV-QPFCT   EnterpriseN
-   VK7JG-NPHTM-C97JM-9MPGT-3V66T   Professional
-   2B87N-8KFHP-DKV6R-Y2C8J-PKCKT   ProfessionalN
-   4CPRK-NM3K3-X6XXQ-RXX86-WXCHW   CoreN
-   N2434-X9D7W-8PF6X-8DV9T-8TYMD   CoreCountrySpecific
-   BT79Q-G7N6G-PGBYW-4YWX6-6F4BT   CoreSingleLanguage
-   YTMG3-N6DKC-DKB77-7M9GH-8HVX7   Core
-   XKCNC-J26Q9-KFHD2-FKTHY-KD72Y   PPIPro
-   YNMGQ-8RYV3-4PGQ3-C8XTP-7CFBY   Education
-   84NGF-MHBT6-FXBX8-QWJK7-DRR8H   EducationN
-   43TBQ-NH92J-XKTM7-KT3KK-P39PB   EnterpriseS_2019           [LTSC 2019]
-   NK96Y-D9CD8-W44CQ-R8YTK-DYJWX   EnterpriseS_2016           [LTSB 2016]
-   FWN7H-PF93Q-4GGP8-M8RF3-MDWWW   EnterpriseS_2015           [LTSB 2015]
-   2DBW3-N2PJG-MVHW3-G7TDK-9HKR4   EnterpriseSN_2016          [LTSB N 2016]
-   NTX6B-BRYC2-K6786-F6MVQ-M7V2X   EnterpriseSN_2015          [LTSB N 2015]
-   DXG7C-N36C4-C4HTG-X4T3X-2YV77   ProfessionalWorkstation
-   WYPNQ-8C467-V2W6J-TX4WX-WT2RQ   ProfessionalWorkstationN
-   8PTT6-RNW4C-6V7J2-C2D3X-MHBPB   ProfessionalEducation
-   GJTYN-HDMQY-FRR76-HVGC7-QPF8P   ProfessionalEducationN
-   NJCF7-PW8QT-3324D-688JX-2YV66   ServerRdsh
-   V3WVW-N2PV2-CGWC3-34QGF-VMJ2C   Cloud
-   NH9J3-68WK7-6FB93-4K3DF-DJ4F6   CloudN
-   XQQYW-NFFMW-XJPBH-K8732-CKFFD   IoTEnterprise
-   QPM6N-7J2WJ-P88HH-P3YRH-YY74H   IoTEnterpriseS
-   K9VKN-3BGWV-Y624W-MCRMQ-BHDCD   CloudEditionN
-   KY7PN-VR6RX-83W6Y-6DDYQ-T6R4W   CloudEdition
-
-   Note - X86-X64 and ARM64 architecture systems are supported.
-        - Any Evaluation version of Windows (i.e. 'EVAL' LTSB/C) cannot be activated.
-        - LTSC 2021 is not supported, IoTEnterpriseS 2021 key will be used to activate it.
-        - LTSC N 2019, 2021 are not supported.
-
-====================================================================================================
-   Switches for the Script (Separate Files Version):
-====================================================================================================
-
- - To activate with Downlevel method (default), run the script with /a parameter
-"HWID_Activation.cmd" /a
-
- - To only generate GenuineTicket.xml with Downlevel method (default), run the script with /g parameter
-"HWID_Activation.cmd" /g
-
- - To enable LockBox method, run the script with /k parameter
-   You need to use this option with either activation or ticket generation. 
-   Example,
-"HWID_Activation.cmd" /a /k
-"HWID_Activation.cmd" /g /k
-
-====================================================================================================
-   File Details:
-====================================================================================================
-
-   https://massgrave.dev/readme-hwid-kms38-files.html
-
-====================================================================================================
-   Manual Activation Process:
-====================================================================================================
-
- - Prerequisite:
-
-   For Windows 10-11 x86-x64 system, you need following files, (Get it from MAS separate files version)
-   gatherosstate.exe
-   slc.dll
-
-   For Windows 10 ARM64 system, you need following files,
-   arm64_gatherosstate.exe
-   arm64_slc.dll
-   * Rename the ARM64 files to gatherosstate.exe and slc.dll respectively.
-
-   Make a folder named 'Files' in C drive, [C:\Files] and copy the required files in that folder.
-
-   -------------------------------------------------------------------------------------------------
-
- - Make sure the Windows Update Service and internet are both enabled.
- - Open a command prompt (run cmd.exe) as administrator, and enter following listed commands in the 
-   the sequence in which they are given.
- - Enter Retail/OEM Key, (Replace '%key%' with the key from the above list) with the following command:
-
-cscript /nologo %windir%\system32\slmgr.vbs /ipk %key%
-
- - Make sure slc.dll and gatherosstate.exe files are located in the folder, "C:\Files" and enter 
-   the following commands to generate GenuineTicket.xml file.
-
-   For x86-x64 systems,
-
-pushd "C:\Files"
-rundll32 "C:\Files\slc.dll",PatchGatherosstate
-call "C:\Files\gatherosstatemodified.exe"
-
- - Now a GenuineTicket.xml file should be created in the folder "C:\Files\", copy and paste this file in the 
-   folder named, "C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\"
-
- - Now apply this ticket using the following commands in this sequence:
-
-net stop ClipSVC
-net start ClipSVC
-
- - Activate Windows with the following command:
-
-cscript /nologo %windir%\system32\slmgr.vbs /ato
-
- - Check Activation Status with the following command:
-
-cscript /nologo %windir%\system32\slmgr.vbs /xpr
-
- - Done.
-
-   * Note - [clipup -v -o -altto ] method to apply the ticket was not suggested because
-            of the issues in case the username have spaces or non English characters.
-
-=========================================================================================================
-   Credits:
-=========================================================================================================
-
-   @mspaintmsi   Original co-authors of HWID/KMS38 Activation without KMS or predecessor install/upgrade
-        &        Various methods of ticket generation and improvements for slc.dll
-   *Anonymous    nsaneforums.com/topic/316668--/?do=findComment&comment=1497887
-
-   @qxkqf        ARM64 port of @mspaintmsi's slc.dll 
-
-
-   Acknowledgements:
-
-   @vyvojar      slshim
-                 github.com/vyvojar/slshim/releases
-
-   @sponpa       New ideas for the HWID/KM38 Generation
-                 nsaneforums.com/topic/316668--/page/21/?tab=comments#comment-1431257
-
-   @leitek8      Improvements for the slc.dll
-                 nsaneforums.com/topic/316668--/page/22/?tab=comments#comment-1438005
-
-   Source codes collection:
-   app.box.com/s/y71tpcamofcg6zv6k7by6gaex6om3q4d
-_______________________________________
-
-   Kind help and snippets:
-
-   @BAU          Reg_own lean and mean snippet
-                 pastebin.com/XTPt0JSC
-
-                 Compressed2TXT
-                 github.com/AveYo/Compressed2TXT
-
-   Scripting help:
-   @RPO, @BAU, @abbodi1406
-
-   ARM64 testing:
-   @Imoagn, @moderate, @Chibi ANUBIS, @smashed
-
-   English grammar fix:
-   @BorrowedWifi
-
-   Thanks for resolving my queries:
-   @awuctl, @sponpa, @leitek8, @mxman2k, @mspaintmsi, @Yen, @BAU, @RPO, @abbodi1406
-
-_______________________________________
-
-   Microsoft Activation Scripts:
-
-  Homepage: massgrave.dev
-     Email: windowsaddict@protonmail.com
-
-=========================================================================================================
-
- -

 

- - - -- cgit v1.2.3