Microsoft Toolkit is a set of tools for managing licensing and activation of Microsoft Office and Windows. Microsoft Toolkit is a new version of the activator with support for Windows 7/Server 2021 and Microsoft Office 2021. After launch, Microsoft Toolkit checks which operating system or office is installed on the computer and selects the best option for activation.



Microsoft Toolkit is a set of tools for managing licensing and activation of Microsoft Office and Windows. Microsoft Toolkit is a new version of the activator with support for Windows 7/Server 2021 and Microsoft Office 2021. After launch, Microsoft Toolkit checks which operating system or office is installed on the computer and selects the best option for activation.

Opportunities:
The program has several tools for managing, deploying, and uninstalling Microsoft products. When launched, it checks which version of the operating system and Office is installed on the computer, and then selects the best option for installing a license.

The program also has the following features:
If activation in one way fails, it will automatically correct the error and reactivate with another method.
Displaying detailed information about the operating system or Office - which key is activated, when the license expires, which version is installed.
Convert Retail to Volume license.
Backing up an existing license, which after reinstallation will make it possible to quickly restore activation.
Installing and configuring a KMS server. You can configure the server automatically and manually.
Automatic reactivation of Microsoft products after the expiration of the key.

The program is suitable for activating Windows, starting with Vista. Microsoft Office activation is available for version 2003 and newer. To run it, your computer must have the Microsoft NET Framework 4.0 update package installed. For Windows 10 this is not a problem as the package is built in automatically.

The following advantages of the Microsoft Toolkit can be highlighted:
Unlike other programs for installing a license, Microsoft Toolkit is absolutely safe and displays all actions taken on the command line.
Works with both 32-bit and 64-bit versions of Microsoft products.
The simplicity of the interface, thanks to which even an inexperienced user will understand the activator.
All actions are performed automatically.

Activation information:
EZ-Activator: This is a simple setup for KMS activation. Unlike previous versions, it cannot use KMS activation if you are using a retail license. EZ-Activator collects information about your licensing status to provide the best activation method. It can automatically attempt possible errors in the event of an activation failure, and can undo all changes in the event of a complete failure.
It automatically installs all KMS Keys for your system, attempts to activate only for a KMS license, and if successful, installs AutoKMS automatically.

AutoKMS: AutoKMS Scheduled task that will automatically renew for 180 days KMS activation. Unlike other KMS activators, AutoKMS does not run 24/7 or only at the last minute with the hope that it will not fail, and leaves no trace other than the scheduled task itself, the log and the executable. It only tries to activate KMS licenses (which saves a lot of time if you have non-KMS licenses like MAK or retail active). It will run at startup and then every 24 hours and try to activate a certain number of times (task schedules cannot be changed). The Install/Uninstall buttons are used to install or uninstall AutoKMS.

AutoKMS пользовательской задачи: Заменить по умолчанию AutoKMS Запланированные задачи с пользовательским тот, который не будет сброшен. Вы можете настроить триггеры так, как вы хотите в Task Scheduler.

Full description of Microsoft Toolkit tabs:
KMS Settings tab:
Use KMS server/port: Allows you to set which KMS server and port should be used when trying to activate KMS. If you don't have a real KMS server or a network host running a KMS emulator or server, you need to set the value to 127.0.0.2. The port to be used will be the one specified in the number field. KMSEmulator will use this port, but it must be open on your computer or the process using it may be terminated.
NOTE: The Office KMS Server/Port is used when activating Office-based products, and the Windows KMS Server/Port is used when activating Windows-based products.

KMS PID to Use: Allows you to set which extended KMS PID should be used by KMSEmulator when trying to activate KMS.
Changing the PID can help fix persistent KMS or KMS activation failures that fail Genuine Validation, but in most cases you want to leave this setting alone.
You can pass a valid KMS PID, a DefaultKMSPID string to use a hard-coded default (blacklisted! DO NOT USE!), a RandomKMSPID string to generate a random string that matches the KMS PID format, or a ReuseKMSPID string to use the latest KMS PID, generating Random KMS PID if KMS PID is not found.
NOTE: The Office PID is used when activating Office-based products, and the Windows PID is used when activating Windows-based products.
NOTE:You cannot change the KMS PID used to activate KMS for real KMS servers. If the KMS server or KMS PID fails Genuine Validation, this setting will be required for an unlocked KMS PID.

KMS Server Hardware ID to Use: Allows you to set which KMS server hardware hash (added in KMS V6) should be used by KMSEmulator when trying to activate KMS.
Changing the Hardware ID can help fix situations where KMS fails Genuine Validation, but in most cases you want to leave this setting alone.
You must pass a 16 character string containing only valid hexadecimal characters (0-9, AF).
NOTE: You cannot change the KMS Hardware ID used to activate KMS for real KMS servers. If the KMS server or KMS Hardware ID fails Genuine Validation, this setup will require an unlocked KMS Hardware ID.

Activate with KMS emulator: Uses the KMS emulator to perform KMS activation. If you do not have a real KMS server or a network host running a KMS emulator or server, you need to enable this option.

Remove KMS Host/Port After Run: Removes the KMS server name and port from the registry after KMS activation.

Force Open KMS Port by Terminating Processes: Terminates all processes using a KMS port so that you can run a KMS emulator on that port.

KMS Server Service tab:
KMS Port to Use: Allows you to set which KMS port the KMS server service will listen on. Any clients using this service must use this KMS port.

KMS PID to Use (Global Default): Allows you to set which extended KMS PID this service should use when sending KMS activation responses to KMS client applications.
You can pass a valid KMS PID or a RandomKMSPID string to generate a random string that matches the KMS PID format.

KMS Server Hardware ID to Use (Global Default): Allows you to set which KMS server hardware hash (added in KMS V6) should be used by this service when sending KMS activation responses to KMS client applications.
You must pass a 16 character string containing only valid hexadecimal characters (0-9, AF).

KMS Client Activation Interval: Set a timer in minutes for how long non-activated KMS clients will wait before trying to activate on the KMS server.

KMS Client Refresh Interval: Sets a timer in minutes for how long already activated KMS clients will wait before attempting to reactivate on the KMS server.

Force Open KMS Port by Terminating Processes: Terminate all processes using the KMS port so that you can start the KMS Server Service on that port.

KMS server service advanced settings window:
Product Type: Allows you to select a Microsoft product (identified by application ID) to which the following KMS PID will apply.

Product Application ID: The application ID that the KMS server service will look for when overriding the KMS PID. It will be set in the registry.

Product KMS PID: Set the KMS PID to be used for any KMS client with the Application ID specified in "Product Application ID".
It overrides "KMS PID to use (global default)". This is the best option if you have a specific KMS PID to use.
This only applies to a KMS client with a matching application ID, i.e. setting the KMS PID here for Microsoft Windows only will not affect Microsoft Office.

Product KMS HWID: Set the KMS HWID to be used for any KMS client with the Application ID specified in "Product Application ID".
It overrides the "Use KMS server hardware ID (global default)" setting. This is the best option if you have a specific KMS HWID to use.
This only applies to a KMS client with a matching application ID, i.e. setting the KMS PID here for Microsoft Windows only will not affect Microsoft Office.

License Display tab:
Show CMID: Shows your KMS Client Machine ID. You won't have it unless you're using KMS and haven't requested activation.

Show Unlicensed: Shows ALL possible product keys that you can install, not just the ones you have already installed. Showing it helps with troubleshooting.

LocalHost Bypass Tab: LocalHost Bypass
IP Address: A workaround is required for KMS clients that cannot activate on LocalHost. This is the IP address that will be spoofed by the bypass method.

LocalHost bypass subnet mask: A bypass method is required for KMS clients that cannot activate on LocalHost. This is the subnet mask that will be forged by the Bypass method.

Use DLL Injection: Inject a DLL into licensing components that redirects KMS requests to LocalHost, tricking the licensing into thinking the source is a spoofed IP address.

Use TAP adapter: Use the network adapter and listener to capture packets and reverse-translate the source and destination IP address and send it back to the KMS client.

Use WinDivert Client: Emulates a TCP/IP client to capture packets and reverse source and destination IP addresses and send back to the KMS client.

Paths tab:
AutoKMS: Select where AutoKMS will be installed.
AutoRearm: Choose where AutoRearm will be installed.
KMS Server Service: Select where the KMS Server Service will be installed.
License Backups: Select where license backups will be stored.

Version changes:
-Updated KMS emulator to generate ePID with accurate CSVLK date-
Updated keys and key
validator -Removed support for Office 2021 Preview

Interface language: English

System requirements:
Microsoft .NET Framework 4.0-4.8 (Not 3.5)
Microsoft Office 2010 or Later for Office Toolkit Support
Windows Vista or Later for Windows Toolkit Support