nguyenduy_89
Well-Known Member
Microsoft Toolkit 2.5 Official - phần mềm bẻ khóa windows 1 cách đơn giản nhất
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
2.5 BETA 5
-Added DLL Injection LocalHost Bypass Method
-Create and Delete IP Routes with Win32 API instead of command line
-No longer require SFX EXE files to Remove or Restart TAP Adapter
-Prevented exception when LocalHost Bypass IP in in use when using TAP Adapter Bypass
-Retry up to 10 times if using LocalHost Bypass and you get 0xC004F074 error
-Set DHCP and Static IP addresses on TAP Adapters using WMI instead of command line
-Warning if more than 1 TAP Adapter is installed before Activation
2.5 BETA 4
-Fixed registry exception if installing a new TAP Adapter
-If another TAP adapter is using the LocalHost Bypass IP that adapter will be set to DHCP
-More WinDivert failure logging to distiguish it as the cause of 0xC004F074 activation failure
-TAP Adapter used for activation will be automatically removed, and without VPN disruption
-Updated WinDivert to 1.1.1
-Using 2 variants of TAP Adapter based on current TAP Adapter to avoid VPN conflict
2.5 BETA 3
-Automatically add and remove Windows Firewall permissions
-Updated WinDivert to not need MSVC++ Runtimes
-Using external loader for WinDivert to allow multiple runs in one MTK instance.
2.5 BETA 2
-Added LocalHost Bypass options
-Added WinDivert as a LocalHost Bypass method
-Always use IP Configuration in new LocalHost Bypass Settings
-Autodetect usable TAP Adapter
-Detect TAP Adapters with numbers (#2) in the name
-Enable All Disabled TAP Adapters on Install Check
-Fixed License Backups Browse button
-Restart TAP Adapter if we change IP Address or set MediaStatus
-Set MediaStatus=1 on IP Change or TAP Listener Start
-Verify TAP Adapter IP was set to avoid invalid IP parse exceptions
2.5 BETA 1
-Added functions to get MSDM and Default Product Keys
-Automatically use TAP Adapter if using localhost (IP, localhost string, or Machine Name) on KMS V6.
-Detect OEMM Keys for License Backup and Restore
-Full KMS Activation support for Windows 8.1/Server 2012 R2 and Microsoft Office 2013 using KMSEmulator (requires TAP Adapter).
-Improved Network Drive Check.
-License Backup and Restore will not prompt for Windows Embedded Volume Keys (such as Windows Thin PC).
-Renamed Check/Show Registry to Check/Show System.
Microsoft Toolkit Settings
KMS Options Tab:
KMS Server/Port to Use: Allows you to set what KMS server and port should be used when attempting KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this set to 127.0.0.2. Whatever the numerical box says will be the used port. KMSEmulator will use this port but it must be open on your PC, or the process using it may be terminated.
NOTE: The Office KMS Server/Port is used when activating Office based products and Windows KMS Server/Port when activating Windows based products.
KMS PID to Use: Allows you to set what KMS Extended PID should be used by KMSEmulator when attempting KMS activation.
Changing the PID can help fix persistent KMS activation failure or KMS failing Genuine Validation, but in most cases you want to leave this alone.
You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format.
NOTE: The Office PID is used when activating Office based products and Windows PID when activating Windows based products.
NOTE: You cannot change the KMS PID used for KMS Activation for real KMS Servers. If a KMS Server or KMS PID fails Genuine Validation, this Setting will need to be an unblocked KMS PID.
Activate Using KMS Emulator: Uses KMS Emulator to perform KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this enabled.
Delete 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: Kill any processes using the KMS Port so you can run KMS Emulator on that port.
NOTE: This is only performed if KMS Activation fails, allowing KMS Emulator to silently fail and a KMS Server Virtual Machine to be used.
KMS Server Service Tab:
KMS Port to Use: Allows you to set what 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 what KMS Extended PID should be used by this service when sending KMS activation responses to KMS Client applications.
You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format.
KMS Client Activation Interval: Set the timer in minutes to how long unactivated KMS Clients will wait before trying to activate against the KMS Server.
KMS Client Renewal Interval: Set the timer in minutes to how long already activated KMS Clients will wait before trying to reactivate against the KMS Server.
Force Open KMS Port by Terminating Processes: Kill any processes using the KMS Port so you can run KMS Server Service on that port.
KMS Server Service More Settings Window:
Product Type: Allows you to choose the Microsoft Product (determined by Application ID), that the following KMS PID will apply to.
Product Application ID: The Application ID that the KMS Server Service will look for when overriding the KMS PID. This 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 the "KMS PID to Use (Global Default KMS PID)". This is best if you have a specific KMS PID to use.
This only applies to the KMS Client with the matching Application ID, as in 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 one if you aren't using KMS and haven't requested activation.
Show Unlicensed: Shows ALL possible product keys you can install, not just the ones you have installed. Showing this helps in troubleshooting.
Paths Tab:
AutoKMS: Choose where AutoKMS will be installed.
AutoRearm: Choose where AutoRearm will be installed.
KMS Server Service: Choose where KMS Server Service will be installed.
License Backups: Choose where License Backups will be saved.
Mã:
[center] [url=http://www.fshare.vn/file/T7FAN4FRBT]Fshare - Dich vu chia se, luu tru du lieu mien phi tot nhat[/url] [/center]
