Aquesta és una versió anterior. La versió actual és la 1.130.86. SysManager 1.130.86 · Data de publicació:
Fitxers d’instal·lació 1.114.4
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
[1.114.4] - 2026-09-28
Several tabs work again for anyone who opens SysManager without "Run as administrator". Preinstalled
Apps found no apps, DNS found no network adapter, Scheduled Maintenance could not be turned on, and Defender
Tweaks showed protection as "On" without having read it. They now read the PC as they already did for an
administrator, and where Windows itself keeps something from a standard user, the tab says so.
Fixed
- Tabs that use PowerShell came back empty for anyone not running as administrator. A standard user's
session ran SysManager's PowerShell scripts inside the app, on a PowerShell that has only its core
commands: none of the everyday ones such as Select-Object, Sort-Object or Test-Path, and none of the
Windows modules for Store apps, Defender or optional features. Every script that used one failed and came
back with nothing, and nothing said so. Preinstalled Apps showed "No Store apps found", DNS could not find
the active network adapter, Scheduled Maintenance could not register its task, Task Scheduler never showed
a task's last and next run, and Defender Tweaks showed a status it had never read. Every session now runs
its scripts in Windows PowerShell 5.1, as an administrator's already did, and finds modules only in the
machine-wide folders, never in the user's own. The first PowerShell action on a tab can take a moment
longer while Windows PowerShell starts. Standard-user sessions have used the in-app PowerShell since the
first release, v0.3.0; since v1.56.2 moved administrator sessions to Windows PowerShell 5.1, only standard
users were affected.
- Restore Points: a standard user is told the list needs administrator, not that there are none.
Windows answers a standard user's request for the list with "Access denied". The tab reported that as "No
restore points found. System Restore may be turned off for this PC." on PCs that had several, and its
banner said the list could be viewed without elevation. It now says the list could not be read and that
"Run as administrator" shows it, and the banner and subtitle say listing needs administrator too. Present
since the tab was added in v1.23.0.
- Defender Tweaks: a status that could not be read is shown as unavailable, not as protection "On". When
a Defender read failed, the tab still built a status out of nothing, and a missing "turned off" setting
reads as protection on. That was every standard user's status until the fix above, and it is still what
happens when the Defender service is not running. The read now stops, and the tab shows the status as
unavailable. Present since the tab was added in v1.39.0.
- Defender Tweaks: a standard user's exclusion list says it is hidden. Windows shows Defender's
exclusions only to an administrator and gives a standard user the sentence "N/A: Must be an administrator
to view exclusions" in their place. The card said "No exclusion folders", which it could not know, and
with the first fix above it would have listed that sentence as a folder. It now says the exclusions are
hidden and that "Run as administrator" shows them. Present since the card was added in v1.45.0.
Verify the download
Get-FileHash .\SysManager-v1.114.4.exe -Algorithm SHA256
Expected SHA256: E70CA6A5635F8B326F48FD1EB0A8B3366ECDB6BA8D538F862BA457F76E2D5828
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.4.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.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.114.4