Dear @Dark Vador , I updated your script a bit, automated a lot of the work but there are still some missing parts. ☺️ Is there a way to permanently activate Office products with the zerocid method using this script with a Retail or MAK product key? I just couldn't figure it out ☺️ Features: LibTSforge.dll Integration: The script loads the LibTSforge.dll file, which is Base64 encoded, into memory. If the file is present, it will be loaded; otherwise, it will be decompressed from Base64 and loaded into memory. Random KMS IP Address Setting: For KMS or Volume licensed products, the script generates a random KMS IP address and sets it in the Windows registry. This helps prevent the "Genuine" license warning. Activation for Different License Types: KMS (Key Management Service) licenses for activation. VIRTUAL MACHINE ACTIVITY for AVMA (Automatic Virtual Machine Activation). MAK, RETAIL, and OEM licenses for activation. Retail Office Products: The script detects retail (consumer) Office products, but it does not perform automatic activation for them. Product Selection and Activation: The script provides a user interface (Out-GridView) for selecting Windows and Office products for activation. Users can choose products and start the activation process. Product Information Retrieval: The script detects the license status of installed Windows and Office products on the system. Version Detection: The script uses the LibTSforge library to detect the current version of the product, and based on this, it performs the appropriate activation. Key Generation: The script generates random product keys and applies them to the corresponding products. Supported Versions: Windows: Windows 10 and later versions (supports zerocid activation). Office: Office 2013 and later versions, particularly for KMS licenses. Compatible with Office 2016 and later versions. (supports KMS activation). User Input: -w: Selects only Windows products for activation. -o: Selects only Office products for activation. When these parameters are used, the script activates only Windows or Office products. If both are selected, it activates both Windows and Office. If no parameters are provided, the user is prompted with a selection screen to choose the products to activate. Special Cases: VIRTUAL_MACHINE_ACTIVATION license type: Works only on Windows Server Datacenter editions and requires Hyper-V or QEMU virtualization environments. While the script indicates success, real activation status may be verified through the slmgr.vbs -dlv command, which might show the actual activation state.
So now you want to install list of massive amount of mak license's, wmi command will be very very slowly In case of rtool, I remove all license, and reinstall vol & mak license And client* and pkeyconfig* license^s * But for a specific product
Got an idea, do query of all office license * specific vol Search for mak same product Not found, search for mak license Install them, than re load license list
TSF Activation updated Thansk @Dark Vador and @Windows_Addict https://github.com/abdullah-erturk/tsf_activation