SysManager 1.52.101

What's new for you

A fix for custom themes in Appearance. If you saved your own color theme, reopening the theme panel now takes you straight to the color editors (instead of the preset list) and shows your actual saved colors. Previously it could show the wrong panel, and tweaking a single color could quietly reset the other three back to defaults — that data-loss is fixed, so editing one color keeps the rest.

---

[1.52.101] - 2026-07-11

Fixed

• Reopening the theme popup on a saved custom theme showed the preset list instead of the color editors, and editing any one color silently reset the other three. SyncUiToService checked the "Custom" mode radio for a persisted custom theme but never made the custom panel visible (the Mode_Changed handler that toggles panel visibility is wired up only afterward, and re-checking an already-checked radio raises no event), so the popup opened on the Presets list; the only way to reach the editors was to click Dark/Light — which immediately applied a preset over the custom theme — then Custom again. Worse, the four hex fields kept their XAML-default literals and were never seeded from the saved theme, and ApplyCustomFromInputs reads all four on any field's LostFocus — so editing just the accent wrote the defaults for background/surface/text, destroying the user's saved custom colors on the next save. SyncUiToService now sets panel visibility (via a shared UpdatePanels helper Mode_Changed also uses) and, for a custom theme, seeds the four hex boxes and preview swatches from ThemeService.CurrentTheme so a single-field edit preserves the rest.

---

Verify the download

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

Expected SHA256: BBB250C98C9BFB79A85A1F6FA2BDD3F4C01E02CCE9FF20A30FCB324A9564CD9B