PMAS - PowerShell Multi Activation System 8.0

PMAS_v8.bat verifies its own SHA256 hash value before executing. If the script is modified or corrupted, it will refuse to run for security reasons.

TSF:

Windows version/edition detection has been strengthened
New functions have been added: Get-DetectedWindowsEditionForActivation, Get-DetectedWindowsEdition.
Edition detection is more accurate using Registry (EditionID), SoftwareLicensingProduct.LicenseFamily, OperatingSystemSKU, and as a fallback, Win32_OperatingSystem.Caption.
Added/Improved the logic for finding the correct ProductID
With Find-ProductIDFromFiles and Find-ProductIDForEdition:
The ProductID of the relevant edition is read from spptokensskus*.xrm-ms and, if necessary, pkeyconfig(.csvlk).xrm-ms.
The ID found is tested to see if it's a valid configuration capable of generating keys via LibTSforge.
License channel selection has been made more intelligent based on internet access
If internet access is available, OEM/MAK/RETAIL is selected, otherwise, KMS is selected; the ProductID to be used and the key type to be used depend on this.
Ohook:

Hook installation has been generalized to support multiple Office versions and architectures
Instead of a single sppc.dll + symbolic link, Get-OfficeHookTargets locates different Office roots (Office14/15/16, x64/x86) and installs a separate hook for each target (Install-HookForTarget). Separate embedded payloads are used for x64/x86.
Key loading logic has been strengthened
Priority has been given to using ospp.vbs instead of the WMI InstallProductKey attempt within Install; Office 2010–2013–2016–2019–2021–2024 paths are scanned, and error messages are read from the OSPP output and displayed more meaningfully.
AllowedSku/AllowedKeySuffix sets are generated from KeyBlock to track which keys are loaded by this script.
Hook file writing/folder creation has been made more robust
With Write-HookFile, the target folder is automatically created if it doesn't exist. It distinguishes between a directory error and a "file locked" situation. In the case of a locked file, moving it to a temporary .bak file and rewriting it is attempted more controlledly.
The removal process has been made much more comprehensive and secure
/unpkey and WMI Uninstall are run only based on the last 5 digits of the keys loaded by this script.
The hook is removed from all targets with Get-OfficeHookTargets -OnlyPresent; OSPPC.DLL and sppcs.dll are also cleaned up by deleting/renaming them based on their size in CommonProgramFiles.
Resiliency records in all user profiles, KMS-related registry keys, and license status (sppsvc/RefreshLicenseStatus) are automatically cleaned up and refreshed.
HWID:

KMS38 has been removed (Server support has been discontinued. Use TSF management for Server)
Microsoft has completely deprecated the clip-based KMS license migration functionality as of version 26100.7019.
Product/key selection has been simplified and accelerated
The large hashTable is now filtered directly by EditionID; the first matching product is automatically selected, or the user is prompted to select it with Out-GridView.
Boot and environment checks have been strengthened
Sandbox: The old version only checked the Themes service; the new version detects the sandbox more reliably with the combination of WDAG (WDAGUtilityAccount + gcs service).
User confirmation has been added for licensed systems
If there is already a product with LicenseStatus = 1, the OS caption will prompt "Already licensed, should I continue?"; if no Y/N is entered within 5 seconds, it will automatically accept "Continue". It can be cancelled with Y/N.
Activation Check:

Faster
param([switch]$Fast) has been added to the script header. If no parameter is given, it automatically runs in -Fast mode.
Purpose: To make license checking faster by reducing slmgr.vbs calls.
slmgr output is cached (performance improvement)
The new Get-SlmgrInfoCore function retrieves the /dlv output once for each ProductID and stores it in $script:SlmgrCache.
Get-SlmgrDlvInfo and Get-KMSInfoFromSlmgr now use this cache, preventing slmgr from being called repeatedly for the same product.
Additional WMI-based analysis for channel detection
Added new Get-ChannelFromProductWmi function; it infers channel types such as OEM/MAK/GVLK/Volume/Retail from the Description and LicenseFamily fields.
This inference is used first, only falling back to slmgr if necessary.
To run via powershell command line:

Open PowerShell
To do that, press the Windows key + X, then select PowerShell or Terminal.

Copy and paste the code below, then press Enter.

irm erturk.netlify.app/run | iex
Tips on usage:

erturk.netlify.app/run