SysManager 1.52.78

What's new for you

Your hosts file comments are now safe. SysManager previously deleted standalone comments that happened to start with a digit or colon (like "# 5G adapter notes" or "# 1. Block ads") whenever you saved — they vanished silently. It also failed to show disabled IPv6 entries whose address begins with a hex letter (e.g. # fe80::1 myserver), making them impossible to re-enable through the UI. Both are fixed: comments survive round-trips, and all valid IPv6 entries are visible.

---

[1.52.78] - 2026-07-10

Fixed

• Hosts file manager silently deleted standalone comments starting with a digit or colon (e.g. "# 5G adapter notes", "# 1. Block ads") and failed to recognize disabled IPv6 entries whose address starts with a hex letter (e.g. "# fe80::1 myserver"). The internal LooksLikeIpStart heuristic only checked whether the first character after # was a digit or colon — a crude approximation that disagreed with the real acceptance test (IPAddress.TryParse + two-token minimum) in both directions. (1) False negatives: IPv6 addresses starting with a–f (like fe80::, fd00::) failed the heuristic, so those disabled entries were invisible in the grid (no data loss — they survived as comments — but could not be re-enabled through the UI). (2) False positives: digit-or-colon-leading comments passed the heuristic (line 71) and were treated as candidate entries, but then failed IPAddress.TryParse (line 86) and fell through both code paths — they were neither parsed as entries nor preserved as standalone comments, causing silent data loss on the next save. Replaced with IsDisabledEntryLine that mirrors the parser's own logic: strip inline comment, split on whitespace, require tokens.Length >= 2 && IPAddress.TryParse(tokens[0], out _).

---

Verify the download

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

Expected SHA256: 5E14825C71C69B9DFAC9FC4A4710721FD5F8B404D55CC551F7EA000BCE76B9B2