Pakua SysManager 1.130.57

[1.130.57] - 2026-10-22
Duplicate Finder says why a folder could not be scanned instead of "No duplicates found", and no longer lists two
names of one file as duplicates.
Fixed
- A folder Duplicate Finder could not scan read as one with no duplicates. A folder that no longer existed, a link
to another location, one Windows would not let it list, or one of the folders every scan leaves out, such as System
Volume Information, came back as "No duplicates found". The tab now says the folder could not be scanned, and why.
Since 0.7.0.
- Two names of one file were listed as duplicates. A hard link is a second name for the same file, so deleting
either frees nothing, and where a folder is built on hard links, as a package store can be, deleting one breaks
what uses that name. Duplicate Finder now asks Windows which file it has opened and leaves a file's other names out
of its group and of the space wasted. Since 0.7.0.
Verify the download
Get-FileHash .\SysManager-v1.130.57.exe -Algorithm SHA256
Expected SHA256: D935E7FE82B2874618B0BBDD57022F96F4D68C79E4B4496248E53ED6C89D01BF
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. 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.130.57.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.130.57.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.