Skip to content

Updates and Releases

chaython edited this page Nov 15, 2026 · 2 revisions

Updates and release channels

WMT publishes a versioned stable release and a moving rolling preview. Choose a channel based on whether you value predictable versions or want to test the newest successful build.

Latest Release Downloads dialog

The Release Downloads dialog reports download counts for the latest release. The numbers are informational and may lag behind the actual release page.

Channels at a glance

Channel Tag How it changes Intended use Package-manager distribution
Stable v<version>, for example v6.9 New immutable release per version Regular use Eligible for optional WinGet, Chocolatey, and Scoop submission
Rolling preview rolling Assets replaced after successful builds from Main Testing current development Not submitted to WinGet, Chocolatey, or Scoop

Stable versions are immutable. Once v6.9 is published, the workflow refuses to replace its tag or assets. A new build requires a higher $AppVersion and a new tag.

The rolling release is mutable by design. The tag and URL stay the same while its contents change, so it is not a fixed version. Record the source commit and SHA-256 if you need to identify an exact build.

How updates reach you

Install method How to update Notes
Portable EXE Download the new EXE from the official release and replace the old one Close WMT, including the tray icon, first
WinGet winget upgrade --id Chaython.WindowsMaintenanceTool --exact The manifest can lag behind the GitHub release
Chocolatey choco upgrade windows-maintenance-tool Availability depends on the optional release job and package moderation
Scoop scoop update windows-maintenance-tool Requires the Scoop Extras manifest to be accepted and updated
Source checkout git pull or download the new WMT-GUI.ps1 Keep the batch launcher and data folder consistent
Built-in self-update Accept the Update Available prompt See the caveats below before relying on it

Package-manager publication is optional. A new GitHub release does not guarantee that every package manager has the same version at the same time.

Built-in self-update

WMT runs a background self-update check at startup. If the remote version is newer than $AppVersion, it offers to download and install the update.

For a compiled EXE, it:

  1. Queries the latest release metadata.
  2. Selects the first .exe asset.
  3. Looks for a matching .sha256 checksum asset.
  4. Prompts before downloading.
  5. Rejects a file smaller than 1 MB or missing the MZ executable header.
  6. Verifies the SHA-256 when a checksum is available.
  7. Stages the file, backs up the current EXE as WindowsMaintenanceTool.exe.backup, replaces the EXE after WMT exits, and restarts it.

For a source script, it:

  1. Downloads the raw script.
  2. Parses $AppVersion and compares versions.
  3. Backs up the current script to data\WMT-GUI.ps1.bak.
  4. Writes the new script and verifies its SHA-256 against the downloaded bytes.
  5. Restores the backup if verification fails, then restarts WMT.

If no checksum asset is published, the EXE updater logs the downloaded hash but proceeds without a comparison. The script updater falls back to a size check when byte-exact verification is unavailable.

Repository endpoint caveat. In the 6.9 source, the built-in self-update checker, the Release Downloads dialog, and the update-failure fallback link use the upstream ios12checker/Windows-Maintenance-Tool repository, while this fork's release workflow publishes to Chaython/Windows-Maintenance-Tool. The checker may therefore not offer this fork's newest build, and Release Downloads may show upstream statistics. For this fork, prefer the official Chaython release page and verify the assets there. Check the endpoint in your build before depending on in-app updates.

Because the self-updater replaces the running EXE or script, treat it as a privileged code-update path. If you need a specific, reproducible version, update manually from the release page and verify the checksum and attestation.

Stable releases

Download from GitHub Releases - latest stable. Stable releases use versioned tags and are the channel intended for everyday use.

The release workflow can optionally submit a stable release to WinGet and Chocolatey. Scoop submission requires an approved ScoopInstaller/Extras issue, a SCOOP_TOKEN, and explicit confirmation that a maintainer approved the issue. These jobs run only for a manual, non-prerelease release when the corresponding input is enabled.

If installed through WinGet:

winget upgrade --id Chaython.WindowsMaintenanceTool --exact
winget uninstall --id Chaython.WindowsMaintenanceTool --exact

For a manually downloaded EXE:

  1. Close WMT, including the tray icon.
  2. Download the new EXE from the official release page.
  3. Optionally verify the checksum and attestation.
  4. Replace the old EXE, or keep it as a backup until the new version starts successfully.
  5. Keep the data folder with the new EXE so settings and caches are preserved.

Do not run two WMT versions against the same data folder at the same time.

Rolling preview

The rolling prerelease is built automatically from the Main branch after a successful workflow run. Its tag and URL stay the same while its assets are replaced by the newest successful build.

Use the rolling preview to test current changes, not when you need the stability of a versioned release. It is not submitted to WinGet, Chocolatey, or Scoop. Download it only from the official rolling release page and verify its assets.

Because the rolling release is mutable, a checksum you recorded earlier may no longer match the current asset. Re-download the checksum and bundle from the same page at the same time, or pin verification to a specific source commit.

Release assets and verification

Newer releases produced by the current build workflow include:

Asset Purpose
WindowsMaintenanceTool.exe Portable application
WindowsMaintenanceTool.exe.sha256 SHA-256 checksum
WindowsMaintenanceTool.exe.sigstore.json GitHub/Sigstore attestation bundle

Download the EXE and its verification files from the same release. Older releases created before attestations were introduced may not have a bundle.

Quick checksum check:

$actual = (Get-FileHash .\WindowsMaintenanceTool.exe -Algorithm SHA256).Hash.ToLowerInvariant()
$expected = ((Get-Content .\WindowsMaintenanceTool.exe.sha256 -Raw).Trim() -split '\s+')[0].ToLowerInvariant()
if ($actual -ne $expected) { throw "Checksum mismatch. Do not run this file." }

Attestation check:

gh attestation verify .\WindowsMaintenanceTool.exe `
  --repo Chaython/Windows-Maintenance-Tool `
  --bundle .\WindowsMaintenanceTool.exe.sigstore.json `
  --signer-workflow Chaython/Windows-Maintenance-Tool/.github/workflows/release-ps2exe.yml

The EXE is not Authenticode-signed. An attestation proves build provenance and integrity, not publisher identity in the Windows certificate sense. See Security for the full explanation and limitations.

Check the installed version

For the portable EXE:

(Get-Item .\WindowsMaintenanceTool.exe).VersionInfo |
  Select-Object FileVersion, ProductVersion, CompanyName, ProductName

For a source checkout:

Select-String -Path .\WMT-GUI.ps1 -Pattern '^\$AppVersion\s*='

The application title also shows the version, for example Windows Maintenance Tool v6.9.

When asking for help, include the version and state whether you installed from WinGet, downloaded a stable or rolling EXE, used the built-in updater, or ran from source.

Version numbering

  • $AppVersion in WMT-GUI.ps1 is the single source of truth.
  • The release tag is v plus that version, for example v6.9.
  • The EXE file version is padded to four parts, for example 6.9.0.0.
  • Stable versions increase over time; the workflow rejects a tag or release that already exists.
  • The rolling release does not use a new version tag. Its notes record the source commit and checksum.

Update safely

  1. Read the release notes and confirm the version and channel.
  2. Close WMT, including the tray icon. If WMT is hidden, use Exit WMT from the tray menu.
  3. Back up data\settings.json and any backups, reports, or provider credentials you need.
  4. Verify the new EXE before running it.
  5. Replace the old EXE or install through the package manager.
  6. Start WMT and confirm the version, settings, and providers.
  7. Keep the old EXE or WindowsMaintenanceTool.exe.backup until the new version works.
  8. If Start with Windows is enabled and you moved the EXE, toggle it off and on so the scheduled task points to the new path.

Do not copy only selected files from a new release over an old installation. Keep the EXE/script, launcher, and data folder consistent.

Roll back or downgrade

There is no built-in downgrade command. To return to an earlier version:

  1. Close WMT.
  2. Restore the previous EXE, or download the older release from GitHub.
  3. Restore the matching data backup if the newer version changed settings or caches.
  4. Start WMT and verify the version.

Older releases may not understand newer settings keys; WMT generally fills missing defaults, but a settings backup from the older version is safer. A downgrade can also lose provider or library state. Do not downgrade to bypass a security fix without understanding the risk.

Release cadence

  • Pushes to Main can publish a new rolling build after validation and a successful build.
  • Stable releases are published manually from Main with a bumped $AppVersion.
  • The release workflow serializes publication so two runs cannot overwrite each other.
  • A stale rolling run checks the Main HEAD before publishing and refuses to replace the rolling release with an outdated build.

Troubleshooting an update

Problem Check
Checksum mismatch Re-download the EXE and .sha256 from the same release; do not run the file if it still mismatches
Attestation verification fails Confirm the repository, workflow path, bundle, and source digest; use the exact release assets
gh is not recognized Install the GitHub CLI and reopen the terminal
WinGet says the package is current The manifest may lag; check the GitHub release and winget source update
Chocolatey or Scoop does not have the version The optional publication job may not have run or the package may still be under review
The built-in updater offers an unexpected version Check the repository endpoint caveat above; update manually from the Chaython release page
WMT will not start after an update Restore the .backup EXE or the previous script from data\WMT-GUI.ps1.bak; check last-crash.txt
Settings look different after an update Restore settings.json.bak or your own backup; review new defaults
The startup task launches the old path Toggle Start with Windows off and on after moving the EXE

For startup failures, missing data, and provider errors, see Troubleshooting.

Related pages

Clone this wiki locally