Skip to content

Security

chaython edited this page Nov 15, 2026 · 2 revisions

Security and release verification

WMT can change Windows services, drivers, firewall rules, registry values, scheduled tasks, disk layout, and boot configuration. It can also invoke package managers, provider tools, and third-party scripts. Treat it as a powerful administrative tool, not a passive viewer.

This page covers how to obtain and verify a release, what the main risk areas are, and how to operate WMT with least privilege.

Trust boundaries

Component Who supplies it Trust consideration
WindowsMaintenanceTool.exe or WMT-GUI.ps1 WMT project Verify the download and the source commit
Windows components (DISM, SFC, CHKDSK, netsh, reg, compact, Task Scheduler) Microsoft WMT passes commands and options; review destructive actions
Package managers (winget, Chocolatey, Scoop, npm, pip, Cargo, RubyGems, Composer, .NET SDK) Their projects They contact their own registries and run installers with your permissions
Game providers (Steam, Legendary/Epic, GOGDL/GOG) Their projects Sign-in tokens are stored locally and sent to those services
Community cleaner rules (winapp2.ini, winapp3.ini, CleanerML) Community sources Rules can target files you need; preview before cleaning
MAS activation script get.activated.win Not controlled by WMT; runs with elevated privileges
Custom update commands You or a third party Run with your permissions; review before saving or running

WMT is a wrapper. A vulnerability or malicious package in an external provider is not automatically a WMT vulnerability, but it can still affect your system.

Download safely

  • Download releases only from the official GitHub Releases page.
  • Do not use unofficial mirrors, re-uploaded EXEs, or files attached to issue comments.
  • Download the EXE and its verification files from the same release.
  • Treat the rolling release as mutable: the same URL can point to different bytes after a later build.
  • Do not disable antivirus, SmartScreen, or Windows security policy solely because WMT is open source.
  • If you build from source, build from a commit you reviewed and keep the toolchain (PS2EXE, PowerShell) from a trusted source.

Verify the SHA-256 checksum

Download these two files into the same folder:

  • WindowsMaintenanceTool.exe
  • WindowsMaintenanceTool.exe.sha256

Then run:

$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 "SHA-256 mismatch. Do not run this file."
}

"SHA-256 matches."

A matching checksum proves that the EXE matches the checksum text you downloaded. It does not prove who published either file. An attacker who can replace both files can make them agree. Use the attestation check for build provenance.

Verify GitHub/Sigstore provenance

Newer releases built by the project's release workflow include a .sigstore.json bundle. Older releases may not.

  1. Install the GitHub CLI.
  2. Download the EXE and WindowsMaintenanceTool.exe.sigstore.json from the same release.
  3. From that folder, run:
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

To pin verification to a specific source commit, add:

--source-digest <commit-sha>

The command should report a verified attestation. If it reports a mismatch, cannot verify the signer workflow, or the bundle is missing, do not treat the file as verified. Confirm that you used the correct files and release, then ask for help before running the EXE.

The release workflow also verifies the attestation before publication and fails closed if the artifact hash, workflow, or source commit does not match.

What an attestation does and does not mean

An attestation provides provenance and integrity evidence for an artifact produced by a particular workflow. It binds the file digest to a workflow identity and source commit.

It is not:

  • An Authenticode signature
  • A Windows publisher certificate
  • A guarantee that the code is free of bugs or malicious behavior
  • A code review of every change
  • A promise that antivirus products will not flag the file

SmartScreen will not treat the EXE as signed by a trusted publisher. Verify the source and the download, and review security warnings rather than bypassing them automatically.

Check what you are running

For a 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*='

Compare the result with the release tag and release notes. A file with the right name but the wrong version is not the release you intended to run.

High-risk operations

Review these before using them. None are required for normal maintenance.

Area Risk
Tweaks that disable UAC, SmartScreen, Windows Update, or Windows Script Host Lowers protection and can break installers or login scripts
Test Mode On Disables driver-signing enforcement and shows a desktop watermark
Enable PS Execution Changes PowerShell execution policy; unrestricted execution weakens a script safeguard
Registry Cleaner Deletes registry keys after backup; a bad rule or user selection can break software
Remove Ghosts, Clean Old, driver deletion Can remove a driver a device still needs
Firewall Defaults / Delete All Removes custom firewall rules; can expose services or block applications
Full Repair in Network and DNS Resets Winsock and TCP/IP; can disconnect the session and affect VPN software
Disable Protection in Restore Manager Deletes all existing restore points
CHKDSK /f /r Can take hours and may schedule a reboot-time check
Compact Compression Changes NTFS compression on files; can affect performance and compatibility
MAS Activation Downloads and runs an external script; may violate licensing terms
Custom update commands and headless installs Run commands and installers with your permissions
System Report, driver exports, logs Contain hardware, network, and account identifiers
Context Menu builder Creates a command that runs when a user clicks the menu entry

Use one change at a time, keep a restore point, and export/back up the affected configuration first.

Least privilege and safe operation

  • Run WMT only on a machine you administer or are authorized to maintain.
  • Approve UAC only for the action you intended. Do not leave an elevated WMT session unattended.
  • Do not run WMT from a network share or a folder other users can modify. A writable script or data folder is a code-execution path.
  • Keep the data folder protected. It can contain registry backups, hosts backups, logs, library caches, and provider credentials.
  • Do not paste custom commands from untrusted sources into the update-command or context-menu fields.
  • Use a standard user account for everyday work and a separate administrator account for maintenance where possible.
  • Test destructive features on a VM snapshot or a disposable PC before using them on production hardware.
  • Keep Windows, firmware, and security software updated independently of WMT.

Network access and privacy

WMT does not operate maintainer telemetry servers. Network traffic occurs when a feature needs an external service, for example:

  • GitHub release and metadata requests
  • Windows Update and Microsoft Store
  • Package-manager registries and provider APIs
  • Steam, Epic/Legendary, and GOG/GOGDL services
  • Community cleaner rule downloads
  • get.activated.win when MAS Activation is explicitly run

Requests are subject to each service's privacy policy and terms. Offline features continue to work without internet access. See Privacy for local data and provider details.

Third-party tools and package managers

WMT can install and update software through external tools. Those tools may:

  • Run installers with administrator rights
  • Add services, drivers, scheduled tasks, or startup entries
  • Contact multiple domains
  • Change file associations or shell integration
  • Require a license agreement or account

Review the package, publisher, and source before installing. WMT's provider logs record installer output, but they do not audit the installer's behavior.

Antivirus and SmartScreen detections

PowerShell-based administrative tools and unsigned EXEs are sometimes flagged heuristically.

  1. Verify the release checksum and attestation.
  2. Confirm the file came from the official release.
  3. If the detection persists, submit the file to the vendor as a suspected false positive and follow the vendor's guidance.
  4. Do not restore or allow a quarantined file until you have verified its origin.

The project README lists vendor submission links. A vendor detection is not proof of malice, and an open-source license is not proof of safety. Investigate both directions.

Protect local data

  • data\settings.json can contain provider selections, custom commands, paths, and ignore lists.
  • data\RegistryBackups contains registry exports that may include sensitive keys.
  • data\package-install-logs contains installer output and paths.
  • data\gogdl\auth.json and Legendary's user.json can grant account access.
  • System reports and driver exports contain computer names, usernames, IP and MAC addresses, and device IDs.

Restrict access to the WMT folder, redact files before sharing, and delete old backups and logs you no longer need. Removing files does not securely erase them on SSDs; use an appropriate sanitization method if the data is sensitive.

Reporting a security issue

Do not publish exploit details, credentials, or unredacted logs in a public issue.

  1. Check whether the repository's Security tab offers private vulnerability reporting and use it if available.
  2. If it does not, open a minimal public issue asking for a private contact channel. Do not include reproduction details that could be abused.
  3. Include the affected version, Windows build, impact, and a minimal reproduction once a private channel is established.
  4. For a vulnerability in a third-party provider or package, report it to that project as well.

Related pages

Clone this wiki locally