Jump to content
nsane.forums

Recommended Posts

november_ra1n

Microsoft Toolkit 2.5

ncs7.png

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:

v. 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
Full Changelog >>>> Or Full Changelog >>>>

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.

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
Name: Microsoft Toolkit,exeSize: 36.6 MBCRC32: CA90B9D2MD5: 7F8A3114659A0ADAA572F0E9E4255BFCSHA-1: 5671C239B85EC01C33C4EB155CAA0DFA6C57E509

Download Links

http://www.mirrorcreator.com/files/QXDRXJJN/MTKV25_0.zip_links

Or

magnet:?xt=urn:btih:1422A50A2BF77CD3490620F7D15AC974DE6EF7AF&dn=Microsoft%20Toolkit%202.5%20Official%20Torrent&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce

Developer: CODYQX4

Edited by november_ra1n

Share this post


Link to post
Share on other sites
PistalPete

Thanks November_ra1n

Another link (thanks to Paiva)

November_rai1n I have tried for the last 10 minutes to sharecode this, but for whatever reason, when I type the link into the sharecode box and then hit ok, nothing happens. It won't sharecode it. sorry, but I am not sure why this is happening.

Download
Site: http://www.solidfiles.com
Sharecode[?]: /d/d20ca40637/

Edited by 7h3Pr3d47oR
Sharecode fixed.

Share this post


Link to post
Share on other sites
tezza

Injection LocalHost Bypass Method working no problem, thanks CODY :win:

(Manually go into settings and choose it, as the default is still set to TAP Adapter.)

Edited by tezza

Share this post


Link to post
Share on other sites
november_ra1n

Q: "Added DLL Injection LocalHost Bypass Method" will be use by ezactivator? And it is automatic about renewal?

CODYQX4:

You have to manually go into settings and choose it, as the default is still set to TAP Adapter.

But yes, if that setting is enabled, EZ-Activator will use it, as will AutoKMS and the normal "Activate" button.

Edited by november_ra1n

Share this post


Link to post
Share on other sites
RobrPatty

Q: "Added DLL Injection LocalHost Bypass Method" will be use by ezactivator? And it is automatic about renewal?

CODYQX4:

You have to manually go into settings and choose it, as the default is still set to TAP Adapter.

But yes, if that setting is enabled, EZ-Activator will use it, as will AutoKMS and the normal "Activate" button.

Thanks NR and tezza for this info. Nice work by CODYQX4.

Share this post


Link to post
Share on other sites
uffbros

How do you go into manual settings and select it? How do I know if I need Tap or Dll injection one? Thanks.

Share this post


Link to post
Share on other sites
oliverjia

dll injection appears to be less intrusive to the system, as it only needs to modify/inject into a running process in RAM on the fly. With TAP driver, you have to actually install a driver into your system before you can activate.

so I'd say try dll injection first, if it's not working for you, then try the TAP method.

How do you go into manual settings and select it? How do I know if I need Tap or Dll injection one? Thanks.

Share this post


Link to post
Share on other sites
unknownasphyxiated

Dll Injection Method only for KMS v6

other than that, you still need to use TAP/WinDivert

wait another week or more or maybe less, you will get Dll Injection Method for all protocol

v2.4 is coming

Share this post


Link to post
Share on other sites
tezza

Dll Injection Method only for KMS v6

other than that, you still need to use TAP/WinDivert

wait another week or more or maybe less, you will get Dll Injection Method for all protocol

v2.4 is coming

Or maybe v2.6 :-)

2.4 :D as @unknownasphyxiated said.

it is based on SECO Injector V2.3 by cynecx

The injection dll is supporting all protocols, I just simply added a check in the injector so you can run it only on 8.1 os .

You have to manually inject it, if you want to use it on different oses ( I think, I will also change this in the new update ) ...

Edited by tezza

Share this post


Link to post
Share on other sites
CODYQX4

Dll Injection Method only for KMS v6

other than that, you still need to use TAP/WinDivert

wait another week or more or maybe less, you will get Dll Injection Method for all protocol

v2.4 is coming

Not sure what you mean, as there is nothing that doesn't use KMS V6 that needs either 3 options. They aren't used if not needed.

Share this post


Link to post
Share on other sites
alexxf

Dll Injection Method only for KMS v6

other than that, you still need to use TAP/WinDivert

wait another week or more or maybe less, you will get Dll Injection Method for all protocol

v2.4 is coming

Wrong. KMS v4 or v5 dont need LocalHost Bypass

Share this post


Link to post
Share on other sites
unknownasphyxiated

Not sure what you mean, as there is nothing that doesn't use KMS V6 that needs either 3 options. They aren't used if not needed.

my bad, mixed up with Dll support for Office 2010

Share this post


Link to post
Share on other sites
SNoffel

Hello, first of all thanks for this amazing tool.

i have one question why i cant download the file? i click on the links and nothing happens after redirecting to the download mirrors...

Share this post


Link to post
Share on other sites
november_ra1n

Hello, first of all thanks for this amazing tool.

i have one question why i cant download the file? i click on the links and nothing happens after redirecting to the download mirrors...

How to create and open Sharecode..!

After that select the mirror you want to download then copy and paste the mirror link in your browser.

Share this post


Link to post
Share on other sites
november_ra1n

Thank's,, Hero :showoff:

but, waiting final

This build as stable as it can be according to CODYQX4 he does not have any plan to come out any Final build for a long time therefore ignore beta tag and use this edition as it is Final..

Edited by november_ra1n

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×