AdGuard for Windows

AdGuard is a unique desktop program that has all the necessary features for the best web experience. The software combines the world's most advanced ad blocker for Windows, a whole privacy protection module, and a parental control tool — all working in any browser or app.
By downloading the program you accept the terms of the License agreement
Recent versions

This version makes a strong accent on the Networking issues. This doesn’t mean everything else was abandoned, on the contrary, there’s been a lot of ad blocking- and UI-related fixes and improvements, just the network-related fixes happened to be the most important ones.

[Fixed] Unrelated TCP connections get reset when starting AdGuard service #2291

AdGuard needs to reset connections when it starts/restarts its service in order to properly filter them. What AdGuard doesn’t have to do is to reset connections that it is not going to filter anyway. So from now on, it won’t do it, as simple as that.

[Fixed] Avast Free prevents AdGuard from suppressing QUIC #2310

The current way of whitelisting apps from filtering for WFP driver has been extended to TDI driver. It allows to avoid compatibility issues with other software, especially with antivirus software.

[Improved] TLS version has been upgraded #2337

Up to this moment we were using a draft of TLS 1.3 technology ([#2155](, as we always want to be at the cutting edge. Now, as TLS 1.3 standard was officially accepted by IETF, we are happy to say that AdGuard supports the most modern encrypting standards.

[Improved] Popup Blocker has been updated to v2.5 #2295

Popup Blocker is an extension (userscript) that is added to AdGuard by default. As it’s clear from its name, it helps block various popup windows (most of which are all kinds of ads). It’s been around forever, but the new version for the first time features its own UI accessable from “Extensions” settings tab. You can whitelist websites there or disable notifications for certain websites. The blocking capabilities have been improved too, of course.

[Changed] TLS 1.2 is used by default if Avast is detected #2368

As we’ve said earlier, TLS 1.3 is the current standard, but some antiviruses still use v1.2, notably Avast. We would like to completely switch to v1.3 but have to take this into consideration.

[Fixed] Application update resets Assistant settings and restores deleted extensions #2365

There won’t be enough fingers combined on hands of all people in our office to count the number of times users complained about this issue. One of our current priorities is to make the process of updating AdGuard as smooth as possible, and certainly preserving users’ settings is a big step in that direction.

Ad blocking

  • [Fixed] Duplicate EV certificate messages #2282
  • [Fixed] Twitch desktop app is not filtered #2289
  • [Fixed] PopupBlocker is not updated alongside AG update #2354
  • [Improved] Popup Blocker extension has been updated to v2.5.8 #2351
  • [Improved] Custom filters URL parsing #2280
  • [Improved] URL exclusion blocking rules are now created with important modifier by default #2305


  • [Changed] AdGuard now asks for a reboot after TDI driver update on Windows 7 #2364
  • [Fixed] Firefox 64-bit handshake issues with some domains #2347
  • [Fixed] QUIC v44 is not blocked properly #2335
  • [Improved] AdGuard now checks on installation if the TDI driver is not registered yet #2321


  • [Changed] Clickable area for “Close” button for AdGuard notification has been increased on Windows 7 #2319
  • [Changed] Highlighting color for the whitelisted requests in Filtering Log #2358
  • [Fixed] AdGuard remembers the last displayed settings tab after closing #2317
  • [Fixed] The Assistant icon appears in full screen mode on YouTube and Twitch #2309
  • [Fixed] Move the assistant icon back to the right corner #2314
  • [Fixed] “Hide your referer” checkbox state is not transmitted properly to web reporting tool #2286
  • [Fixed] Duplicate “Trial is expiring” message #2287
  • [Fixed] AdGuard fails to start service #2339
  • [Fixed] Crash on multiple tray clicks right after the installation #2340
  • [Fixed] “Service failure” tile and “Trial expired” tile appear simultaneously #2342
  • [Fixed] Crash upon opening the Filtering Log #2346
  • [Fixed] Update AG icon to high resolution version #2341
  • [Improved] Suppress the Alt-Svc header #2343


  • [Fixed] AdguardSvc process memory leak #2114
  • [Fixed] Crash while closing from tray #2252
  • [Fixed] Crash after auto-update on the application startup on Windows 7 #2290
  • [Fixed] An error while parsing the userscript metadata #2311
  • [Improved] A privacy-friendly protocol is now used for the parental control web service #2316
  • [Improved] Localizations have been updated, new languages have been added (Slovenian, Czech, Belarusian) #2361

While we are still polishing CoreLibs and are not ready to implement it just yet, we can sweeten the waiting with this new release. New "Nightly" update channel, added TLS1.3 support, improved performance and many more other changes.

[Added] Nightly update channel

The concept of a “Nightly” build is very simple. It literally means “a build that is released at the end of every day”, hence “nightly”. In reality, it may not happen every single day, but rather every 3 or 4 days, but the idea is there. All the latest changes made by developers will be included in the nightly build (yes, including possible bugs — be prepared!). If you feel that beta is not enough for you, and you need to be a step ahead of the rest, this is the choice for you. Just go to AdGuard settings and switch to Nightly update channel.

[Added] TLS1.3 Support (draft 28) #2155

TLS 1.3 is a new version of the cryptographic protocol used to encrypt messages sent via HTTP. It is faster, more secure and overall better than its predecessors. It has not been accepted by IETF as a standard yet, but it is only a matter of time. The process has already started, and we want to be at the forefront, and thus we have already added the TLS 1.3 (draft 28) support. As not everyone supports TLS1.3 yet, there can be problems on some websites potentially, so we added a new advanced setting to switch between TLS versions at will.

[Added] Option to subscribe to a filter by clicking a special link on a webpage #1945

Many filter developers put a special subscription link on their filters' homepage. Now AdGuard is able to detect these links when you click on them and will ask you if you'd like to subscribe to that filter right away. A minor thing, but it will save you just enough of extra clicks to be worthy.

[Added] A notice to inform about closed connections to websites with EV certificate #2015

Some websites have so-called EV (extended validation) certificates — basically, this means that the owner went through a very long and thorough process of validating their identity. In other words, these websites are generally the safest on the web. Filtering these websites is often extensive, as they rarely have ads anyway, but can sometimes lead to conflicts. AdGuard provides an option to disable filtering for such websites, and if it is enabled, a notification will inform you when you visit them for the first time. Clicking on the notification will allow to force filtering on the website anyway.

[Added] Stealth mode options applied to requests added to Filtering log #247

This is something a lot of aspiring filtering rules creators asked for. Knowing which Stealth Mode options affected this or that request is often crucial when working on a new rule. Now you can find it right in the Filtering log when you select a request. For sure, this sounds a little bit nerdy for an average user, but we try to take into account needs of all our users, casual and advanced alike.

[Changed] Default builder has been drastically reworked #1965

Basically, this is the change that caused the build size reduction that was advertised in the introduction. As the app accretes new features over the years and the code mounts up, this becomes more and more relevant. Thanks to this change, now we can add even more!

[Improved] Better support for visually impaired users #2068

AdGuard tries to provide the best online experience for all users alike, and visually impaired users are no exception. Starting with this version, AdGuard menus are much better suited to be read by NVDA Screen Reader and other screen reading programs.

[Improved] Filters update procedure's performance #2211

If you had the misfortune of a habit to update your filters often, you certainly noticed that it took quite a lot of time, as well as installing new filters. We addressed this problem, the situation should change drastically for the better now.

Ad Blocking

  • [Added] Option to subscribe to a filter by clicking a special link on a webpage #1945
  • [Fixed] "Block Flash" setting doesn't block Adobe Flash #2058
  • [Fixed] AdGuard cannot start protection after installing an update #2033
  • [Fixed] Cannot parse CSP from a meta tag #2207
  • [Fixed] HTML parser fails on #2221
  • [Fixed] Incorrect exception rule is created with Assistant #2265
  • [Fixed] Applications manually added to “filtered apps” get removed after an update #2195
  • [Improved] ExtendedCss has been updated to version 1.10 #2152


  • [Added] New approach to switching the update channel for default userscripts #2177
  • [Changed] Common API response format to use for XHR and WS APIs #2228
  • [Changed] HTTP headers with an empty value are not ignored from now on #2264
  • [Changed] Existing connections of filtered apps are closed now on AG startup #1977
  • [Changed] Problem with Github discontinuing TLS 1.0/1.1 support has been addressed #2098
  • [Changed] Symantec certificates have been deprecated #1634
  • [Changed] TDI, WFP drivers and libs have been updated #2089
  • [Fixed] CSP issue at #2151
  • [Fixed] Invalid HTTP response header prevents a website from opening #2188
  • [Fixed] and other online tests show as if AdGuard does not block WebRTC #1995
  • [Fixed] The issue with FIPS security error on license check #1033
  • [Improved] Method for detecting untrusted certificates has been improved in accordance with Chrome policy #2171


  • [Added] A notice to inform the user about closed connections to websites with EV certificate #2015
  • [Added] A "Beautifier" to the Filtering log and userscripts editor #1671
  • [Added] Stealth mode options applied to requests added to Filtering log #247
  • [Added] Swedish localization #2173
  • [Changed] Filtering log — long rules now collapse while in detailed mode #1845
  • [Changed] Several localizations updated #2088
  • [Changed] More details added to "AdGuard service" description #422
  • [Changed] Old links have been replaced with new ones #2102
  • [Changed] Parental control password is now hidden while typing #1816
  • [Changed] The first screen of the installer #2240
  • [Fixed] "Referer" field is now disabled unless "Hide Referer" is enabled #2025
  • [Fixed] AdGuard breaks encoding of a custom filter #2232
  • [Fixed] Can’t export/import configuration in Spanish localization #2018
  • [Fixed] Filter editor bug when pressing backspace #1439
  • [Fixed] Filter status change is not applied #2180
  • [Fixed] GUI hangs when enabling/disabling filter lists #2036
  • [Fixed] Incorrect "time updated" value is shown after filter remove/install #2220
  • [Fixed] Incorrect version of custom filter is displayed after an update #2206
  • [Fixed] Logo issue #2095
  • [Fixed] Parental control module doesn't save sensitivity level choice #2257
  • [Fixed] Toast notifications are broken in Windows Insider Preview #2278
  • [Fixed] Sometimes app crashes after adding an HTTPS exclusion #2024
  • [Fixed] The disclaimer in "About" window is hidden while updating #2165
  • [Fixed] The `~` symbol looks like `-` in Parental control settings #2219
  • [Fixed] Windows notification center is unavailable after first install #2268
  • [Improved] Handling of plural forms in localizations #2046


  • [Changed] Digital signature and description #2045
  • [Changed] Restrictions on the length of non-script and non-style elements have been removed #2237
  • [Changed] Suppress browser cache on a GM storage state change #2258
  • [Fixed] "Traditional Chinese" language file title #2190
  • [Fixed] `block_third_party_auth` parameter does not work #2073
  • [Fixed] App has crashed while being closed from tray #2019
  • [Fixed] Application update clears userscripts' storage even for the same update channel #2194
  • [Fixed] Cannot export settings in nightly builds #2204
  • [Fixed] Crash while closing from the tray #2252
  • [Fixed] MS Edge is not filtered in the Windows Insider Preview #2270
  • [Fixed] Tab and arrow keys can be used while in the password protected menu #2012
  • [Fixed] Userscript's `require` and `resources` parameters are not exported along with with its contents #2212
  • [Fixed] Windows notification center is unavailable #2181
  • [Fixed] Wrong folder is opened after the export operation is finished #2123
  • [Fixed] User script name being corrupted while export settings #2275
  • [Improved] `` can now be run as a "true" win64 process on 64-bit OS #1809
  • [Improved] Do not allow auto-switch update channel within the process of the upgrade #2269
  • [Improved] Traditional Chinese translations for filters have been updated #2245

Over the last weeks, we've received several reports about bugs that slithered in the latest release. They turned out to be both moderately important and relatively easy to fix, so we decided to release a new update off-schedule.

[Fixed] "Reinstall certificate" feature does not work in Firefox #2013

While not being the most important feature, the automatic certificate reinstall is more relevant for Firefox-based browsers than for any other ones. This fix eliminates the need to do it manually.


  • [Fixed] Connect to failed: ERR_CONNECTION_CLOSED #1991
  • [Fixed] Can't send pictures in desktop Viber app #1990


  • [Fixed] Fix the translation for the 'Get Premium' tile #1999
  • [Fixed] Baofeng video software compatibility issue #1993
  • [Fixed] Several userscripts compatibility issues #1986

Hello! The changelog this time is truly gigantic. Every time we thought we were going to release the current version, there was always something we felt was essential to fix, add or improve. How did it turn out?

Let's start with UI changes. Both Filtering log and Filter editor have been seriously redesigned. We need to say a big 'thank you' to everyone who has expressed his or her opinion because few changes depend as heavily on users' feedback as these.

[Changed] Filtering log rework #96

We know for certain that quite a few of our users are actively using Filtering log — both for creating new custom rules and generally knowing what's going on. So why not help them a bit? It has undergone a major renovation. New Filtering log overlaps with Filter editor a great bit, for example, you can create new rules and unblock blocked requests right therefrom.

There are more details to see about each request, too. The request details dialog window is very reminiscent of the Developer tools in Chrome browser. All in all, the new Filtering log is much more than a simple list of which requests are blocked and which are not.

[Changed] Filter editor rework #1293

Filter editor has also changed for the best. The addition of an 'Edit mode' allows replacing the data grid with a text area. This lets you copy/paste/delete many rules at once without having to bother with export/import.

Basic hotkeys are now available, which will speed up the process of working with the filter editor. There are many other quality of life changes, especially to the UI, which will draw your attention as soon as you launch the new version.

[Added] Integration with Windows 10 notifications center #1554

Many Windows 10 users find the Notification center to be helpful when it comes to tracking the activity of their apps. We have finally decided to take advantage of it and integrated AdGuard with the center. AdGuard has a surprisingly decent amount of various notifications. Just to name a few: notifications related to the license/trial period, automatic filter activations, new rules in User filter, Safebrowsing triggers, update checks results, etc. If you use Windows 10, you'll be able to find them all in one place now, thus making it much easier to keep up with what's going on with AdGuard.

[Changed] Network settings moved to a separate settings tab #1404

This one is rather straightforward. Previously, all network settings were crowding inside the 'General settings' tab making it harder to scroll up in down, searching for the one setting you need. Adding a separate first-level tab makes it easier to navigate through the app.

Assistant and other extensions

While not being an integral part of AdGuard for Windows, some extensions (or *userscripts*) have grown over time to become strongly associated with it. And we showed them some love!

AdGuard Assistant

A lot has been done in terms of improving AdGuard Assistant, and a lot more is planned for the future, so we decided to allocate it a separate, own GitHub repository:

By the way, you may notice that the 'Report website' button now leads to a whole new page. Basically, what you see is a web reporting tool that allows you to easily send us a report on anything from a missed ad to a false positive. More about this later.

What else is done already? The biggest change is the ability to drag the Assistant icon across the page and place it wherever you see fit. Moreover, AdGuard will memorize the position of the Assistant icon for each website separately, so you can really customize it according to your taste and preferences.

The Assistant interface overall has become smaller but retained full functionality compared to earlier versions. There is even one new feature: a switch for toggling the filtering on the website on and off. Previously, the Assistant wasn't shown on websites with disabled filtering, and you had to go to User filter to enable it back.

Oh, and we could use your help with translating the new Assistant. Did you know that anyone can volunteer as a translator? If you feel confident, head right here and find your native language. Don't forget to read through the translator's memo.

AdGuard PopupBlocker

[Added] AdGuard PopupBlocker extension v2.1 #1883

For quite a while now, AdGuard works as a userscript manager — you can install any script via AdGuard to use it in any browser. PopupBlocker has always been one of the 'native' userscripts that are installed by default, alongside AdGuard Assistant. Its purpose is clear — to block any unwanted pop-ups.

Previous version (v1.0) was functional but very little beyond that. We have completely redesigned the PopupBlocker. It now has advanced pop-up detection, compared to its predecessor and its alternatives, restores the initial click behavior and is invisible to other scripts. All in all, new PopupBlocker is a solid addition to your online protection suite.

By the way, it is available as a standalone script that can be used on its own with any other userscript manager. To find more information about PopupBlocker, visit its GitHub repository.

Reports web app

[Added] Integration with Reports Web App #1964

When it comes to keeping our filter lists updated, we owe our users a big one. Thanks to their timely reports of missed ads, false positives etc., AdGuard filters are always up-to-date. We want to make the process of reporting a website easy for users and informative for filter developers, that’s why we decided to integrate AdGuard for Windows with a special web reporting tool.

When you see any problem like missed ad or annoyance, click on the Assistant icon and choose “Report this website”. You will be taken to a new page and asked to fill in some information about your AdGuard settings and the nature of the problem. Good thing is that AdGuard pre-fills most of the fields automatically, so most of the job is already done for you :)

We hope this change will strengthen the feedback from our users and allow AdGuard filters to stay at the cutting edge of ad blocking technology.

Userscripts handling

[Changed] The way AdGuard handles userscripts #1714

A lot of effort has been put into improving (better to say, rethinking) the way AdGuard works with userscripts. This actually has two different aspects:

First, from now on, the communication between AdGuard and Assistant is based on WebSocket, which results in better performance. This is also perfectly applicable to AdGuard Browser extension, when it is working in the integration mode with AdGuard for Windows.

Second, we have taken a whole complex of measures that allow for any external userscripts that you install via AdGuard to show higher speed and execution stability.

Other important changes

[Added] Settings export/import #1405

A lot of users were asking for this, and finally we deliver. Now you can save your settings configuration into a file and then use it to set up AdGuard on another machine exactly how you prefer. Another implication of this is to quickly switch between different settings profiles without having to feverishly click through a dozen of tabs and checkboxes.

[Improved] A complete "Exit AdGuard" functionality was added #1509

Now users have a choice between closing AdGuard as they usually do, and closing it completely. That means closing the Windows service as well as UI, and when UI is getting started again, the service will start as well (you may be asked for the admin privileges, though).

[Added] An option to create custom filters not backed with a file #1669

In addition to the usual option of adding any list by URL or loading it from a local file, you can now create independent new filters from scratch. It is possible to create several such filters, give each of them their own name and fill with any rules. As a result, you can create a set of specified filters which can be separately enabled, disabled and edited.

Full changelog:

Ad Blocking

  • [Added] "Block third-party authorization header" Stealth Mode option #698
  • [Added] "Pure URL" functionality has been added to the Stealth Mode #356
  • [Added] `$app` modifier support #1396
  • [Added] $extension modifier #1542
  • [Added] An option to hide Java and Flash support #1064
  • [Changed] $webrtc rules are being ignored now #1776
  • [Changed] Synchronous XMLHttpRequest got rid of #1503
  • [Changed] The $important modifier is now applied to rules created by enabling/disabling filtering via Assistant #1924
  • [Changed] The behavior of the `~third-party` modifier #1564
  • [Changed] The range of $$ rules was increased #1464
  • [Changed] The script is not getting removed anymore if there is an $empty modifier in a rule #1789
  • [Changed] X-Requested-With is being used now to detect object-subrequest content type #1435
  • [Fixed] $replace rules are applied to HTTPS sites even when HTTPS filtering is disabled #1752
  • [Fixed] Adguard can not recognize :empty+div selector #1687
  • [Fixed] Automatic update for disabled filters #1445
  • [Fixed] Chromium is not filtered by default #1956
  • [Fixed] Content filtering exception rules behavior #1560
  • [Fixed] content-length duplicate header issue #1982
  • [Fixed] Cosmetic filters are not applied to the pages whitelisted by a `$document` exception anymore #1574
  • [Fixed] Duplicate filtering rules #1686
  • [Fixed] Error while parsing filtering rules of a particular type #1558
  • [Fixed] No filtering with TCP Fast Open enabled in Firefox Nightly #1867
  • [Fixed] Notification API isn't blocked properly #1706
  • [Improved] "ExtendedCss" module has been upgraded to v1.0.8 #1823
  • [Improved] GM_openInTab to handle data URLs in chrome #1971
  • [Improved] Multiple filters can be automatically enabled as language-specific at once now #1758
  • [Improved] The way `$network` modifier works #1645


  • [Added] Brotli support #1545
  • [Changed] HasConflictWithWpf flag values have been updated #1976
  • [Changed] SHA1 deprecation process is finished #1325
  • [Changed] WoSign and StartCom Certificates have been completely deprecated #1359
  • [Changed] XMLHttpRequest in the API is now protected #1434
  • [Fixed] A page is broken in IE #1591
  • [Fixed] AdGuard 6.2.390 on Windows 10 stops browsing until user kill the process #1901
  • [Fixed] AdGuard breaks local HTTPS connections #1896
  • [Fixed] Adguard cannot filter Edge HTTPS traffic when TCP Fast Open is turned ON #1093
  • [Fixed] Adguard cannot handle huge chunks properly #1772
  • [Fixed] Disabling HTTPS filtering breaks #1792
  • [Fixed] DNS is unreachable when using AdGuard #1918
  • [Fixed] Dropbox CSP messes with Adguard scripts #1678
  • [Fixed] HTTPS filtering on does not work sometimes #1902
  • [Fixed] Impossible to set custom IP in Stealth Mode #1828
  • [Fixed] Incorrect encoding was being used for the preview purposes #1741
  • [Fixed] Invalid gzip causes connection to hang #1817
  • [Fixed] Requests blocked when HTTPS filtering is disabled aren't present in the filtering log #1639
  • [Fixed] Several userscripts do not work when installed via Adguard #1562
  • [Fixed] SHA-1 intermediate issue #1702
  • [Fixed] SHA-1 intermediate issue #1702
  • [Fixed] Stealth mode settings may break filtering completely #1693
  • [Fixed] Warnings about synchronous requests #1688
  • [Fixed] Wrong ciphers order #1884
  • [Improved] Adguard doesn't recognize userscript updates when the version string is too long #1541
  • [Improved] Custom filter updates are being validated now #1765
  • [Improved] The strong key exchange within secure connections has been enforced #1728
  • [Improved] WebRTC detection #1831


  • [Added] "Adguard service" description #422
  • [Added] "Start time" and "Time" fields in the log records #1677
  • [Added] "Storage" and "Reinstall" buttons on “Extensions” screen #1893
  • [Added] A "Preview" feature for the blocked requests in Filtering Log #1695
  • [Added] A "Reset to defaults" button to the Extensions settings #1473
  • [Added] A loader is shown while Filter Editor is being prepared to be opened #1638
  • [Added] A switch to change the filter list display mode #574
  • [Added] A tooltip has been added to the "Support" window #1432
  • [Added] A warning in the "Filtered apps" section when Adguard is in the proxy mode #942
  • [Added] An option to disable all Adguard popup notifications #1630
  • [Added] An option to disable pop-up text in the Filter editor #1082
  • [Added] Filtering log export feature #1662
  • [Added] Filtering log records context menu #1668
  • [Added] Search function was added to the preview textarea #1694
  • [Changed] "Applied rules" appearance #1676
  • [Changed] All elements in Filter Editor UI are now shown as disabled until rules are fully loaded #1638
  • [Changed] Dutch localization was updated #1663
  • [Changed] Expiration date in the 'License' section has been made more distinguishable #674
  • [Changed] Filtering log scrolling behavior #1791
  • [Changed] Graying out the disabled modules has been uniformed across the app #1827
  • [Changed] Hebrew localization was updated #1548
  • [Changed] Interface has been optimized for screen readers #352
  • [Changed] License key symbols in the 'License' section are hidden now #627
  • [Changed] More details have been added to the "Adguard service" description #422
  • [Changed] Prevent closing the editor after editing a userscript #1632
  • [Changed] Program logo and "About" screen have been updated #1812
  • [Changed] Resizing the details pane was made more convenient #1675
  • [Changed] The EULA has been updated #1824
  • [Changed] The Filter Editor does not allow switching to other filters now when you're in the edit mode #1656
  • [Changed] The link to custom rules creation manual is added to the Filter editor #1410
  • [Changed] The maximum number of records in the Filtering Log was limited #1723
  • [Changed] UDP/TCP and HTTPS tunnel connections moved to the "Other" section of the filtering log #1670
  • [Changed] Update channel is now set to "Beta" if you install or update AdGuard to beta version #196
  • [Changed] Values in the details panel are now selectable #1667
  • [Fixed] "Connection" type records issues #1674
  • [Fixed] "Support" contact form is missing #1753
  • [Fixed] A “new line” symbol is added after copying a rule in Filter editor #1878
  • [Fixed] An incorrect message is shown upon checking for the updates w/o an Internet connection #1552
  • [Fixed] Can't use 0 as a value for self-destructing cookies setting #1642
  • [Fixed] Cancel button is missing #1899
  • [Fixed] Cannot close "validation error" dialog when editing a userscript #1894
  • [Fixed] Changing Advanced settings does not lead to network filtering restart #1800
  • [Fixed] Closing the right pane for a blocked request in Filtering Log does not highlight the entry #1729
  • [Fixed] Complete exit functionality bugs #1826
  • [Fixed] Crash after exiting Adguard via the tray menu #1697
  • [Fixed] Ctrl + Z does not work in any input field #1960
  • [Fixed] Default filters could have been deleted in filter editor #1786
  • [Fixed] Disabling HTTPS filtering leads to duplicate entries in the filtering log #1793
  • [Fixed] Facebook response preview is broken as preview tool does not support Brotli #1657
  • [Fixed] Filter editor bug #1969
  • [Fixed] Filtering log and Filter editor windows have different styles #1920
  • [Fixed] Filtering log search does not show UDP requests #1658
  • [Fixed] Filters content is being written to the application log #1703
  • [Fixed] GUI can't start after changing language #1664
  • [Fixed] Log export does not work #1900
  • [Fixed] New filtering log does not display removed elements #1660
  • [Fixed] Remote address bug in Filtering log #1852
  • [Fixed] Search does not work in userscript editor #1814
  • [Fixed] Search tooltip bug #1830
  • [Fixed] Stealth Mode tooltip bugs #1520
  • [Fixed] There was a sequence of actions that could lead to the removal of User filter #1787
  • [Fixed] UI crash when disabling the service with opened Filtering Log #1751
  • [Fixed] User filter is always empty when "Filter editor" is opened for the first time #1970
  • [Fixed] User Filters search doesn't work in 'advanced editor' mode #1821
  • [Fixed] User installed disabled filters are enabled after checking for updates #1692
  • [Improved] More filter editor tweaks and fixes #1750, #1778
  • [Improved] Search criteria in the filtering log were extended #1513
  • [Improved] Speed of searching in Filter Editor and Filtering Log was increased #1725
  • [Improved] Support for the PT-PT localization has been added #1640


  • [Added] Adguard French filter #1596
  • [Changed] 'Adblock Protector' added to the list of filters available by default #1584
  • [Changed] Bandizip app has been added to the list of apps filtered by default #1680
  • [Changed] Localizations have been updated
  • [Changed] Several browsers and apps were added to the list of apps filtered by default #1182, #1563
  • [Changed] Spotify app has been added to the list of apps filtered by default #1904
  • [Changed] Swing browser has been added to the list of apps filtered by default #1769
  • [Changed] The list of HTTPS exclusions has been updated
  • [Changed] Whale browser has been added to the list of apps filtered by default #1770
  • [Fixed] "Add application" tool in “Filtered Apps” can't detect installed Viber #1559
  • [Fixed] A generic hiding rule in third-party filter is not being applied #1696
  • [Fixed] Adguard crashes when you block a request in the filtering log #1868
  • [Fixed] Assistant settings are reset with the 3.0 -> 4.0 update #1738
  • [Fixed] Problematic userscript prevents others from working #1962
  • [Fixed] Several third-party userscripts compatibility issues
  • [Fixed] Stealth mode blocks Bitrix24 calls #1685
  • [Fixed] Typos #1825
  • [Fixed] Userscript is not injected #1958
  • [Improved] Data is now being preprocessed before the import/export #1691
  • [Improved] Log columns were reordered #1779
  • [Improved] The log file is now being validated before importing #1722
  • [Improved] Version check algorithm for filters added by URL #1431

This update might not be the biggest one, in a sense it doesn't feature any revolutionary additions or the immense number of changes. But it's surely a unique one, and it's because it is by far the most influenced by the user feedback. We sincerely thank everyone who has helped us!

It is super important for two big reasons, both concern networking/compatibility: we have *finally* fixed the compatibility issue with KIS/ESET and, also, we've fixed a certificate issue in modern Chrome versions (59+). Details below.

[Fixed] Compatibility with KIS/ESET #1565

Adguard used to have compatibility issues with such antivirus software like Kaspersky and ESET. Users had to seek for compromises: disabling SSL scanning in antivirus, disabling WFP driver or even HTTPS filtering in Adguard. The core of the problem was the WFP network driver incompatibility, and we had had plans to develop a new driver for what now seems like an eternity.

We'd already claimed to have this fixed in the previous releases, but things turned out to be more complicated. We've come through countless iterations, test builds, and driver updates, and now we are confident enough to say that this time the problem is fixed for real. No more BSODs and other funny stuff when you run Adguard alongside with KIS or ESET.

And again, we can't thank enough everyone who was willing to cope with raw test builds and provided invaluable feedback in order to help us make things right. Just look at the task - it is blowing up with comments. We are happy to have such users, you are awesome.

[Fixed] Compatibility with Chrome 59+ #1597

With big news which WFP driver compatibility fix is it could be easy to neglect other changes. And that would be so wrong! This fix, in particular, is of utmost importance. It ensures Adguard will run without problems on modern (v59+) Chrome versions. Otherwise, there would be troubles with Adguard certificate validation.


  • [Changed] The search criteria in the filtering log were extended #1513
  • [Changed] Connections are not allowed if DH1024 is in use #1616
  • [Changed] The default HTTPS exclusions list has been updated #1618
  • [Fixed] Adguard Service keeps downloading data after closing the browser #1599
  • [Fixed] An error encountered when adding a filter by URL #1583

UPD: hotfix update 6.1.314 brings a fix for the bug #1569, messing with filtering when HTTPS filtering is disabled.

It was quite a while since the last Adguard for Windows release. And there are other reasons for that apart from the Christmas/New Year holidays: we'd been extensively testing the new network driver before, finally, we felt ready to include it in the new release version. But what is there for me in this network driver, you might ask? Well, it fixes an old compatibility issue with several antivirus programs. For sure, there are other fixes and changes as well, and you will find the whole list below.

You can also find all relevant information about this release (and discuss it) in our blog.


[Improved] WFP driver was updated to fix compatibility issues with KIS and ESET #1497

Previously, it was not unusual at all that Adguard would have compatibility issues with some antiviruses, and KIS and ESET being the most common ones. The workarounds existed but were far from ideal - you had had to sacrifice some parts of functionality on either Adguard or antivirus side. With updated WFP driver these conflicts will be no more, allowing users to run Adguard alongside with KIS and ESET.

[Improved] The way we respond to HTTP protocol violation #1452

It would take too long to explain technical nuances, but effectively this fixes the problem some users might have come across before: when you try to open a page and it is downloaded as a file instead.

  • [Fixed] $popup rule bug #1504
  • [Fixed] QUIC protocol issue when KIS is installed #1482
  • [Fixed] HideUserSearch option breaks the 'maximize' button graphics #1536
  • [Fixed] 'Disable Fast Open' setting doesn't work in latest Insider Preview builds #1487
  • [Fixed] Several issues in Firefox with the default value of 'Hide you user-agent' setting #1493

Ad Blocking

  • [Added] $network basic rules modifier to solve the issue with loading ads through WebRTC #1297
  • [Changed] Extra Steam executables removed from the list of filtered apps #1468
  • [Fixed] Invalid executable for CentBrower #1453
  • [Fixed] $replace rules aren't applied to .m3u8 files content #1428
  • [Fixed] Regular expressions with $ aren't processed properly #1475
  • [Improved] Cosmetic exception rules compilation speed #1533


  • [Added] A new advanced settings property to change the injection method #1492
  • [Changed] Version history link in about section #1471
  • [Changed] Parental Control password protection is made separate for different Windows user accounts #1480


  • [Changed] HTTPS exceptions list is updated #1532
  • [Changed] Opera Neon browser added to the list of filtered apps #1495
  • [Changed] Orbitum browser added to the list of filtered apps #1467

This version should be considered as a revision of the Adguard for Windows 6.1 release. This is why you will not spot many 'major' changes - mostly bugfixes, small changes, improvements etc. More drastic changes will come eventually with 6.2 version.

Ad Blocking

[Added] $important modifier #1312

This new addition is an important one (no pun intended), but mostly relevant for creators of custom filter rules. With it's help you can give certain rules higher priority.

  • [Changed] Several apps and browsers added to the list of apps filtered by default #1230, #1236, #1274, #1280, #1344, #1347
  • [Fixed] Inconsistent $replace result #1358
  • [Fixed] Adguard now filters pages with Content-Type:application/xhtml #571
  • [Fixed] HTTPS exceptions do not cover subdomains #1317
  • [Fixed] $replace rule can now be applied along with the other rules #640
  • [Improved] Filters update check period is now customizable #941
  • [Improved] Adguard now can partially block encrypted ads without decrypting SSL protocol (if HTTPs filtering is disabled) #1233


  • [Changed] Switched to the DigiCert certificate #1268
  • [Changed] WoSign and StartCom certificates became unstrusted #1359
  • [Changed] Proxy mode will use IPv4 address when it is available from now on #1323
  • [Fixed] CSP is now handled in meta tags #797
  • [Fixed] Issue with invalid HTML #1222
  • [Fixed] "iframe" elements are not removed from the page code #1245
  • [Fixed] Adguard.Tools.exe heavy CPU load issue #1229
  • [Fixed] Opera dev ad blocker compatibility issue with Adguard Assistant #1173
  • [Fixed] Opera built-in VPN compatibility issue #1116
  • [Fixed] Certificate validity check order #1277
  • [Fixed] SSL exceptions aren't deleted on network API reinit #1304
  • [Fixed] Adguard code is injected into a non-HTML document #1316
  • [Fixed] WFP driver impacting DPC latency #1156
  • [Fixed] $empty modifier behaviour #1360
  • [Fixed] Stealth mode ignores $stealth exception #1362
  • [Fixed] Inability to apply inline style #1331
  • [Fixed] An empty 'style' tag is added even if there's no element hiding #1336
  • [Fixed] $replace modifier breaks content charset #1378
  • [Fixed] Adsbypasser and some other userscripts do not work properly #1363
  • [Fixed] "Enable safe search" function in Parental Control breaks Google #1383
  • [Fixed] Adguard doesn't filter HTTPs when Fiddler is switched on and in "decode https" mode #1372
  • [Fixed] Adding a URL to temporary HTTPs exceptions is suppressed now when connection is closed from the server side #1341
  • [Fixed] 'access-control-allow-origin' header console error #1381
  • [Improved] HTTPS is now used for safebrowsing service requests #1386
  • [Improved] Encrypted connection is used now with #1369
  • [Improved] Adguard styles are now protected from removing #1272
  • [Improved] Content type detection #1264
  • [Improved] Content injection algorithm was reworked #1099, #1305


[Changed] WOT extension is now disabled by default #1364

Recently, an article was posted in one of the popular technology blogs, claiming that Web of Trust is selling its users' browser history to third-parties. WoT extension is preinstalled in Adguard for Windows, and although it was developed by us and is not sending any of your data to WoT, we can not leave this without a reponse. For this reason we make WoT extension disabled by default in Adguard for Windows. You can read our official stance regarding these news in our blog.

  • [Changed] You can now completely remove WoT extension #1364
  • [Changed] Unnecessary text in 'Import rules' dialog window is removed #1349
  • [Fixed] Filter's name isn't copied with the rest of request details #1318
  • [Fixed] Button size issue on the last step of Adguard wizard #1352
  • [Fixed] Adguard crashes if you try to close UI while editing a filter rule #1258
  • [Fixed] $replace rule is shown as applied to images #1392


  • [Fixed] Deleted records from HTTPs exclusions are not restored on app update anymore #904

Many other minor fixes and changes. The full list can be found in descriptions to prior beta versions in our repository on GitHub.

Briefly about new Adguard for Windows version: Stealth Mode got new useful options, userscripts work better now, ad blocking became more advanced and our network drivers - more stable. All the details are below.

Stealth Mode

[Added] "Self destructing cookies" option in Stealth Mode #678

Previously Stealth Mode module provided only the option to completely block third-party cookies. Now you will not only have an ability to differ first- and third-party cookies, but also the ability to set the exact time which cookies will be kept alive for. Important note: you can still block cookies alltogether, just set the keep-alive time to '0'.

[Added] Added an option to block "Browser location API" #139

[Added] Added an option to block "Browser notifications API" #1121

Normally browsers may detect your location and use this information to prioritize specific search results or make other various suggestions based on it. With browser location API blocked this will be impossible.

Blocking browser notifications API feature works somewhat similar, but rather prevents browser from showing things like news or social media frames that pop-up in the corner of your browser.


[Improved] Content injection algorithm #1099

We completely redesigned content injection algorithm. First and foremost, this should solve issues with scripts that start when the page opens, resolve some of the known conflicts (AdsBypasser, YouTube+), and also optimize usage of scripts and ad blocker styles. Overall, a technical, but very important change.

[Added] Userscripts handling #1172

We adopted a new way of handling user.js (userscript) files. Now Adguard will automatically detect when user.js file was processed. If it is a valid userscript, Adguard will open a dialog window, offering user to install it. Of course, this setting will be optional and possible to turn off through settings.


[Added] Hebrew localization, Dutch localization #1076, #1063

We continue to make Adguard more easily accessible for users all over the world. This time we add two more new localizations and fix some mistakes in already existing ones.


[Improved] Network SDK was updated #1179

In reality, this implies many various fixes that concern our network drivers. It would be hard to list them all here, and most of them are rather technical anyway. For example, the WFP driver - Windows Defender compatibility issue was addressed.

Ad Blocking

[Added] Support for extended selectors #1225

This is a technical term, but what hides behind it? With extended selectors support, we can much more easily create some rules that were very, very hard to create earlier. Notably, this concerns rules required to block such things as 'Sponsored posts' on Facebook.

[Added] Extended CSS support

This is a very important addition in terms of future (and present) possibilities that it opens for ad blocking. Extended CSS is a module for applying CSS styles with extended selection properties. Basically, it means that we will be able to select and, therefore, block some elements that we would not be able to block otherwise. Currently we support following pseudo-classes: -ext-has (:has), -ext-contains (:contains), [-ext-matches-css (:matches-css).


Dozens of minor fixes and improvements.

A hotfix after last weeks release. Previously there turned out to be several problems, including router page loading problem and other. These bugs are fixed with this version.

  • [Fixed] Indefinite loading of router page #1042
  • [Fixed] Rare problem when Adguard crashes after clicking on tray menu icon #1045
  • [Fixed] Adguard will not crash any more if you switch tabs while have active search on 'Settings' screen #1043
  • [Fixed] Adguard now detects HTML correctly for all websites if there is an xml declaration at the document start #1011

Good news, everyone! We haven't seen any new bugs since the latest beta version, and it means nothing else but the new stable release is arriving. During the last couple of months that had passed since the 6.0 release we were able to track quite a lot of bugs and defects, which were crucial to fix. So we concentrated on them for a while. Finally, everything seems to be fixed and we are ready to turn on the autoupdate for all our users who still use Adgguard 5.10. We were looking forward to this moment! Even if you were already using Adguard 6 and you are not as excited by these news, you should be. This release means we can finally put all our efforts into implementing cool new features you might have or have not seen in our [roadmap]. In case you missed last beta releases and respective release notes, you can catch up and read about all the fixes and additions below. Most important of them, as usual, are described in detail.

UI changes

  • [Changed] Adguard uses native-style tray menu now #1006
  • [Changed] Adguard window is now opened with a single click on tray menu #1030
  • [Fixed] 'About' window content is not flickering anymore #954
  • [Fixed] Empty strings are now removed when importing user filter #973
  • [Fixed] Error previously encountered while installing a userstyle #934
  • [Improved] Proxy name validator now recognizes domain names and not only IP addresses #931

Ad Blocker

  • [Improved] Added $stealth modifier that disables Stealth Mode for the specified website #339 As we already mentioned in our blog, separate whitelist for Stealth Mode is on our roadmap. It is a much needed feature for anyone who actively uses Stealth Mode. We are not quite there yet, but we made a big step in the right direction by implementing $stealth modifier. It works similar to all other modifiers, just add it to any exception rule and it will disable Stealth Mode for that website specifically, even if the module itself is enabled. For example: @@||^$stealth You can find more information about rules formatting on our website: [](
  • [Changed] Facebook windows app added to default filtered apps list #974
  • [Changed] $replace rules should now have higher priority than other basic rules #1023
  • [Fixed] Adguard does not try to filter data: URLs any more #1007
  • [Fixed] $domain modifier now does work for blocking WebSocket connections #998
  • [Fixed] Adguard now doesn't ignore tag href attribute while constructing absolute URL #978
  • [Fixed] Error previously encountered while parsing a style tag with embedded svg #977
  • [Fixed] Language-specific filters are now detected properly from users keyboard layouts #401
  • [Improved] Adguard now can process websites names in punycode when adding them to HTTPS exclusions #962

Languages and Translations

  • [Added] Support for complex language codes #808 We have completely reworked applications localization system. This allowed us to significantly increase number of languages we can potentially support (this mostly concerns various dialects, alternative alphabets etc.).
  • [Added] Croatian language


  • [Improved] HTML content detection #855 Content type detection was significantly improved. This effectively means that Adguard will not interfere with those types of traffic which do not require filtering, decreasing the number of potential conflicts.
  • [Fixed] Web interface of TP-Link router is broken #844 Some of our users encountered problems with accessing TP-Link routers' interface with enabled Adguard. Upon investigating this issue we discovered a serious issue with WFP driver which resulted in problems with displaying some websites. As a result, we have improved communication with some specific web-servers.
  • [Added] Support for HTTP method REPORT #1020
  • [Fixed] Adguard can now detect HTML if there is an xml declaration at the document start #1011
  • [Fixed] ESET compatibility issue when Chrome browser would randomly hang #899
  • [Fixed] Data is now read to end after blocking a POST request #916
  • [Fixed] Issue with unexpected connection reset with TDI driver #1025


  • [Fixed] Blank dialog while updating from 5.10 to 6.0 #924
  • [Fixed] CMD window is no more shown on Adguard update #935
  • [Fixed] An issue when update errors were shown as valid updates in tray notification #993
  • [Fixed] Adguard now detects Chrome in 'Filtered apps' on Windows 10 insider build #972


  • #914, #927, #948, #946, #945, #944, #1014, #1029
  • For the full version history visit this page.
    Install AdGuard ad block for Windows and see the Internet as it was supposed to be — clean and safe.
    More on AdGuard
    We are always open to communication. You can leave feedback on AdGuard for Windows on our Forum.
    We have an open bug tracker, so feel free to report issues or simply check what we are working on at the moment.
    Have a question that is not answered on this page? Head to our Knowledgebase, as it is likely to be covered there.