Microsoft Toolkit - Official KMS Solution for Microsoft Products This is a set of tools and functions for managing licensing, deploying, and activating Microsoft Office and Windows. All output from these functions is displayed in the Information Console. All functions are run in the background and the GUI is disabled to prevent running multiple functions, as they could conflict or cause damage if run concurrently. The Microsoft Office Setup Customization Functions (Customize Setup Tab), AutoKMS Uninstaller (if AutoKMS is installed), AutoRearm Uninstaller (if AutoRearm is installed), Office Uninstaller and Product Key Checker work even if Microsoft Office or Windows is not installed/supported. For information about individual functions, see the program readme. Requirements: Microsoft .NET Framework 4.0 or 4.5 (Not 3.5) Microsoft Office 2010 or Later for Office Toolkit Support Windows Vista or Later for Windows Toolkit Support Microsoft Toolkit Changelog: 2.5 -Added ability to specify KMS Hardware ID. -Added KMSPID option to reuse the last KMSPID from KMS Activation. -AutoKMS gives messages about what type of KMS Server it is connecting to. -Can install AutoKMS alongside KMS Server Service to be able to use it for LocalHost KMS Activation. -Disabled DefaultKMSPID as a valid option for KMS Server Service (please change it to RandomKMSPID if you have it set to DefaultKMSPID) -Fixed KMS Server Service Installer arithmetic overflow by changing the way Service Handles were compared to NULL -If KMS activation fails twice with DLL Injection, kill KMS Connection Broker with each further attempt -KMSPID options (not for KMS Server Service) set to ReuseKMSPID by default. -Use DLL Injection is now the default LocalHost Bypass method Credits: -Bosh for the original GUI Design and co-development of Office Toolkit -ZWT for the original KMSEmulator -letsgoawayhell, Phazor, nosferati87, and mikmik38 for KMSEmulator fixes and improvements -MasterDisaster, FreeStyler, Daz, nononsense, and janek2012 for work on Key Checker EXE MD5*: 7F8A3114659A0ADAA572F0E9E4255BFC *CODYQX4 recommends checking the md5 hash with a tool such as hashtab to verify the file, especially if you have any problems. Project Homepage: http://forums.mydigitallife.info/threads/28669-Microsoft-Toolkit-Official-KMS-Solution-for-Microsoft-Products