AdGuard For Windows Release Notes

v7.22.4 introduces SockFilter

This is one of those moments where a patch deserves the same attention as a full release: v7.22.4 introduces SockFilter, a new, experimental lightweight network driver for AdGuard for Windows. While still far from perfect (you will probably find a few bugs here and there), we’re confident in its potential to make AdGuard better in the future.

Why introduce a new driver at all?

Until now, AdGuard for Windows relied mostly on a WFP driver. WFP is powerful, but it also comes with complexity, compatibility challenges, and stability issues.
The TDI driver used to be an alternative, and while it is still available, it’s an outdated solution and may lead to filtering issues in some versions of Google Chrome. A temporary workaround exists, but it’s not a reliable long-term solution.
The conclusion was simple: it was time for a change. That’s why we’re introducing SockFilter — it brings a different approach that works especially well for ad blocking, plus it’s the solution we’ve been waiting for to finally put these problems behind us.

The advantages of SockFilter

When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers. Right now, it’s still experimental and unstable, so you might not see all the benefits yet. But here’s a look at what’s possible in the future:

• Better interaction with other network apps: SockFilter is designed to cooperate smoothly with VPNs, firewalls, and antivirus software. By avoiding clashes over network control, it can help prevent connection issues and make everything work together more reliably.
• Lower risk of system crashes: SockFilter works in a safer part of Windows networking, which can help it avoid deep system errors that can sometimes cause sudden blue-screen crashes. In practice, this can result in better stability and fewer chances of your system unexpectedly crashing while AdGuard is running.
• On track for better stability: SockFilter works closer to how apps normally use the Internet, instead of dealing with low-level network data, resulting in the potential to reduce complexity behind the scenes and making AdGuard more reliable in everyday use.

Known issues

So far, a small number of users have reported an issue with SockFilter: the new driver appears to interfere with voice and video calls on Discord. The problem was described on GitHub.
Our QA team has successfully reproduced the issue and is actively working on a fix. If you notice any related problems or have additional details to share, please let us know. Your feedback helps us resolve this faster.

How to start using it

Other issues may appear when using SockFilter, after all, Experimental mode means that it’s ready for testing and that there may be bugs. We’d love your help in finding them!
To test it, go to Settings → Network → Traffic filtering, enable traffic filtering, and select SockFilter (Experimental) from the list of available options. If you notice anything unusual, unexpected, or just plain broken, you can switch back to TDI or WFP at any time. In that case, please report the issue on GitHub — your feedback directly helps shape the future of AdGuard for Windows.

Changelog

Improvements

• Added SockFilter driver #5780

Original source Report a problem

Hotfix

In this hotfix, we’re automatically migrating all users from the outdated TDI driver to the more reliable WFP driver. This change comes as a solution to an issue reported by users, ensuring filtering works with the latest versions of Chrome-based browsers, which aren’t fully compatible with TDI.

TDI isn’t going away completely — you can still enable it if you want to. But if you do, the app will show you a clear warning explaining the potential issues and how to temporarily fix them. For all the details, check out our Knowledge Base.

Original source Report a problem

Improved userscript compatibility

This update brings exciting improvements to make your AdGuard experience even better: you now get more customization with our improved userscript compatibility. Behind this change is CoreLibs v1.19, AdGuard’s filtering engine and technical core. Although not strictly tied to this release, we also have something worth celebrating: AdGuard is now available in the Microsoft Store, making installation more convenient and, we dare say, easier than ever.

Some userscripts are designed to work on Single Page Applications (SPAs), such as YouTube. Until now, these scripts often failed to load correctly: if a user opened YouTube’s homepage first, the script wouldn’t inject, and it wouldn’t trigger when navigating to other pages where it was supposed to work. With this update, AdGuard fixes that limitation by ensuring such scripts are properly executed across SPA websites, making AdGuard even more flexible for advanced customization options. This enhancement also allows us to confidently recommend useful tools like the SponsorBlock userscript, which automatically skips sponsored segments in YouTube videos. To try it out:

• Go to https://mchangrh.github.io/sb.js/.
• Click Generate link.
• Copy the link that appears.
• Open AdGuard and go to Extensions → Add extension → Import from file or URL.
• Paste the copied link and confirm.

AdGuard is now in the Microsoft Store

You can now download AdGuard directly from the Microsoft Store, making it quick and secure to install, update, and manage alongside your other apps. Subscriptions and payments are still handled directly through AdGuard’s website, ensuring flexibility and full control over your license. Product updates for builds downloaded from the Microsoft Store will work the same way as in the regular builds. In other words, the store version is simply a new distribution channel, and the update process remains unchanged.

Support for Comet browser

We’ve added full compatibility for Perplexity’s Comet browser. Now you can now enjoy the same reliable ad blocking and privacy protection in Comet as you do in other supported browsers.

Changelog

Improvements

• Added Perplexity Comet to the list of supported browsers
• Added a warning when userscripts require modifying the CSP

Fixes

• The option “Exclude Wi-Fi SSID from the DNS filtering” does not work
• Microsoft Recall is enabled by default on Windows 10 Pro 22H2
• User rules counter appears at app’s launch
• Active tabs in the Filtering log are not visually highlighted in dark theme
• False “Error” status is shown during update check despite filters being updated successfully
• The filter version and the date information are not shown in Custom filters

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.6.20

CoreLibs (Filtering engine)

• CoreLibs updated to v1.19.34

Improvements

• Added wildcard and regexp support to the $app modifier
• Added support for the ALPS extension

Fixes

• Content-type modifiers cannot be used with the $urltransform modifier
• XHR timeout with “immersivetranslate” userscript
• Filtering is disabled because it may affect websites’ performance
• Some extensions stopped working after updating to v2.17
• $removeparam does not work in pair with $domain

Scriptlets (JavaScript enhancement for filtering rules)

• Scriptlets updated to v2.2.10

Improvements

• Added new scriptlet — trusted-replace-argument
• Added support for uBO arguments for href-sanitizer

Fixes

• prevent-element-src-loading — TrustedScriptURL is not defined in Firefox
• trusted-replace-node-text — some quotes are incorrectly escaped
• Scriptlets compilation error in Safari 15 due to unsupported regex
• trusted-set-cookie-reload — infinite reload for constantly changing values

Original source Report a problem

Here’s an additional technical update following the previous one. In it, we’ve fixed bugs and kept working on the app stability.

Changelog

Fixes

• Pages on Facebook don’t load fully when AdGuard and ESET are running simultaneously
• The app keeps crashing after updating to the latest version 7.21
• Rules are loading strangely at app startup

CoreLibs (Filtering engine)

Fixes

• CoreLibs updated to v1.18.34

Scriptlets (JavaScript enhancement for filtering rules)

Fixes

• Scriptlets updated to v2.2.8

Fixes

• trusted-set-cookie-reload — infinite reload for constantly changing values

Original source Report a problem

Along with the usual bug fixes, this version brings something new for those using Microsoft’s latest Copilot+ PCs. The Tracking protection section in AdGuard for Windows now includes an option Disable Windows Recall. Why is it needed?

This feature blocks Recall, a tool that periodically takes screenshots and stores them locally, so you can search through your past activity like a timeline.
Microsoft claims it’s private enough: it’s off by default, requires Windows Hello authentication, avoids collecting sensitive data like credit card numbers or ID documents, and encrypts all stored data.
But for AdGuard, that’s not enough. Screenshots still capture what’s on your screen — and not everything that’s private can be reliably filtered out. For example, a chat window, a partial account number, or something as simple as your to-do list could be saved without your knowing.
While Copilot+ PCs are still new and not widely used yet, they’ll likely become the new norm soon enough. AdGuard is ready to protect your privacy even before that happens.
To stop Windows from capturing your screen activity, open Settings and enable Tracking Protection — Disable Windows Recall will be enabled automatically.

Changelog

Fixes

• A blank update snack briefly appears after the UI starts
• Some filters don’t change their status to “Up to date” after manual updating
• The search line in the rule editor has an unnecessary length limit
• The AdGuard VPN icon doesn’t appear in Settings right after enabling Show AdGuard VPN in Settings
• Empty directories are accumulated in %AppData% after program updates
• New rules are not applied immediately after a filter update
• Statistics aren’t reset immediately after clicking Reset statistics
• Ads in the Start menu are not blocked when Disable Windows OS ads is enabled
• Problems with importing settings from the link
• The “Adguard Popup Blocker (Beta)” userscript does not load properly
• Manual filter update does not work on v8.0 Nightly
• AdGuard does not launch after updating to v7.21 Beta
• AdGuard causes BSODs
• Default date is shown in the empty User rules filter
• Filters are still updated when auto-update is turned off
• App consumes too much memory and CPU
• App UI does not open on v7.20.3

CoreLibs (Filtering engine)

• CoreLibs updated to v1.18.27

Fixes

• When CoreLibs runs in HTTP proxy mode with an MTU smaller than the ClientHello size, traffic fragments and bypasses filtering
• Long processing time of large HTML

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.6.8

Improvements

• Added a public method for detecting upstream protocol

Original source Report a problem