Microsoft Toolkit

2.7.3
Download
4.9/5 Votes: 34
Size
14 MB
Version
2.7.3
Requirements
Windows x32 / x64
Report this app

Description

Microsoft Toolkit Overview:

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 Features:

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 the license.

The program also has the following features:

  1. If activation fails in one method, it will automatically correct the error and reactivate using another method.
  2. Display detailed information about the operating system or Office – which key is activated, when the license expires, what version is installed.
  3. Converting Retail to Volume license.
  4. A backup copy of the existing license, which after reinstallation will make it possible to quickly restore activation.
  5. Installing and configuring a KMS server. You can configure the server automatically or manually.
  6. Automatic reactivation of Microsoft products after the key expires.

The program is suitable for activating Windows starting from Vista. Microsoft Office activation is available for versions 2003 and newer. To run it, Microsoft NET Fraemwork 4.0 update package must be installed on your computer. For Windows 10 this is not a problem since the package is built in automatically.

The following advantages of Microsoft Toolkit can be highlighted:

  1. Unlike other programs for installing a license, Microsoft Toolkit is absolutely safe and displays all actions performed on the command line.
  2. Works with both 32-bit and 64-bit versions of Microsoft products.
  3. The simplicity of the interface allows even an inexperienced user to understand the activator.
  4. All actions are performed automatically.

Activators Inside:

  • EZ-Activator: This is a simple setup to activate KMS. 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 try possible errors in case of activation failure, and can cancel all changes in case of complete failure.
    It automatically installs all KMS Keys for your system, attempts activation only for the KMS license, and if successful, installs AutoKMS automatically.
  • AutoKMS: AutoKMS Scheduled task that will automatically renew KMS activation for 180 days. Unlike other KMS activators, AutoKMS does not work 24/7 or only at the last minute with the hope that it will not fail, and does not leave any traces other than the scheduled tasks itself, the log and the executable file. It only attempts to activate KMS licenses (which saves a lot of time if you have non-KMS licenses such as MAK or retail active). It will run at startup and then every 24 hours and attempt to activate a certain number of times (the task schedule cannot be changed). The Install/Uninstall buttons are used to install or uninstall AutoKMS.
  • AutoKMS custom task: Replace the default AutoKMS Scheduled tasks with a custom one that will not be reset. You can configure triggers the way you want in 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 attempting to activate KMS. If you don’t have a real KMS server or a network host running an emulator or KMS server, you need to set the value to 127.0.0.2. The port used will be the one specified in the numeric field. KMSEmulator will use this port, but it must be open on your computer, otherwise 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 KMS extended PID should be used by KMSEmulator when attempting to activate KMS.
Changing the PID can help fix persistent KMS activation failures or KMS failing Genuine Validation, but in most cases you’ll 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 matching 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 unblocked 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 attempting to activate KMS.
Changing the Hardware ID can help fix situations where the 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 has not passed Genuine Validation, then an unlocked KMS Hardware ID will be required for this setup.

Activate using KMS emulator: Uses the KMS emulator to perform KMS activation. If you don’t 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 the KMS port so you can run the 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) this service should use 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 attempting activation 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 you can start the KMS Server Service on that port.

KMS Server Service Advanced Settings window:
Product Type: Allows you to select the 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 installed 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 the KMS client with the corresponding 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 that will be used for any KMS client with the Application ID specified in “Product Application ID”.
It overrides the “Use hardware KMS server ID (global default)” setting. This is the best option if you have a specific KMS HWID to use.
This only applies to the KMS client with the corresponding 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 are using KMS and have requested activation.

Show Unlicensed: Shows ALL possible product keys you can install, not just the ones you’ve already installed. Showing this helps when troubleshooting.

LocalHost Bypass Tab:
LocalHost Bypass IP Address: For KMS clients that cannot be activated on LocalHost, a bypass method is required. This is the IP address that will be spoofed by the bypass method.

LocalHost Bypass Subnet Mask: For KMS clients that cannot be activated on LocalHost, a bypass method is required. This is the subnet mask that will be spoofed using the Bypass method.

Use DLL Injection: Injecting a DLL into licensing components that redirects KMS requests to LocalHost, deceiving licensing that the source is a fake IP address.

Use TAP Adapter: Use a network adapter and listener to intercept packets and reverse-resolve the source and destination IP addresses and send them back to the KMS client.

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

Paths Tab:
AutoKMS: Select where AutoKMS will be installed.
AutoRearm: Select 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 saved.

File Information:

Program version: 2.7.3
Official website: My Digital Life
Interface language: English
Treatment: not required

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

What's new

-Updated KMS emulator to generate ePID with exact CSVLK date
-Updated keys and key checker
-Removed support for Office 2021 Preview

TAGS

Leave a Reply

Your email address will not be published. Required fields are marked *