Follow up on the latest improvements and updates.

RSS

March 3, 2026

new

Windows Roaming Client

3/3 March 3 – CyberSight Beta for Windows Roaming Client (v3.2.0)

CyberSight is now available in the

Windows 3.2.0 Beta Roaming Client

for customers using the Beta Channel.

To enable CyberSight, go to

Roaming Clients → Control Center → CyberSight

in your dashboard and toggle on CyberSight Analytics and Browser Extension URL.

✨

What’s New

CyberSight Activity Overview & Logs Dashboards

– A new device activity logging capability that records time-stamped user behavior to provide context around security events and operational issues.

CyberSight delivers a behavioral timeline that combines:

Full browser URL visibility
Application usage
Device state changes

All within a single, unified dashboard view.

This creates a clearer picture of what occurred before, during, and after an event — giving administrators actionable context beyond DNS data alone.

✅

Why It Matters

Reconstruct activity surrounding endpoint alerts and suspicious events
Detect unusual or risky activity earlier
Support compliance and acceptable-use reviews with objective activity records
Improve troubleshooting during outages or service interruptions
Maintain visibility even when alternate DNS resolvers or proxies are used

March 2, 2026

new

Windows Roaming Client

03/02 March 2 - Windows Roaming Client v3.2.0 Beta

The latest

Windows Roaming Client (v3.2.0)

is now available in the

Beta Channel

and can be downloaded from

Deployments → Roaming Clients → Install Roaming Client

in your dashboard.

🛠️Improvements

Reduced Installer Size & Improved Windows Agent Performance
– The Windows Roaming Client installer has been optimized to reduce size and improve runtime efficiency, enabling faster deployments and smoother performance across devices.

🪲 Bug Fixes

Improved Configuration Handling During Sleep & Resume
– Resolved an issue where configuration changes processed while a device was in modern standby could result in broken filtering or DNS behavior upon wake. The agent now defers network-impacting changes until the device is fully awake.
Corrected DualStack IPv6 Failover Logic
– Fixed a condition where loss of IPv6 connectivity could leave devices without DNS resolution instead of automatically failing over to IPv4.
Resolved Whitelabel Configuration Issue
– Ensured required configuration files are written during installation for whitelabeled deployments, preventing service startup failures and restoring full functionality for integrations such as CyberSight and dashboard reporting.
Addressed DNS Failures on Startup
– Eliminated a startup condition that caused DNS queries to fail for several seconds before upstream connectivity was established.

January 21, 2026

new

Windows Roaming Client

1/21 January 21 DNS PreCheck Beta for Windows Roaming Client

DNS PreCheck

is now generally available in the

Windows 3.1.0 Beta Roaming Client

for customers using the Beta Channel.

To enable DNS PreCheck, go to

Roaming Clients → Control Center → Connection & Filtering

in your dashboard.

✨ What’s New

DNS PreCheck (modern DNS protection)

– A transparent DNS proxy that validates and filters DNS locally before queries leave the device. This reduces conflicts, improves reliability on unmanaged networks, and helps preserve connectivity without requiring DNS setting changes.

New Connection & Filtering Mode framework

– Configure behavior directly from the

Roaming Client Control Center

across three dimensions:

Connection Mode:
Transparent Proxy or DNS Loopback
Filtering Mode:
Classic DNS or DNS PreCheck
Failover Mode:
Fail Open or Fail Closed

✅ Why It Matters

More reliable protection
on untrusted networks with fewer DNS conflicts
Greater admin control
with predictable behavior and clearer outcomes
A stronger foundation
for future feature delivery and cross-platform consistency

⚠️ Known Limitations

Some network and VPN/security configurations may impact behavior in certain environments. For details, see our knowledge base.

December 17, 2025

new

Windows Roaming Client

12/17 December 17 - Windows Roaming Client v3.1.0 Beta

The latest

Windows Roaming Client (v3.1.0)

is now available in the

Beta Channel

and can be downloaded from

Deployments → Roaming Clients → Install Roaming Client

in your dashboard.

🛠️ Improvements

More helpful
client logging
is enabled by default, making Windows troubleshooting easier
Upgrade checks now account for local client state
, reducing unnecessary
DNSFilter Updater
requests and limiting repeated upgrade attempts
The Windows
tray icon now determines connection state independently of DNS
, improving reliability and reducing flicker during state changes

🪲 Bug Fixes

Fixed an issue where DNS settings were not applied after wake or certain network transitions, which could prevent filtering from resuming until the client re-evaluated the connection
Fixed a configuration precedence issue where legacy registry values could override settings defined in appsettings.overrides.json file

⚠️ Known Issue

Automatic upgrade from Windows Roaming Client 3.0 to 3.1.0 does not occur.
Devices running 3.0 must manually install version 3.1.0.
Duplicate dashboard entries may appear after upgrading to 3.1.0
on devices that were fresh-installed on Windows Roaming Client 3.0 and may require cleanup.

November 13, 2025

new

improved

fixed

Windows Roaming Client

RC Release Channels

Beta

11/13 November 13 - Windows Roaming Client v3.0.0 Beta

The latest

Windows Roaming Client (v3.0.0)

is now available in the

Beta Channel

and can be downloaded from

Deployments → Roaming Clients → Install Roaming Client

in your dashboard.

✨ What’s New

🧱

Modernized Architecture

Implemented a modern architecture that improved reliability, performance, and long-term maintainability.

Upgraded to
.NET Core
, aligning with modern Windows frameworks and improving compatibility with future releases.
Refactored core services for more consistent performance and cleaner communication between components.
Streamlined update handling and service behavior for smoother operation in complex environments.
Establishes a stronger, more maintainable base for future feature development and cross-platform consistency.

🧩

Configuration & Management Improvements

Introduced a unified configuration structure that simplified management, customization, and troubleshooting across deployments.

Centralized configuration, logging, and overrides to make setup and maintenance more consistent.
Adopted a modern configuration model.
Registry support temporarily continues
, but all custom settings should now be applied through the
appsettings.overrides.json
file. This update also enables distinction between server-managed and local device configurations.
Standardized validation and logging to ensure settings apply correctly during upgrades and improve diagnostic clarity.
Established a foundation for future dashboard-based configuration visibility and remote management.

🪲 Bug Fixes

Improved VPN Compatibility Recognition
– Fixed an issue where the client ignored the dashboard’s VPN Compatibility setting until the service restarted, causing inconsistent behavior in 2.x deployments.
Enhanced Recovery Handling
– Addressed a condition where the client failed to recover automatically after a “pipe not connected” error, requiring a manual restart.
Corrected Logging Behavior
– Resolved inconsistent log rotation and retention that could lead to excessive file sizes or missing entries.
Stabilized IPv6 Operation
– Fixed a failure mode in IPv6-only environments where the client incorrectly closed filtering if no IPv6 DNS was advertised.
Improved Configuration Reliability
– Fixed scenarios where client overrides (such as VPN or registry-based settings) were not applied during startup or reinstallation.

August 13, 2025

fixed

Windows Roaming Client

RC Release Channels

8/13 August 13 - Windows Roaming Client v2.2.1 Production

A new version of the Windows RC is now available via the Production channel. This version can be downloaded from the dashboard Deployments → Roaming Clients → Install Guide
, or by selecting the Install Guide 
from the Control Center
 in the Roaming Client Management
 dashboard. 
Organizations with Automatic Updates turned on will start receiving this update incrementally from the date of this release.
For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.
🪲 Bug Fixes
Changed the default connection preference back to IPv4 for better reliability; IPv6-IPv4 mode is still available to configure as needed
Improved how the app handles certain IPv6 networks that don’t provide their own DNS, reducing connection failures
ℹ️ Note:
 In rare IPv6-only network configurations without an advertised IPv6 DNS server, connectivity may still be impacted when manually selecting IPv6-only mode
🤓 Dad Joke
I got a pet termite🐛and named it Clint. Clint Eatswood🪵

July 30, 2025

improved

fixed

Windows Roaming Client

RC Release Channels

7/30 July 30 - Windows Roaming Client v2.2.0 Production

A new version of the Windows RC is now available via the Production channel. This version can be downloaded from the dashboard

Deployments → Roaming Clients → Install Guide

, or by selecting the

Install Guide

from the

Control Center

in the

Roaming Client Management

dashboard.

Organizations with Automatic Updates turned on will start receiving this update incrementally from the date of this release.

For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.

✨What's New

🧰

Expanded Device and Protocol Support

ARM64 Architecture Support
Now available: a separate build for ARM64-based Windows devices, extending protection to a broader range of hardware beyond x64.
IPv6 Support
Full IPv6 support is now included. DNS queries from IPv6-enabled devices are routed properly through DNSFilter. IPv6 is now attempted first by default—no registry changes needed.

🛡️

Service Manager: Improved Stability & Self-Healing

A new Service Manager has been a dded to monitor and protect the Roaming Client in real time:

Automatically checks health every 5 minutes
Restarts services if needed
Self-repairs and verifies installation integrity
Runs as a Windows service with enterprise-ready behavior
Now bundled with the installer

Think of it as built-in resilience—if the client goes down, it brings itself back up.

🛠️Improvements

🧹

Smarter Startup with Built-in Cleanup

The client now removes outdated or leftover registry settings on startup, helping avoid config-related issues and ensuring a cleaner, more reliable launch experience.

💽

Smarter .NET 8 Dependency Handling

The installer now detects and installs missing .NET 8 dependencies automatically, reducing manual setup steps and avoiding install-time errors.

🧩

Better Compatibility with Windows Defender

The installer now better aligns with Windows Defender and related security settings to avoid being flagged in stricter environments.

🪲 Bug Fixes

Local Domain Resolution
Fixed an issue where the client failed to fall back to a secondary DNS suffix for local domain lookups.
API Error Handling
The client now retries on temporary API errors instead of shutting down, improving service continuity.
Startup Reliability During API Downtime
Improved behavior during initial startup if DNSFilter’s API is temporarily unreachable.

🤓 Dad Joke

Don't throw false teeth 😬 at your vehicle -- you might denture car🚗

July 16, 2025

improved

fixed

Windows Roaming Client

RC Release Channels

7/16 July 16 - Windows Roaming Client v2.2.0 Beta

A new version of the Windows Roaming Client, v2.2.0 Beta, is now available via the Beta channel. This release supersedes the v2.1.0 Beta, incorporating feedback from beta users and adding key improvements to ensure better compatibility and reliability across various environments.

This version can be downloaded from the dashboard

Deployments → Roaming Clients → Install Guide

, or by selecting the

Install Guide

from the Control Center in the

Roaming Client Management

dashboard.

For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.

🔁 Recap of v2.1.0 Beta

🧰 Support for ARM64-based Windows devices
🌐 IPv6 compatibility, enabled by default
🛡️ Introduction of the Service Manager for auto-healing and service monitoring
🧹 Built-in cleanup of outdated registry settings
🪲 Stability improvements during DNSFilter API downtime

👉 View the full v2.1.0 Beta changelog

----------------------------------------------

✨What's New in v2.2.0 Beta

💽 Smarter .NET 8 Dependency Handling

The installer now detects and installs missing .NET 8 dependencies automatically, reducing manual setup steps and avoiding install-time errors.

🛠️Improvements

🧩 Better Compatibility with Windows Defender

Updated the installer to better align with Windows security settings, reducing the chance of being flagged in environments with stricter protection enabled.

🪲 Bug Fixes

🌐 Local Domain Resolution

Fixed an issue where the client failed to fall back to a secondary DNS suffix for local domain lookups.

🤓 Dad Joke

What did the tectonic plate say after bumping into another? Sorry, my fault! ⛰️

May 29, 2025

improved

Windows Roaming Client

RC Release Channels

Beta

5/29 May 29 - Windows Roaming Client v2.1.0 Beta

A new version of the Windows Roaming Client, v2.1.0 Beta, is now available via the Beta channel. This version can be downloaded from the dashboard Deployments → Roaming Clients → Install Guide
, or by selecting the Install Guide 
from the Control Center
 in the Roaming Client Management
 dashboard. 
For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.
What's New in Windows Roaming Client v2.1.0
🧰 ARM64 Architecture Support
You've asked for it, you've got it! With version 2.1.0 Beta, we now have a separate build to support devices that run ARM64-based architecture. This tandem approach ensures that protection can extend to devices outside of the x64 Windows architecture. 
🌐 IPv6 Support
We’ve added full IPv6 support
 to the Windows Roaming Client. This means better compatibility and future-proofing as internet providers and networks increasingly rely on IPv6. DNS queries from IPv6-enabled devices will now route properly through DNSFilter, just like IPv4. 
Where previous versions had provision for enabling IPv6 through a registry modification, this version tries IPv6 by default first.
🛡️ Improved Stability & Self-Healing with the Service Manager
This release introduces a new Service Manager
 that monitors and protects the Roaming Client in real time. Here’s what it does for you:
Monitors health automatically: 
It checks in every 5 minutes to make sure the Roaming Client is running as expected.
Restarts services if needed:
 If something goes wrong (like a service unexpectedly stops), Service Manager will try to restart it immediately—no action needed from you.
Self-repairs and verifies installations:
 It helps ensure upgrades and installations are smooth and that everything’s configured properly.
Runs as a Windows service:
 Seamless operation in the background with better support for enterprise environments.
Now included in the installer:
 Service Manager is packaged with the standard installer, making setup easier.
You can think of this as a built-in safety net—if the client goes down, it’ll get itself back up again.
🧹 Smarter Startup with Built-in Cleanup
We’ve added a feature to clean up leftover or outdated registry settings automatically when the Roaming Client starts. This helps avoid issues caused by old configurations and keeps the app running clean.
🪲 Bug Fixes
Better Handling of API Errors
If there's a temporary issue with the DNSFilter API, the Roaming Client will now retry instead of shutting down. This ensures more consistent service.
Startup Reliability During API Downtime
The client now starts and registers correctly even if there’s a temporary issue reaching DNSFilter’s servers.

May 14, 2025

new

Windows Roaming Client

RC Release Channels

5/14 May 14 - Windows Roaming Client v2.0.10 Production

A new version of the Windows RC is now available via the Production channel. This version can be downloaded from the dashboard Deployments → Roaming Clients → Install Guide, or by selecting the Install Guide from the Control Center in the Roaming Client Management dashboard. 
Organizations with Automatic Updates turned on will start receiving this update incrementally from the date of this release.
For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.
What's New
Version 2.0.10 represents a cumulative build that incorporates all of the enhancements delivered in the previous 2.0.8 Production version, and the two Beta versions since that was released. 
The following enhancements and fixes are being delivered as part and parcel of this release:
More Reliable Connectivity Checks
The Roaming Client now automatically retries its connection to our service if a temporary error occurs, preventing unnecessary shutdowns. This ensures more stable operation by giving the client multiple chances to validate its identity before taking action.
Update Process Optimization
We’ve streamlined how the Roaming Client checks for updates, reducing redundant status checks that were happening too frequently. This improvement boosts performance and efficiency in the background.
Smoother Startup with Built-in Registry Cleanup
The Roaming Client now includes automatic registry cleanup during startup, improving stability—especially when the system was previously in an unstable or "dirty" network state. This replaces the need for manual PowerShell scripts and ensures a smoother initialization process.
Fixed Intermittent Offline Issues
We've resolved a bug that occasionally caused the Roaming Client to go offline unexpectedly, leading to DNS filtering interruptions and VPN disconnections. This fix ensures a more stable and consistent connection, even after the device wakes from sleep.
Improved Network Protocol Switching
Devices that previously cycled between online and offline states every 15 seconds when switching between IPv6 and IPv4 networks will now remain connected. Transitions between network types are now seamless and reliable.

→