How can we help?

Client Filter 10.30 EA Release (Dec. 6, 2022)


The Netsweeper Client Filter 10.30 EA is now available. This release updates a lot of shared libraries to the latest release along with adding some new functionality for Windows to watch the registry keys for changes. Customers running the 10.x Client on Windows, MacOS, Chrome, iOS or Android should consider upgrading to the 10.30 EA release.

Netsweeper will be moving to the Chrome Client Filter v3 manifest over the next few Sprint cycles. Google has extended the V2 Manifest for enterprise policies until January 2024 due to a lot of the changes and problems many developers have been running into. We are committed to making sure the new V3 manifest is available before customers can no longer use the V2 manifest version. More information from Google can be found here,

If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (

Return to the Client Filter 10x Release Notes page.

Previous Release and Next Release


10.30 Change Log

Issue Type





The Windows Client Filter System Tray now disappears on shutdown or restart of the service.



The nMonitor brand did not update the Chrome nsfilter-ea.xml and nsfilter-beta.xml files for the 10.20 release.

New Feature


The Chrome Client Filter now has the ability to use different brand settings between Chrome browsers and Chromebooks running on different operating systems.

New Feature


Chrome Client Filter 10.30 and above now supports disable/enable using the -f 8 (disabled) and -c -f 0 (enable) to enable filtering.

New Feature CF-123 Shared iPAD Support has been enabled to allow the Netsweeper nFilter for iOS VPN Client to work with multiple users and allow for fast user switching.



Changing the policy service from a 7.2 or later release to an older version could cause the Client Filter to fail open or close. Now we do not reset the protocol version when no protocol version is explicitly sent from the policy server.



There is now the ability to read CONFIGEDIT="-p -y brand123" and NMONITOR_CONFIG="" in the MacOS installer so customers can Brand it without getting a Brand.



The Chrome filter did not parse multiple -f if listed in ConfigEdit.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request