How can we help?

Client Filter 10.40 EA Release (Jan. 10, 2023)


The Netsweeper Client Filter 10.40 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.40 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 (

Netsweeper Client Filter 10 Features

  • Support for iOS Shared iPads allowing for filtering when a single device is used by multiple users
  • Firefox browser updates for the iOS release
  • Ability to differentiate brand between Chromebook and Chrome Browser running Windows/MacOS
  • Improved Windows Registry GPO/registry key change to allow for more flexible group policy settings changed per user
  • Experimental Windows performance improvements allowing the Windows Client Filter to operate closer to line rate performance. This must be enabled manually for customer who wish to test this new experimental kernel driver.
  • Automated silent install for MacOS and improved configurability for Upgrade vs Install

Return to the Client Filter 10x Release Notes page.

Previous Release and Next Release






Chrome Web Store

10.40 Change Log

Issue Type





The Chrome nMonitor 10.10 to 10.30 loading keyword lists and all versions did not detect and reload Keyword Lists in prior releases.



The private key password loading has been improved to be more secure by generating the SHA256 directly into the password callback memory and removing stack copy/clear requirement.

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