Lataa SysManager 1.52.84

[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