Administrator Popular Post draww Posted July 9 Administrator Popular Post Share #1 Posted July 9 Method 1 - PowerShell On Windows 10/11, right-click on the windows start menu and select PowerShell or Terminal. Copy-paste the below code and press enter Hidden Content Give reaction to this post to see the hidden content. You will see the activation options, and follow onscreen instructions. That’s all. Method 2 - Traditional Download the file from Hidden Content Give reaction to this post to see the hidden content. Right click on the downloaded zip file and extract In the extracted folder, find the folder named All-In-One-Version Run the file named MAS_AIO.cmd You will see the activation options, and follow onscreen instructions. That’s all. Homepage -> Hidden Content Give reaction to this post to see the hidden content. 42 10 1 1 Link to comment
Administrator Popular Post draww Posted September 25 Author Administrator Popular Post Share #2 Posted September 25 Changelog: 2.0 Minor update: Add info in check activation scripts to ignore ospp.vbs /dstatus results if Ohook install is found. Changelog: 1.9 Ohook: Added Ohook activation method, it can activate Office permanently on Windows 8 and higher and their Server equivalent except Office 2010 and Office UWP apps. Thanks to @asdcorp for this new method. More info Hidden Content Give reaction to this post to see the hidden content. Hidden Content Give reaction to this post to see the hidden content. HWID/KMS38: HWID activation is added for IotEnterpriseS 2024. At the moment, the 2024 version of IotEnterpriseS and IotEnterpriseSK have HWID activation, EnterpriseS/SN don't More checks are added to find better error details for: Internet issue WMI issue SvcRestartTask issue Services issue Some codes are optimized Online KMS: Script will create schduled task files in C:\Program Files\Activation-Renewal instead of C:\ProgramData\Activation-Renewal due to security reasons The script is updated as per @abbodi1406 KVA v50. Changes: Fixed conversion for Office 2016 C2R Retail previously, the first run mistakenly said conversion had failed, even though it was successful (due to confusion with Office 2019 licenses/location detection) Added support for activating Windows 10 IoT Enterprise LTSC 2021 (LCU 19044.2788 or later) Change Windows Edition: Script will use @ave9858 (Alex) DISM API method instead of changepk.exe method to change from Windows 10/11 Core to Non-core (e.g. Home to Pro) Advantages: Internet doesn't need to be disabled, all OEM/GVLK key restrictions are removed, and better error output Script will only use best methods to change edition instead of showing multiple choices Troubleshoot: Script will compress large log files to cab instead of deleting and creating them fresh in DISM restore and SFC scan options WMI fix is improved All: Insert HWID key script is removed because it's not important and causes confusion Scripts will now disable quick edit mode temporarily because users often click inside the script window and it pauses the script Check is added for Null service at the start of the script because corrupt service crashes the script Codes are optimized and fixed a few bugs 13 4 1 Link to comment
Bl4ckCyb3rEnigm4 Posted September 27 Share #3 Posted September 27 HWID isn't working because of changes made by Microsoft, so for now use KMS38 5 Link to comment
Administrator draww Posted October 2 Author Administrator Share #4 Posted October 2 Changelog: 2.1 HWID: Added info for activation not working issue. It's not working because of server-side changes at Microsoft. Use the KMS38 option for now. Your previously established HWID is safe. This happened because of recent change to not allow Windows 7/8 free upgrades. Ohook: Change the key preference for Office products in this order Retail:TB:Sub > Retail > OEM:NONSLP > Volume:MAK > Volume:GVLK Fixed a few bugs 5 1 Link to comment
Popular Post Bill_Boquet Posted October 3 Popular Post Share #5 Posted October 3 Hidden Content Give reaction to this post to see the hidden content. Changelog: 2.2 A New Hope For HWID HWID: A new method is discovered to activate with HWID. Hidden Content Give reaction to this post to see the hidden content. Thanks a lot to the Hidden Content Give reaction to this post to see the hidden content. and team for the discovery. 13 2 1 Link to comment
Administrator draww Posted October 19 Author Administrator Share #6 Posted October 19 Changelog: 2.3 Bug Fixes Ohook: Script is updated to use v0.4 Ohook. It will help in preventing license check banner in non-admin, Domain joined and future new user accounts. Script is updated to find and remove remnants of Office vNext license for all user accounts in registry. Change Edition: Script will check for Pending reboot flags before proceeding with Edition change with DISM. Change to ServerRdsh edition is blocked in the script since it’s policies often can not roll back. All: Scripts will now check for updates and notify users. Some other bugs fixed. 3 2 Link to comment
Bill_Boquet Posted October 21 Share #7 Posted October 21 Hidden Content Give reaction to this post to see the hidden content. Changelog: 2.4 Minor update Ohook: Reverted the Ohook version back to 0.3. We noticed some Antivirus detections (false positive), possibly due to the registry adding change introduced in 0.4. The downside of 0.3 is that the Ohook script would need to be run again upon new user account creation in Windows if O365 is installed. Separate files version for Ohook script is changed to AIO. Users don’t need to update their Ohook installation with this update. 10 1 Link to comment
Administrator draww Posted November 15 Author Administrator Share #8 Posted November 15 Changelog: 2.5 Added Support For New Editions HWID: Added support for the Windows 11 IoTEnterpriseK edition. KMS38: Added support for Windows Server 2025 editions. Ohook: Added support for Microsoft Office 2024 (Preview) editions. Fixed a delay issue in checking user account SIDs if a lot of users are added to the domain-joined system. All: Fixed a delay issue in checking WPA registry keys Optimized some codes and fixed a few bugs 4 2 Link to comment
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now