ਇਹ ਪੁਰਾਣਾ ਵਰਜ਼ਨ ਹੈ। ਨਵਾਂ ਵਰਜ਼ਨ 1.136.177 ਹੈ। SysManager 1.136.177 · ਰਿਲੀਜ਼:
ਇੰਸਟਾਲਰ ਫ਼ਾਈਲਾਂ 1.136.170
| ਆਰਕੀਟੈਕਚਰ | ਕਿਸਮ | ਕਿਸ ਲਈ | ਫ਼ਾਈਲ ਦਾ ਆਕਾਰ | ਡਾਊਨਲੋਡ | SHA256 |
|---|---|---|---|---|---|
| 64-ਬਿੱਟ | ਪੋਰਟੇਬਲ | — | — | github.com | VirusTotal |
ਲਿੰਕ ਅਤੇ SHA256, Windows Package Manager ਦੇ ਕਮਿਊਨਿਟੀ ਮੈਨੀਫ਼ੈਸਟਾਂ ਤੋਂ ਲਏ ਗਏ ਹਨ। ਫ਼ਾਈਲ ਚਲਾਉਣ ਤੋਂ ਪਹਿਲਾਂ ਉਸ ਦਾ ਹੈਸ਼ ਮਿਲਾ ਕੇ ਦੇਖੋ।
ਰਿਲੀਜ਼ ਨੋਟਸ
[1.136.170] - 2026-11-12
A File Shredder folder shred now says when the folder is still on your computer, and keeps it in the queue, instead
of calling it done.
Fixed
- A folder picked through a link above it, such as a folder under a junction or on a drive letter made with SUBST,
was walked as empty: its files were not touched, the folder was reported shredded, and the queue showed it as
0 bytes. The shred and the queue's size now walk such a folder as they walk any other. It has been that way since
the folder walk started refusing links above the folder in 1.131.4.
- An emptied folder Windows would not remove, such as one made read-only by Properties > Customize, stayed on disk
while the folder was reported shredded and taken off the queue. Such a folder is now removed once it is empty, and
a folder still on disk after its shred stays in the queue as "Partly shredded" or "Failed", with the reason. A
Cancel during the last file's overwrite also stopped the removal of the emptied folders, with nothing said.
- A file whose contents were overwritten, but whose name Windows would not remove, was listed among the files "left
in place (not deleted)", which reads as untouched. It is now counted as destroyed, and the message says its name
is still in the folder. Folders inside it that could not be opened are named as still on the computer too.
Verify the download
Get-FileHash .\SysManager-v1.136.170.exe -Algorithm SHA256
Expected SHA256: 686DCD91ED93693FE8123D9CE0410FD6977F7219E579B671585926AE03D2FD81
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.170.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.170.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.https://github.com/laurentiu021/SystemManager/releases/tag/v1.136.170