Version 3.8.15 of the Windows Roaming Client is now available on the . The latest installer is available in the dashboard under .

Version 3.8.15 of the Windows Roaming Client is now available on the . To install, download the latest beta installer from the dashboard under .

Version 3.7.11 of the Windows Roaming Client is now available on the . The latest installer is available in the dashboard under .

DNSFilter's DNS-layer protection already follows users onto any network, but being covered is not the same as being private. On hotel Wi-Fi, in airport lounges, and on the home connections where hybrid work actually happens, the destinations a device reaches stay visible to whoever runs the network — and to the ad networks, location trackers, and data brokers collecting alongside. SecureTransit closes that gap by making privacy a policy the organization enforces, not a choice each user has to remember to switch on.

The Windows agent replaces the right-click tray menu with a full DNSFilter One window, themed to match your system's light or dark mode.

Some networks don't leave DNS alone. Hotel Wi-Fi, captive portals, and ISPs that quietly intercept resolvers can redirect DNS traffic before it ever reaches DNSFilter — and on those networks, blocked domains could resolve anyway, with neither the admin nor the end user aware the gap existed. DNS PreCheck v2 detects that interference and keeps policy enforced regardless of what the local network does with DNS.

Version 3.7.11 of the Windows Roaming Client is now available on the . To install, download the latest beta installer from the dashboard under .

DNSFilter's DNS-layer protection already follows users onto any network, but being covered is not the same as being private. On hotel Wi-Fi, in airport lounges, and on the home connections where hybrid work actually happens, the destinations a device reaches stay visible to whoever runs the network — and to the ad networks, location trackers, and data brokers collecting alongside. SecureTransit closes that gap by making privacy a policy the organization enforces, not a choice each user has to remember to switch on.

The Windows agent replaces the right-click tray menu with a full DNSFilter One window, themed to match your system's light or dark mode.

Version 3.6.10 of the Windows Roaming Client is now available on the . The latest installer is available in the dashboard under .

– DNS PreCheck now maintains policy enforcement even on networks that hijack or redirect DNS traffic — closing a gap where certain network conditions could allow content through that should have been blocked. PreCheck v2 is being rolled out gradually and is not automatically enabled with this agent update. Once enabled, the tray will update to show "DNS PreCheck v2" to confirm the active mode.

– The system tray process now automatically restarts if it stops unexpectedly, keeping tray status and controls available without requiring a manual restart of the client or machine.

– The agent now correctly restores DNS settings on all network adapters when the service stops, including on machines with multiple adapters such as a VPN or virtual adapter alongside Wi-Fi.

– The agent now reliably resumes filtering through PreCheck and Transparent Proxy modes after a network interruption or sleep/resume cycle without requiring a service restart.

– The loopback proxy no longer starts when the client is running in Transparent Proxy or PreCheck mode, preventing the two filtering paths from conflicting.

– Resolved an issue where the agent could crash or enter repeated service restart cycles after waking from sleep, causing intermittent DNS resolution failures until the service recovered.

– Resolved an issue where the agent returned SERVFAIL instead of NXDOMAIN for non-existent records in Classic (Loopback) mode, causing browser retry behavior and extended DNS delays on page loads.

– Resolved an issue where the Last Sync timestamp in the system tray froze after agent startup and never updated, even while the device was online and actively filtering.

– Resolved a conflict between the Roaming Client and GlobalProtect VPN that could cause DNS resolution failures and in some cases an agent crash.

– Resolved an issue where a null value for the browser extension setting in the API response caused the agent's configuration sync to fail on every cycle, preventing local domains and other dashboard settings from reaching the agent.

Version 3.6.10 of the Windows Roaming Client is now available on the . To install, download the latest beta installer from the dashboard under .

Version 3.4.23 of the Windows Roaming Client is now available on the channel. This release addresses a DNS resolution issue affecting some endpoints on dual-stack (IPv4 + IPv6) networks.

To install, download the latest production installer from the dashboard under Deployments → Roaming Clients.

– When installed on a Windows Server OS, the agent now automatically falls back to Loopback filtering mode rather than attempting to load unsupported filtering modes. Windows Server OS is not an officially supported environment, but this change prevents unexpected behavior on Server deployments.

– Devices are now identified more consistently in the dashboard, reducing missing identifiers after upgrades or reinstalls causing duplicate entries

– Improved installer prerequisite validation and upgrade handling — failed upgrades no longer leave the endpoint without the Roaming Client installed.

– Resolved issues affecting endpoints on dual-stack (IPv4 + IPv6) networks where the agent could interfere with other networking software, in some cases preventing local or public DNS queries from resolving correctly.

– Resolved scenarios in Transparent Proxy mode that could cause local-name and search-suffix DNS lookups to fail or leave the endpoint without connectivity.

– Resolved a conflict that could cause the DNSFilter tray icon to be unreliable on shared/multi-user Windows machines and in environments with certain third-party applications.

Version 3.4.23 of the Windows Roaming Client is now available on the . This release addresses a DNS resolution issue affecting some endpoints on dual-stack (IPv4 + IPv6) networks.

To install, download the latest beta installer from the dashboard under .

We've released Windows Roaming Client v3.3.8 with an improvement to how the agent handles connectivity checks in the background.

– Reduced the frequency of internal connectivity checks performed by the Windows Roaming Client under steady-state conditions. Checks are now triggered by actual network events rather than on a fixed polling cycle, improving efficiency without impacting connectivity detection or DNS filtering behavior.

– Resolved an issue where transient IPv6 route changes could leave the agent in a state where filtering was marked as not working, even though network connectivity had not actually changed. The agent now correctly recovers and resumes filtering when the underlying network state has not changed.

We've released Windows Roaming Client v3.3.6 to address a local domain resolution issue affecting some users on Classic DNS Filtering.

– Resolved an issue where local network resources were not resolving correctly for some users after updating to Windows Roaming Client v3.3.1 with Classic DNS Filtering enabled. Local domain resolution now works as expected.