Microsoft Toolkit

About Microsoft Toolkit

This is one of the older tools in the category and it survives because it is more than a button. It splits into separate management tabs for the system and for the office suites, and each one exposes the underlying operations individually rather than hiding them behind a single action, which is what a technician needs when a machine does not behave the way the simple tools expect.

The information tab is the reason to open it even when nothing needs changing. It reports the installed edition, the current state, the configuration in use and the details of what is registered, all in a text pane that can be copied out. Diagnosing why a machine is in an odd state usually starts here rather than with running anything.

The customise setup builder is the part most people never find. It takes an office installation source and produces a configured one, with the applications that are not wanted removed before installation rather than uninstalled afterwards, and the setup options set in advance. On a fleet of machines that turns a repetitive manual install into an unattended one.

Everything it does is written to a log pane in the window, which can be saved to a file. That transparency is the practical argument for it over newer tools: when something fails, the log names the step and the error, so the next move is informed. It is portable, runs from a folder or a stick, and leaves nothing installed behind it.

What is included in this build

• Separate management tabs for the system and the office suites
• Individual operations exposed rather than hidden behind one action
• Information tab reporting edition, state and registered configuration
• Customise setup builder producing a configured office installation source
• Unattended installation options set in advance of deployment
• Full operation log in the window, saveable to a file
• Portable operation from a folder or a technician stick
• Coverage across desktop and server editions and multiple office generations

Changed in version 2.7.4

• Support extended to additional office generations
• Improved detection reporting in the information tab
• Setup builder handling of larger installation sources made more reliable
• Clearer log output on failed operations
• Reduced package size

Installation walkthrough

These steps assume a clean machine. If a previous release of the same application is present, deal with that first, since an overlapping install is the most common cause of a setup that stops halfway.

1. Exclude the folder in the protection software before extracting, since tools of this type are flagged on heuristics.
2. Extract the package rather than running it from inside the archive.
3. Run the executable as administrator.
4. Open the information tab first and read the current state before running any operation.
5. Save the log pane to a file if a machine needs to be handed to someone else afterwards.

System requirements and file details

Frequently asked about this title