Pakua SysManager 1.136.91

[1.136.91] - 2026-11-02
Boot Analyzer names what Windows says slowed boot, with the delay each part added rather than the time it took.
Fixed
- Boot Analyzer gave seven of the ten kinds of slow start-up Windows records the wrong name: prefetching read as an
app or a driver, Group Policy as a service or a device, a device and Windows' Session Manager as "Background", and
the core system as a device. Each row now names what Windows' message names: an app, a driver, a service, the core
system, which the Session Manager is part of, prefetching, Group Policy or a device. Only an app or a service
links to Startup Manager or Services, the tabs that can switch one off; machine policy offered Open Services, and
a device and the Session Manager offered Manage startup items, though neither tab can change them.
- Every delay was the time the part took altogether rather than the delay it added: Windows' Session Manager, which
added 0.45 s, read as 10.5 s, and a typical app's delay was about doubled. The Delay column now shows the delay
Windows measured, and so do Startup Manager's Startup impact column and the Dashboard's check for a slow start,
which adds the delays up and so says a start was slow less often. The names and the delays were wrong since the
tab was added in 1.33.0, and the links since rows got them in 1.105.0.
Verify the download
Get-FileHash .\SysManager-v1.136.91.exe -Algorithm SHA256
Expected SHA256: FCBA495630FB295510BE2FDB535F0912FB88D49202AECEFBB62BEB32DB976E55
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.91.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.91.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.