Install Endpoint Toolbelt
One MSI package: test it on one device first, then deploy it as a Win32 app with Intune.
Version 1.0.1 of 18 November 2026, as an MSI package on GitHub. License: MIT. View the source code
For Windows 10 22H2 or Windows 11, 64-bit, enrolled in Intune. IT installs it; users need no administrator rights.
- Test on one device with msiexec
- Deploy as a Win32 app with Intune
- Pass settings at installation or through the registry
A manual installation with msiexec works too, for a test or without Intune.
What you need
- A device with Windows 10 22H2 or Windows 11, 64-bit, enrolled in Microsoft Intune.
- The MSI package
EndpointToolbelt-<version>-x64.msifrom the release page on GitHub. - For the deployment with Intune: the Microsoft Win32 Content Prep Tool, and a device with Windows Enterprise, Pro or Education that is joined or registered to Microsoft Entra ID. Since its end of support, Microsoft lists Windows 10 as allowed in Intune, no longer as supported.
1. Test on one device
Install the package with admin rights on a test device:
msiexec /i EndpointToolbelt-<version>-x64.msi /qn
After that the shortcut Endpoint Toolbelt is in the Start menu. The user needs no admin rights to use it. Uninstall with the same MSI package:
msiexec /x EndpointToolbelt-<version>-x64.msi /qn
If you do not have the package at hand, the product code of the version works too: msiexec /x {ProductCode} /qn. Read it on the test device where the version is installed. PSChildName is the product code:
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' |
Where-Object DisplayName -eq 'Endpoint Toolbelt' | Select-Object PSChildName, DisplayVersion
You also need the code in step 3, for the uninstall command and the detection rule.
Does the app not start, or does the installation fail with error 1920? Error 1920 only says that the service did not start. First check whether something blocks it: Microsoft Defender event 1121 in the Microsoft-Windows-Windows Defender/Operational log, or in the System log Service Control Manager event 7000 for Endpoint Toolbelt Service, with “Access is denied”. If you see neither, install again with a log (/l*v <file> on the command line) and read it. If it is event 1121, the guide on ASR rules explains how to allow Endpoint Toolbelt.
2. Package the MSI
Intune expects a Win32 app in the .intunewin format. The Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) converts the MSI package into it. Microsoft offers the tool as a zip file on GitHub. Put the MSI package in a folder of its own, keep the tool outside it and pass the folder, the file and the output folder:
IntuneWinAppUtil -c <folder with the MSI package> -s <folder with the MSI package>\EndpointToolbelt-<version>-x64.msi -o <output folder>
3. Add the app in Intune
- In the Intune admin center, go to Apps > All Apps > Create, choose the platform Windows and then Windows app (Win32).
- Choose the
.intunewinfile as the package. - For the program, choose the installer type Command line and enter:
- Install command:
msiexec /i EndpointToolbelt-<version>-x64.msi /qn - Uninstall command:
msiexec /x {ProductCode} /qn - Install behavior: System
- Install command:
- For the requirements, choose 64-bit under Operating system architecture, and under Minimum operating system the lowest version of Windows you support.
- Configure the detection rules manually and choose the rule type MSI, with the product code of this version under MSI product code. Do not set MSI product version check to Yes: the product code is enough, because each version has a code of its own.
- Leave the return codes as Intune fills them in.
- Assign the app as Required to the groups that should get it.
4. Pass your settings
Endpoint Toolbelt has no management console. What the app may do, you set at installation or through the registry.
At installation you pass a setting on the command line, for example the text and the link of your service desk:
msiexec /i EndpointToolbelt-<version>-x64.msi /qn SUPPORTTEXT="SoulBit Service Desk" SUPPORTURL="https://support.soulbit.example"
With the link, the app shows Contact IT on Home and on “My problem is not listed”. Set both the text and the link: many results send the user to the service desk.
For each setting, the name at installation comes first, then the one in the registry:
- Waiting time between two full IME resets (hours, 1 by default; 0 switches it off):
FULLRESETCOOLDOWNHOURS·FullResetCooldownHours - Waiting time between two Windows Update repairs that changed something (hours, 4 by default; 0 switches it off):
WUREPAIRCOOLDOWNHOURS·WURepairCooldownHours - Maximum number of actions that change the device, per user per hour (1 to 60, 20 by default; cannot be switched off):
USERRATELIMIT·UserRateLimitPerHour - Actions that affect every session, while others are signed in (1 by default, allowed; 0 blocks them):
ALLOWMULTISESSIONRESET·AllowMachineWideOnMultiSession - Text of the service desk (empty by default):
SUPPORTTEXT·SupportText - Link to the service desk (an https address, empty by default):
SUPPORTURL·SupportUrl - Days after Patch Tuesday after which that month’s update is expected (10 by default):
WUDEPLOYMENTDELAYDAYS·WUDeploymentDelayDays - Free space in GB below which the Windows Update repair cleans up first (15 by default):
WUMINFREEGB·WUMinFreeGB - Remove stale servicing packages during that repair (0 by default; 1 allows it):
WUREMOVESTALEPACKAGES·WURemoveStalePackages
You also set the same settings as a registry value under HKLM\SOFTWARE\Policies\EndpointToolbelt, with the second name from the list. A registry value there takes precedence over the value from the installation, and the service applies a change within 30 seconds. There is no ADMX template.
Switching single tools off is possible only there, with the value DisabledTools: a REG_MULTI_SZ with one tool name per line, for example FullReset or RepairWU. The names are in the configuration table of the admin guide.
5. A new version
Each version has a new product code. So add a new version as a new Win32 app and set the previous app under Supersedence, with Uninstall previous version on No: the MSI package upgrades the installation itself. According to Microsoft, an app that replaces another does not get the old app’s assignments by itself. So assign the new app to the same groups: a device that only has the old assignment does not get the new version. Then remove the Required assignment from the old app.
Settings from the installation survive an upgrade. Values you pass again replace them.
Sources from Microsoft
- Uninstall Registry Key, accessed on 17 November 2026
- msiexec, accessed on 17 November 2026
- Add and Assign Win32 Apps to Microsoft Intune, accessed on 16 November 2026
Show 6 more sources
- Prepare a Win32 App to Be Uploaded to Microsoft Intune, accessed on 16 November 2026
- Add Win32 app supersedence, accessed on 16 November 2026
- Operating systems and browsers supported by Microsoft Intune, accessed on 16 November 2026
- Command-Line Options, accessed on 17 November 2026
- Update release cycle for Windows clients, accessed on 16 November 2026
- Registry value types, accessed on 16 November 2026