SysManager 1.136.159 አውርድ

[1.136.159] - 2026-11-09
SysManager deletes the native libraries its older versions left in your temp folder, about 26 MB for each version,
which stayed there for good.
Fixed
- The .NET runtime unpacks the native libraries a single-file app needs into %TEMP%\.net, under a folder named
after the exe and a folder for each build inside it, and never deletes them, and SysManager's temp clean-ups leave
that folder alone on purpose. So every version you ever ran kept about 26 MB there: a SysManager-v<version>
folder for each release run as downloaded from GitHub, and one more build inside SysManager for each winget
upgrade. Once its window is up, SysManager now deletes the folders of older versions, and the other builds beside
its own, when nothing in them has been written for a week. It leaves a folder that is or holds a link, one that
holds files but not WPF's renderer, which every build of SysManager unpacks, and one whose renderer a running copy
has loaded: Windows will not delete a loaded library, and that file is tried first. It does this only when it runs
without administrator rights: the folder is yours, and any program running as you can write to it, so a delete
there as an administrator would let such a program choose what an administrator process deletes. (#2858)
- SysManager took the folder its exe runs from for the folder its libraries were unpacked into. Measured on a build
published the way the release is, the runtime gives the exe's folder as the app's base folder, and names the
unpacked one only in its list of folders to load native libraries from. Nothing the app did changed, since the
temp clean-ups skip the whole unpacking folder and still skip the exe's own; the clean-up above needed the real
one.
- Tests pin each folder the clean-up deletes and each one it leaves, with every file checked: an older release, a
build beside its own, a folder emptied of its files, the week's boundary, the same or a newer version, other apps'
folders, a file written this week, a renderer held open, a folder without one, links in and above the folder, and
an elevated run.
Verify the download
Get-FileHash .\SysManager-v1.136.159.exe -Algorithm SHA256
Expected SHA256: 12A652E153306FBC9C92CB09F01593E325C0B94E1A4E9BDEE14A5E834326B916
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.159.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.159.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.