SysManager 1.136.67 yüklə

[1.136.67] - 2026-11-02
System Health's disk check repairs nothing, as its card says, says in plain words what chkdsk found, and keeps its result when the drive list is refreshed.
Fixed
- The disk check ran chkdsk /scan, which repairs what it can while the drive is in use, under a card that says
it reports problems without fixing them. It now runs chkdsk /scan /forceofflinefix, which leaves every repair
for when the drive is not in use, and a drive with problems reads "Problems found", with the status line saying
how Windows repairs them. This was there since 0.3.0.
- A repair could not be shown: chkdsk follows "Windows has made corrections to the file system." with "No
further action is required.", which a healthy scan ends with too, and the healthy sentence was read first. A scan
that found problems matched no sentence and read "Exit 3". chkdsk's own sentences are now read in an order where
none hides another, and an exit code with no sentence the tab knows is said in words. This was there since
0.28.3.
- Refreshing the drive list, Scan or F5 while a check ran left the drive's row saying "Idle": the check wrote
"Running..." and its verdict to the rows it started with, which a refresh had replaced. The check now writes to
the row on screen, and a refresh keeps each drive's status as it keeps its tick. This was there since 0.4.0.
- A row's own Scan left the header showing what the last "Scan selected" did, in the running colour, for the whole
run. It now says which drive it scans and how the scan ended. This was there since 0.4.0.
Verify the download
Get-FileHash .\SysManager-v1.136.67.exe -Algorithm SHA256
Expected SHA256: 21388AE6BC47126590B94925A3AEE365986902E7A40AB16DA550F0E8FD0611B3
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.67.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.67.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.