Repository navigation
SysManager 1.20.19
·
1026 commits
to main
since this release
[1.20.19] - 2026-06-12
Fixed
- Activity history can no longer be corrupted by concurrent updates. The recent-actions log saved its data outside the lock that protects it, so two actions logged at the same time could clash and produce a "collection modified" error or a truncated file. It now writes a consistent snapshot taken under the lock.
- The in-app updater fails gracefully when the download location can't be determined. Installing an update now checks the downloaded file's folder up front and shows a clear message instead of risking a crash.
Fixed
- More resilient reading of battery, memory, and app-list data. Unexpected values from Windows (battery stats, memory-module details) could throw a conversion error and interrupt a scan; those conversions now fall back safely. The winget output parser also no longer throws when the tool reports columns in an unusual order.
Fixed
- Plugged several resource leaks. The system-tray icon's underlying graphics handle was never released on shutdown; the elevated-relaunch helper left a process handle open; and a memory-module query left a WMI result set undisposed. All are now released properly. Also added handling for a WMI namespace being unavailable when reading drive media/bus details, so that case fails quietly instead of surfacing an error.
Fixed
- Starting or stopping a Windows service no longer crashes the app on failure. If a service couldn't be started or stopped (access denied, a dependency problem, or the service state changing mid-operation), the underlying error escaped unhandled. Those failures are now caught and shown as a clear status message.
- Privacy toggles no longer crash on a registry write error. Applying a privacy toggle only handled permission errors; a registry I/O error or an invalid key/value now logs a warning instead of bringing down the app.
- Disabling Xbox Game Bar no longer crashes on a registry I/O error. The Performance tab's Xbox Game Bar action now handles I/O failures the same way it already handled permission and state errors.
- A misbehaving UI subscriber can no longer permanently lock an operation category. If a property-change notification threw while acquiring an operation lock, the category could stay locked forever (blocking all future disk/network/system operations of that kind). The lock is now rolled back cleanly if that happens.
Verify the download
Get-FileHash .\SysManager-v1.20.19.exe -Algorithm SHA256Expected SHA256: D79C8A0A4630A3A30839A98C164EFCBF4763B88C91408093FFE1A4AD015429C4