Shkarko SysManager 1.136.106

[1.136.106] - 2026-11-05
Importing a profile asks about the settings it will overwrite, by SysManager's own names for them, and says how many sections it will skip.
Fixed
- The import confirmation listed each section by the name written in the profile, but the import writes by the
section's key. A shared or hand-edited profile could show "Theme & appearance" for the section that lets the Bulk
Installer fetch app icons from the web, an empty line for a section with no name, and a section SysManager does not
know as if it would be imported, though the import skips it. Each section is listed by SysManager's own name for it
now, the ones the import skips are counted but not named, and the status afterwards counts only the sections the
confirmation listed. Since Profile Export / Import first shipped, in 1.28.0.
- The confirmation's "Exported … by SysManager v…" line showed the version as the file wrote it, so a profile could
put text of its own there. It shows only a version number read from the file now, and leaves out a date or version
the file does not carry instead of showing "0001-01-01" or a bare "v". Since 1.28.0.
- A profile with no section SysManager knows asked to be imported and then imported nothing. It says there is nothing
to import now, without asking.
Verify the download
Get-FileHash .\SysManager-v1.136.106.exe -Algorithm SHA256
Expected SHA256: DEEED29F9FC24A1157224B7C4C0E5A8AA37B69F238D13A43744CC9ED347E88CE
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.106.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.106.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.