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

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

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

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

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

Hotfix time! Our first patch targeted a critical bug, and now the second one brings some small improvements to v7.20. Think of it as the finishing touch: we’ve updated the libraries and the drivers, optimized the filter update system, fixed bugs, and addressed a CVE vulnerability.

Changelog

Fixes

• AdGuard doesn’t open automatically after the update
• !#if statement condition is not working
• AdGuard causes a BSOD related to the Microsoft driver netio.sys
• AdGuard import settings failed
• Some filters cannot be added in v7.20, although it was possible in v7.19
• Turning off User rules in the Ad blocking section turns off the User rules filter in the DNS section
• Legacy Browser Assistant can’t be enabled after update to v7.20

Corelibs (Filtering engine)

• Corelibs updated to v1.17.108

Original source

This hotfix, as well as the release before it, focuses on filters. Many users have reported a big issue: filters and extensions were gone after updating from the previous version. Rest assured, they are not gone permanently — we always create backups. If you’ve been affected by this issue, please follow the steps below to restore your settings:

• Open File Explorer and navigate to the path "%programdata%/adguard/backups".
• Find the backup zip file associated with the 7.19 version. It will be named something like adguard_settings_7.19... . Save this file somewhere.
• Uninstall AdGuard, but make sure to keep your settings (don’t check the box Delete settings).
• Go back to File Explorer and navigate to "%programdata%/adguard". Delete the FLM folder and the adguard.db file.
• From the zip file you saved in step 2, extract the adguard.db file and copy it to the "%programdata%/adguard" folder.
• Finally, install version 7.20.1. Your settings should be restored.

Changelog

Fixes

• Filters and extensions are gone after updating from v7.19 to v7.20

Original source

Filtering is the core of any ad blocker, and it’s the main focus of this release. We’ve introduced differential filter updates to ensure you always have the latest filters. Plus, we’ve made DNS filtering easier to customize by offering ready-to-use filters that can be added with just one click. And in other filtering-related news, we’ve revamped the screens you see for blocked websites so you can interact with them more.

Differential filter updates

Previously, even minor changes to a filter list required downloading the entire list again. This approach was inefficient, leading to excessive bandwidth usage, increased latency, and unnecessary server load.
Now, with differential updates, AdGuard downloads only changes to filter lists instead of the entire list. This reduces server load and speeds up the process. You don’t have to do anything — updates are applied automatically, so you always have the latest filters. And what does more filter updates mean? Yes,, more effective ad blocking.

One-click DNS filters

In the DNS Protection section, you’ve always been able to import filters to customize your DNS filtering. Now adding filters is even easier: simply select from pre-built, trusted filters — the same ones AdGuard DNS users know and love. Filters are grouped into categories for convenience:

• General: block ads and trackers
• Regional: target websites in specific languages
• Security: block phishing and other threats
• Other: cover special use cases that don’t fit the above

Blocking pages: now interactive

Chances are, you’ve seen one of our blocking screens before — whether due to a phishing threat, Parental Control, or a filtering rule. Previously, these pages were more like roadblocks. Now, they’re more like intersections where you have options.
For example, If AdGuard blocks a website due to phishing suspicion, but you’re sure it’s safe, you can let us know directly from the blocked page. You can also access our security check tool to get more details about the website.
A website blocked by a filtering rule? Just click “Add this website to the allowlist” and an unblocking rule will be generated automatically and added to User rules.
As with every new release, this one includes updated WFP and TDI drivers, along with updated filtering engines — CoreLibs and DnsLibs. What else is there to ask for? If there is — your input is welcome in our repository.
Heads-up: This version does not support Windows 7. If upgrading to a newer version of Windows isn’t possible, you can stay with AdGuard v7.19.

Changelog

Improvements

• Added support for Zen Browser

Fixes

• Excluding Wi-Fi SSID from the DNS filtering does not work
• Filters are reset when updating from 7.20 nightly 3 to nightly 4
• HTML requests are not displayed in the filtering log if there is a rule with the $generichide modifier
• “Image of the day” is blocked by Disable Windows OS ads
• Types of filters and some of their names are not translated
• The message “Settings were successfully imported” appears even though the import link was invalid and the settings were not imported
• The main window stays open when Windows starts
• When updating filters, the screen does not fit properly
• Can’t save a custom IP in Blocking mode for hosts rules
• The splash screen of the AdGuard app appears after the PC is restarted
• When importing settings by shared URL, DNS servers add to Recommended list, instead of Custom
• When adding a custom filter list, notification shows that some filters have been updated

CoreLibs (Filtering engine)

• CoreLibs updated to v1.17.94

Improvements

• Removed trust in GlobalTrust certificates
• Enable post-quantum cryptography when it’s used by the filtered app
• Implemented new blocking pages
• Provided the ability to add userscripts without specifying a resource
• Added safe search for so.com into Parental Control
• Allow HTTPS filtering with trusted self-signed certs

Fixes

• “Proceed anyway” button doesn’t work when website is blocked by rule with the $all modifier
• Access to function “GM_getValue” is not allowed
• AdGuard overrides User-Agent changes made by the browser, which reduces privacy
• On reddit.com, URL parameters with %24 are not removed
• “##+js(rmnt, #text, [...])” rule with non-ASCII UTF-8 characters is not converted

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.5.51

Scriptlets (JavaScript enhancement for filtering rules)

• Scriptlets updated to v2.1.4

Improvements

• trusted-click-element — check for containsText of all matched selectors

Fixes

• trusted-click-element — the element has been removed and then added again before it is clicked on
• trusted-set-cookie — cannot set cookie if name has __Secure- prefix

UserscriptsWrapper

• UserscriptsWrapper updated to v2.0.1

Original source

Rolling in like that quirky relative who always brings the best presents, here’s version v7.19 for you! With it, you can share your settings via link, enjoy fancy userstyles, log in in a new way, and say goodbye to nasty bugs.
Before you dive in, we have some important news: this is the last release to support Windows 7. Why? We use several libraries for our work, the latest versions of which no longer support Windows 7. And the latest versions are necessary — both for user safety and for the overall functionality of the app. If upgrading to a newer version of Windows isn’t possible, please stick with version 7.19.
Now, onto the features.

Sharing settings

We believe that sharing is caring, so we’ve introduced a new feature that lets you share your settings via a link. If you’ve got everything set up perfectly, just scan the QR code to transfer your settings to another device. Or share the link with friends — spread the love settings!

Adding style to your browsing

Want a dark theme on a website that doesn’t have one? With userstyles, it’s possible!
Userstyles are custom themes that allow you to change how web pages look in your browser without modifying their content. They work by adding CSS styles to the website’s existing styles.
To add a userstyle, go to Settings → Extensions → Add → Import from file or URL. Feeling creative? Click Add → Create userstyle. You can find ready-made userstyles online. Once you install one, just open your browser, and voilà — it’s all styled up.

Logging in a new way

Now, when you select Log in with email, you’ll be taken to a browser to sign in to the app and your AdGuard account. Not so convenient at first, but you can put a password manager to use — enable autocomplete in your browser and you won’t have to enter your login info every time. Plus, it makes it easier for us to maintain the service, which means we’ll be able to respond more quickly if something goes wrong.
You can also opt for one-time codes. We’ll send you a code to your email, and you’ll never have to worry about remembering your password again.

Last but not least

You know that list of settings on the left side of the app? Well, we’re updating their names to make it clearer what they actually do. So Stealth Mode becomes Tracking protection. Makes sense, since it doesn’t make you literally invisible, but it does protect you from being tracked.
Every new version comes with bug fixes, some bigger than others. Like the BSoD issue, which is quite annoying. We did our best to fix it, and with updated WFP and TDI network drivers, everything works as it should.
We also updated the Scriptlets, the DnsLibs, so you can count on quality filtering and clean, safe browsing.

Changelog

Improvements

• Added userstyles support
• Added support for the Floorp browser
• Updated translation of the Fanboy’s Annoyance List description

Fixes

• AdGuard causes a BSOD related to the Microsoft driver netio.sys
• AdGuard DNS filter doesn’t work after re-enabling the DNS module
• Dark theme missing in search bars for context menu
• Disable Windows OS ads feature appears in Windows 10
• Double-click doesn’t work in Blocklist and Allowlist
• Minor dark theme UI issue with scrollbar background in Filter Editor
• 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.16.44

Improvements

• Enable post-quantum cryptography when it’s used by the filtered app

Fixes

• AdGuard content script is blocked by CSP on uber.com
• GM_xmlhttpRequest doesn’t support the Referer header
• Impossible to log in at sony.de in Firefox when AdGuard is enabled

Scriptlets (JavaScript enhancement for filtering rules) updated to v1.11.27

Improvements

• Added allowed and denied values to set-local-storage-item
• Added line number support for inlineScript and injectedScript to abort-on-stack-trace
• Added checked and unchecked values to set cookie
• Added reload option to trusted-click-element

Fixes

• log-on-stack-trace — player did not work on deltabit.co

DnsLibs (DNS filtering engine) updated to v2.5.41
ContentScript updated to v2.0.6
UserscriptsWrapper updated to v1.2.24

Original source