Pakua SysManager 1.114.49

[1.114.49] - 2026-09-29
Deep Cleanup and Windows Update no longer work on the same folder at the same time. Cleaning the Windows
Update caches now waits for an update install or a Windows Update reset to finish, and they wait for it.
Fixed
- Deep Cleanup could delete inside the Windows Update folder while Windows Update was using it. Two of its
categories, "Windows Update cache" and "Delivery Optimization cache", delete inside
%WinDir%\SoftwareDistribution. A Windows Update install reads its downloaded packages from there while it
runs, and Reset Windows Update renames the whole folder, which fails while anything inside it is open. Deep
Cleanup held a different lock from both, so a clean could remove packages an install still needed, or make
a reset fail.
- With either category ticked, Deep Cleanup now also takes the lock the install and the reset hold, so none
of the three starts while another runs. A clean started during an install says "Cannot start — untick
"Windows Update cache" or wait: Windows Update install is already running.", and an install or a reset
started during a clean says that Deep Cleanup is running.
- The lock is given back as soon as the files are deleted, before the rescan that follows. The rescan only
reads, and on a used PC it can take minutes.
- A clean without either category is unchanged.
Present since v0.5.0 for an update install, and since v1.26.0, when System Fixes gained Reset Windows
Update, for the reset.
Verify the download
Get-FileHash .\SysManager-v1.114.49.exe -Algorithm SHA256
Expected SHA256: 8D92F3A96EFC4950C1591D829F810DE218D73D111CA0D68756F7BF7E157C8978
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.114.49.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.114.49.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.