SysManager 1.136.76 yüklə

[1.136.76] - 2026-11-02
File Shredder leaves a file it does not shred exactly as it found it, measures a folder without freezing, and keeps the method you confirmed.
Fixed
- File Shredder cleared a file's read-only flag before it refused a hard-linked file or honoured a cancel that came
before the first byte, so a file it left "untouched" had lost the flag, and a refused hard link lost it under every
name the file has. The flag is now set again on any file the shred leaves as it found it. This was there since
1.52.76.
- Add Folder measured the folder on the thread that draws the window, so a large one, a photo archive or a USB drive,
froze SysManager for the whole walk, and one unreadable folder anywhere inside turned the whole folder away. It is
measured in the background now, with the walk the shred itself takes, which passes over a folder it cannot read.
This was there since the tab was added in 1.4.0.
- The Method box stayed on during a run and every item read it again, so switching Thorough to Quick part-way shredded
the rest with one pass instead of the seven you confirmed, and the activity log recorded the whole run as a one-pass
overwrite. A run now uses the method you confirmed, and the box is off until it ends. This was there since 1.4.0
too.
Verify the download
Get-FileHash .\SysManager-v1.136.76.exe -Algorithm SHA256
Expected SHA256: B8C72377BE99CE32F76C8E7D2F1D1F9F7871F1EC3195379FCCCA95D156FB5CFB
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.76.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.76.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.