Pakua SysManager 1.118.0

[1.118.0] - 2026-10-06
Battery Health now shows how the battery has worn over time, and whether that is normal. A new card draws how
much charge the battery holds when full, from the history Windows keeps of it, with one sentence saying whether it
is wearing at the usual rate.
Added
- Capacity over time on Battery Health (#1513). The tab showed one reading, "Health 87%", which cannot be read as
fine or failing without something to compare it to.
- The line is what the battery holds when full as a percentage of what it held when new, the same measure as the
Health figure, with a dashed line at 100%. It comes from the history Windows keeps in its battery report, a
point a week and a point a day for the last few days, so it shows months on the first visit. The report is
written to a temporary file, read and deleted, and needs no administrator rights.
- One verdict under it. Up to 8% lost in the last six months is normal wear, up to 15% a little faster than
usual, more than that faster than usual. A shorter history is scaled to six months, and under three months a
loss above the normal rate is called too early to tell. The verdict says what helps and never says the battery
is dying.
- Each end of the period is the median of up to three entries, because the full-charge figure moves a point or
two from week to week on a healthy battery.
- After a battery replacement the line starts at the new battery instead of drawing it as a recovery. With less
than a month of history the card says how much Windows has recorded so far; when Windows keeps none, or the
report cannot be read, it says so in one line. A failed read after a good one keeps what was shown.
- The card is not shown on a PC without a battery, and the report is not run there.
Changed
- The note under Health and Wear no longer says that Windows reports capacity only to an elevated process. The two
figures still need administrator rights because of where SysManager reads them; the battery report does not.
Verify the download
Get-FileHash .\SysManager-v1.118.0.exe -Algorithm SHA256
Expected SHA256: 1A2DC63E2839182AC317AF19795C3264C9673707070F438D216B2A35B9BA7DED
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.118.0.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.118.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.