Skip to content

SysManager 1.52.82

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jul 12:50
· 711 commits to main since this release
v1.52.82
286ee48
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new for you

The Health → Disk drive list is now resilient to a single problematic drive. Previously, if one volume was BitLocker-locked or momentarily busy at the moment of the scan, the entire drive list could come back empty — hiding your healthy drives too. Now that one drive is simply skipped and all the others show up normally.

[1.52.82] - 2026-07-10

Fixed

  • Drive enumeration aborted entirely when a single volume's DriveFormat property threw (e.g. BitLocker-locked or transiently busy). FixedDriveService.Enumerate() used a LINQ .Where(di => ... di.DriveFormat ...) predicate to filter drives to NTFS/ReFS. Because LINQ predicates evaluate lazily during MoveNext(), the DriveFormat property access ran OUTSIDE the per-drive try/catch block (which only covered the loop body). An IOException from one BitLocker-locked or transiently-busy volume caused the IEnumerator.MoveNext() call to throw, aborting enumeration of ALL remaining drives — even healthy ones. Callers (Deep Cleanup, System Health) saw zero drives instead of all-minus-one. Moved the DriveFormat filter inside the per-drive try block so one flaky volume is skipped (logged at Debug) while all remaining drives enumerate normally. The DriveType and IsReady checks remain in the predicate — those are backed by cached kernel data and do not hit the volume handle.

Verify the download

Get-FileHash .\SysManager-v1.52.82.exe -Algorithm SHA256

Expected SHA256: FF091AB1D0015598838818074FCBFD2CD4B1CC283787F6F2A769FA11F0DACE59

Assets 4
Loading