Skip to content

SysManager 1.52.84

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jul 13:22
· 709 commits to main since this release
v1.52.84
d0b882d
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

Traceroute (in the Network tools) now traces a clean path to the site you enter. Before, for big sites served from many servers (like google.com), it could mix hops toward different servers into one confusing route. It now locks onto a single address up front, so the route reads correctly.

[1.52.84] - 2026-07-10

Fixed

  • Traceroute re-resolved the destination hostname on every probe, so a round-robin / CDN host could produce a garbled route toward different servers. TracerouteService.RunAsync passed the raw hostname string into Ping.SendPingAsync inside the per-hop/per-probe loop, re-running DNS for each of up to MaxHops * ProbesPerHop (30×2 = 60) probes. For a load-balanced hostname (e.g. google.com), consecutive TTLs could resolve to different destination IPs, interleaving hops toward different servers into one nonsensical route — plus ~60× redundant DNS lookups. The destination is now resolved exactly once, up front, via a new ResolveDestinationAsync helper (IP literals are used verbatim with no DNS; hostnames pin the first Dns.GetHostAddressesAsync result), and every probe targets that fixed IPAddress. A resolution failure now surfaces as InvalidOperationException (the type the ViewModel already handles) instead of silently looping MaxHops times with per-probe DNS failures. Single-IP hosts and IP literals were never affected; the reverse-DNS lookup of each responding hop is unchanged.

Verify the download

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

Expected SHA256: F9F6200F3B55C40060373270382C24C11E190E84443C371A52C92AD5C14C8B01

Assets 4
Loading