SysManager 1.136.163 አውርድ

[1.136.163] - 2026-11-10
When two installed apps share a name, the Uninstaller runs each one's own uninstaller, and what an uninstall left
behind no longer includes a folder another installed app lives in.
Fixed
- The Uninstaller matched the apps it lists to Windows' uninstall entries by name alone, the first app of a name
taking the first entry of that name. Of two programs with one name, a 32-bit and a 64-bit build, or a copy for one
user beside a copy for everyone, one ran the other's uninstaller and stayed installed, and the other had no
uninstall command at all. An app winget found only in the registry carries an id that names its own entry, and now
takes that entry; any other app is matched by name and then by version, and takes no command and no folder from
entries of its name that still differ.
- A Windows Installer command that opens a program's setup (/I) was turned into one that removes it (/X) only
when written as a bare MsiExec.exe. The same command quoted, or with MsiExec's full path, was refused as not a
plain removal. The removal switch now follows the program that runs, however the command is written.
- The search for what an uninstall left behind keeps a folder off the list when another installed app lives in it
or around it, and it worked out where that app lives through the check the Uninstaller applies before it runs a
command. A command it would not run, with an & outside quotes say, read as "lives nowhere", so a folder holding
that app could be offered as the uninstalled app's install folder, ticked. The search now reads where the
uninstaller is without that check, and also keeps a folder off the list when another app's uninstall command names
it anywhere, which covers the DLL a rundll32 command loads and a command no rule can split.
Verify the download
Get-FileHash .\SysManager-v1.136.163.exe -Algorithm SHA256
Expected SHA256: E2CF8B518027382B129CADD0D4B64825346656473A3AD8623831EB19FDC6E80E
This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use it. Full
privacy policy.
Verify where this binary came from
This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:
gh attestation verify .\SysManager-v1.136.163.exe --repo laurentiu021/SystemManager
That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.136.163.sbom.json, a CycloneDX inventory of
every dependency resolved for this build, and THIRD-PARTY-NOTICES.txt, the
licenses and notices of the open-source components the exe carries, which About
also opens from the exe itself.