Repository navigation
Installation
Windows Maintenance Tool (WMT) is distributed as a portable executable. WinGet can install and manage that portable package, but WMT is not a traditional MSI application and has no setup wizard.
| Method | Best for | Notes |
|---|---|---|
| WinGet | Most users | Package-managed portable app, Start menu entry, and wmt command alias |
| Portable release | Users who want to manage the executable themselves | Download and run the EXE; keep it in a stable folder |
| PowerShell script | Contributors and users running from source | Requires Windows PowerShell 5.1 and the project files |
All methods run the same application. The difference is how the files are installed, updated, and removed.
Open PowerShell or Windows Terminal and run:
winget install --id Chaython.WindowsMaintenanceTool --exactIf WinGet asks you to accept source or package agreements, review them and follow the prompt. After installation, open a new terminal and launch WMT with:
wmtYou can also find Windows Maintenance Tool in the Start menu. If the wmt command is not recognized, see Troubleshooting.
Use WinGet to manage the package:
winget upgrade --id Chaython.WindowsMaintenanceTool --exact
winget uninstall --id Chaython.WindowsMaintenanceTool --exactDo not move or manually delete files from the WinGet-managed installation directory. Uninstalling the application and deleting its separate settings or generated data are different operations; review Settings and Data and Privacy before removing user data.
- Open the official latest stable release.
- Download
WindowsMaintenanceTool.exe. For a newer release, also downloadWindowsMaintenanceTool.exe.sha256and, when present,WindowsMaintenanceTool.exe.sigstore.json. - Verify the download as described in Security.
- Save the EXE in a folder you control, such as a dedicated folder under your user profile.
- Run the EXE. If Windows displays a security warning, verify the release before deciding whether to continue.
The portable release does not register an uninstaller. Keep it in a stable location if you enable Start with Windows, scheduled compression, or other behavior that stores a path to the executable. If you move it later, revisit those settings and confirm that scheduled tasks still point to the correct location.
A manually managed copy commonly looks like this:
Windows-Maintenance-Tool\
├─ WindowsMaintenanceTool.exe
└─ data\
├─ settings.json
├─ RegistryBackups\
├─ hosts_backups\
└─ reports and caches...
WMT creates the data folder next to the application or script when it needs to store settings, reports, backups, or caches. Exact contents depend on the features you use. See Settings and Data for the full list.
Only run source code that you obtained from a repository you trust. To clone the official project:
git clone https://github.com/Chaython/Windows-Maintenance-Tool.git
Set-Location .\Windows-Maintenance-ToolLaunch the script directly:
powershell.exe -NoProfile -File .\WMT-GUI.ps1If your PowerShell execution policy blocks the script, first review the source and your organization's policy. If appropriate for your environment, you can bypass the policy for this PowerShell process only:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\WMT-GUI.ps1The repository also contains Start_WMT_GUI.bat. Unlike direct script launch, the batch launcher requests administrator elevation when starting WMT and performs online update checks. Inspect the current launcher contents and its download sources before using it, especially when working from a source checkout.
For build instructions, see the Developer Guide.
- Confirm the title bar shows the expected WMT version.
- Let the application finish its initial background loading. The Tweaks and My Device pages may show a loading overlay while state is collected.
- Open Support & Credits and review the startup, tray, background-job, and update-scan toggles. They are described in Background Jobs and Tray.
- Open Updates > Providers and enable only the package sources you actually use.
- Run an inventory or scan before running any delete, repair, or toggle action.
- Create a restore point if you plan broad system changes and System Protection is available.
Opening the Updates page does not start a scan by itself. Use Refresh All, press F5, or wait for a configured automatic scan.
WMT includes both read-only views and actions that modify protected Windows resources. Many maintenance features need administrator access. Depending on the action and launch method, Windows may show a User Account Control (UAC) prompt, or the action may require WMT to be started elevated.
Approve elevation only when you intended to run that action. Declining a prompt can prevent the requested operation from completing; it does not mean you need to elevate every application you run.
Some actions open a separate elevated console window, such as SFC, DISM, Quick Fix, and CHKDSK. Keep that console open until the operation finishes so you can read the result.
WMT writes reports, backups, settings, caches, and other feature data locally. Some output is kept in a data folder next to the script/application; provider caches and optional authentication data may also be kept in the Windows user profile. Exact files depend on the features and providers you use.
- For a manually managed portable copy, keep the EXE in a stable folder and back up any data you want to retain before moving or replacing files.
- For a WinGet installation, let WinGet manage the application directory. Do not rely on its internal path as a permanent location.
- Before removing an old copy, moving the application, or cleaning its data, disable or update any startup entries and scheduled jobs that refer to its old path.
- If Start with Windows stops working after a move, open Support & Credits and toggle the startup control so WMT can validate and repair its saved launch path.
-
WinGet installation:
winget upgrade --id Chaython.WindowsMaintenanceTool --exact. -
Portable copy: close WMT, keep a backup of the old EXE and
datafolder, download the new release, and replace the EXE. Reopen WMT and confirm the version and your settings. -
Source checkout: pull the repository changes, review them, and relaunch
WMT-GUI.ps1.
Do not update a running portable copy in place. Close the main window and exit from the tray icon first; otherwise the executable may be locked or a background process may continue using the old files.
- Close WMT and exit the tray icon.
- For a WinGet installation, run
winget uninstall --id Chaython.WindowsMaintenanceTool --exact. - For a portable copy, delete the EXE and its folder after backing up anything you want to keep.
- Disable or remove any WMT-created startup entry, scheduled task, or context-menu entry that remains.
- Remove WMT-specific data folders only after identifying them positively. Do not delete broad
%APPDATA%or%LOCALAPPDATA%directories.
See Settings and Data for paths and safe cleanup guidance.