7.14 RC

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

AdGuard for Windows 7.14 release candidate is now available! It works even better now that we have made some improvements and fixed a bug. Look out for the official release version soon!

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.14 beta 1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

In this beta version, we have improved the efficiency and compatibility of our app by updating the WFP and TDI drivers. We have also redesigned the tray icons to give them a fresh new look. Finally, we have fixed some bugs and updated Corelibs.

Changelog

Features

• Finished translating Advanced settings to Russian #4704

Fixes

• The CPU usage is high when using AdGuard VPN in Selective mode with Ad Blocker and system DNS enabled #4750
• Incorrect detection of filtered apps when Browser Assistant is used #4680
• An incorrect rule is suggested when attempting to unblock Stealth Mode for a request #4675
• Unnecessary filter localhost notification when connecting to AdGuard VPN #4687
• The context menu theme for Filtering log does not change when switching the app theme #4628

Design

• Updated the uninstaller icon #4599
• Improved the settings icon in the Filtering log to appear when filtering criteria are set #4656

Versions

• Updated CoreLibs to v1.11.117 #4755

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.13.2

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

In this release we’ve fixed the Blue Screen of Death (BSoD) error that occurred on some devices and updated CoreLibs.

Changelog

Fixes

• The processUdpPacket causes BSoD #4733

Versions

• Updated CoreLibs to v1.11.114 #4734

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.13.1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

In this release we’ve fixed a few bugs that crept into the last version, including compatibility issues with NordVPN and Cloudflare WARP, and BSOD appearance issue. And of course we didn't leave out the CoreLibs and DnsLibs updates either.

Changelog

Fixes

• Cloudflare WARP doesn’t work when AdGuard’s DNS Module is enabled #4692
• The adgnetworkwfpdrv.sys caused BSOD #4691
• Nord VPN interferes with AdGuard if DNS module is enabled #4673
• AdGuard blocks access to domains if the Use Encrypted Client Hello setting is enabled and AdGuard VPN Browser Extension is running #1751

Versions

• Updated CoreLibs to v1.11.111 #4717
• Updated DnsLibs to v2.1.44 #4710

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.13

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

As spring arrives, AdGuard for Windows unveils its latest release, complete with numerous new features and improvements.

Experimental Encrypted ClientHello support

Notably, the addition of experimental support for Encrypted ClientHello (ECH) is worth mentioning. This new technology fully encrypts HTTPS connections, concealing server names you are connecting to from ISPs and ensuring complete privacy.

So that you can benefit from it, we’ve added the Use Encrypted ClientHello feature to the Advanced settings section and enabled DNS protection by default for all users.

Note that the Use Encrypted ClientHello feature can only work with the low-level Block ECH setting disabled and DNS protection enabled. The thing is that ECH relies on data obtained through DNS, so in order for AdGuard to receive this data and enable ECH globally for users, DNS filtering is necessary.

For Encrypted ClientHello technology to work, it must be supported on both client and server sides. Today, ECH support is implemented in a limited number of applications. Chrome and Firefox, for example, are in the process of adding it. Here we have no choice but to wait. But thanks to AdGuard, ECH support will automatically work in all apps and browsers on your device.

To check whether ECH is working, you can:

1. Go to https://crypto.cloudflare.com/cdn-cgi/trace/ and see if it says sni=encrypted.

2. Go to https://defo.ie/ech-check.php and check if it says SSL_ECH_STATUS: success.

As the Use Encrypted ClientHello feature is experimental, it may also lower your browsing speed a bit. But, we're currently working on solving this issue.

New Advanced settings

We’ve also added 16 more features to the Advanced settings section. A detailed description of each feature can be found in our Knowledge base. Here we’ll only give their names.

All new advanced features can be divided into six groups:

• Anti DPI options allow to modify packets at a low level during filtering to prevent tracking via deep packet inspection

  • Adjust size of fragmentation of initial TLS packet
  • Add an extra space to the plain HTTP request
  • Plain HTTP request fragment size

• Keepalive settings allow to configure settings to work with keepalive connections

  • Enable TCP keepalive
  • TCP keepalive interval
  • TCP keepalive timeout

• Filtering exclusion settings allow to exclude both Wi-Fi networks and particular subnets (specified in the CIDR notation) from DNS filtering

  • Exclude specified IP ranges from filtering
  • IP ranges excluded from filtering
  • Exclude specified Wi-Fi network names (SSID) from DNS filtering

• DNS-related options allow to fine-tune DNS settings

  • Use fallback DNS upstreams
  • Use HTTP/3 for DNS-over-HTTPS
  • Query DNS upstreams in parallel
  • Always respond to failed DNS queries

• Certificate security options allow to check certificates of websites and web services

  • Check websites' certificate transparency
  • Enable asynchronous OCSP SSL/TLS certificate revocation checks

• Enable filtering at system start-up. Now by default, AdGuard for Windows does not filter traffic after OS startup if the option Launch AdGuard at system start-up is disabled. If you want filtering to be performed even if AdGuard is not launched, you should enable this option.

Note that before v7.12 the AdGuard's service started in filtering mode by default (even if the Launch AdGuard at system start-up was disabled). If you were satisfied with the old behavior, enable this option.

What else? Aside from the regular CoreLibs and DnsLibs updates, we’ve updated WFP and TDI drivers and ExtendedCSS. We’ve also allowed to disable the Filter localhost advanced feature. But be aware that disabling this feature will prevent AdGuard Ad Blocker and AdGuard VPN from working simultaneously.

Changelog

Features

• Added an option to disable DNS filtering on selected Wi-Fi networks #4578

• Added an option to disable the Filter localhost advanced setting if AdGuard VPN is also enabled #4586

• Implemented the newest TLD-to-locale mappings from the AdGuard Browser Extension repo #4620

• SafeVisit was added to the list of filtered applications #4618

• When the default settings for displaying queries in the Filtering log are changed, the filter icon is highlighted #4406

• Allowed the Ctrl + E combination to open the advanced filter editor of the currently selected DNS filter #4330

• AdGuard now backs up UI settings 4404

• Added an option to operate the dialog boxes using the Enter button #4526

Fixes

• AdGuard hangs after resuming from hibernation #4565
• AdGuard does not automatically import CA for Firefox #4595
• AdGuard's certificate is not deleted from the system certificate store after removing the app #4610
• After the system starts, the message The app can't reach AdGuard servers appears #4590
• WCF communication breaks after resuming from hibernation #4551
• Imperfections in the installer's dark theme #4584
• The filter editor reopens instead of focusing once the filter editor button is clicked more than once #4619
• A DNS server or filter cannot be added via the Add to AdGuard button if Parental Control is enabled and a password is set #4272
• Not possible to exit the advanced DNS filter editor by clicking the Esc button #4329
• Once the DNS Filter Editor is opened, clicking the down arrow selects not the User rules section, but the filter below it. #4333
• The up/down arrow keys do not work correctly in the DNS Filter Editor after certain actions #4362
• When attempting to create a custom filter with an already used name, a notification Error while processing the custom filter appears
  #4437
• If the filter rule editor is already open, clicking the Edit button in the User rules will bring up a window for editing the previously opened filter #4438
• With filtering disabled for an app, the browser assistant continues working as if filtering was not disabled #4379
• Incorrect behavior of the Disable protection for 30 seconds feature after enabling or disabling protection #4535
• AdGuard doesn't filter the Craving Explorer browser #4544
• If you exit AdGuard and open its settings from Assistant while the service is running, AdGuard won't open #4556
• DNS filter rules are not applied after network shutdown #4588
• NordVPN interferes with the work of AdGuard if AdGuard’s DNS module is enabled #4673
• Upon exiting AdGuard, the Assistant indicates that AdGuard is not installed or misconfigured #4663
• Incorrect translation in the updater window #4640
• Disabling the Enable traffic filtering option does not stop filtering #4657
• The path modifier does not work on yandex.ru/images #1738
• The $jsonprune modifier can’t handle jsonp #1717
• Filtering does not work on websites with dot at the end #1741
• In some cases filtering doesn’t work on Google-related websites (e.g. youtube.com) #4480
• AdGuard Browser Assistant doesn't work in Chrome 113 #4693

Important for filter maintainers

Features

• The jsonprune, badfilter, `r...

7.13 RC

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Before a big release, it's a good idea to double-check everything and get rid of even the smallest problems. That's why today we're launching a release candidate of AdGuard v7.13 for Windows.

We’ve updated CoreLibs and DnsLibs, fixed a few bugs, including the compatibility issue with NordVPN, and improved the Browser Assistant.

Changelog

Fixes

• NordVPN interferes with the work of AdGuard if AdGuard’s DNS module is enabled #4673
• Upon exiting AdGuard, the Assistant indicates that AdGuard is not installed or misconfigured #4663
• Incorrect translation in the updater window #4640
• Disabling the Enable traffic filtering option does not stop filtering #4657
• The path modifier does not work on yandex.ru/images #1738
• The $jsonprune modifier can’t handle jsonp #1717
• Filtering does not work on websites with dot at the end #1741
• In some cases filtering doesn’t work on Google-related websites (e.g. youtube.com) #4480

Versions

• CoreLibs updated to v1.11.86 #4678
• DnsLibs updated to v2.1.37 #4686

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.13 beta 2

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

What time is it? It’s time for the second beta of AdGuard v7.13 for Windows! You won't see such a huge changelog here as you did in the What time is it? It’s time for the second beta of AdGuard v7.13 for Windows! You won't see such a huge changelog here as you did in the first beta. Nevertheless, the changes made are good enough to draw your attention.

DNS protection is now enabled by default for both new and old users. Previously, this was done only for newcomers. Once you run AdGuard for Windows after a clean installation, DNS protection will be turned on with the system DNS server and AdGuard DNS filter enabled. The same occurs if you update the app with the DNS module disabled. But nothing will change if you update an installed app with the DNS module enabled and configured.

We’ve also made some bug fixes, updated CoreLibs and DnsLibs to improve the app’s performance.

Changelog

Versions

CoreLibs

• Updated CoreLibs to v1.11.69 #4655
• HTTPS filtration breaks the trading.finam.ru website #1724
• The elearning.ual.pt website does not open with the Protect from DPI option enabled #4451

DnsLibs

• Updated DnsLibs to v2.1.27 #4639

Scriplets

• Updated Scriplets to v1.9.1
• Added a new m3u-prune scriptlet #277
• Added more possible values in the set-attr scriptlet
  #283
• Fixed compatibility for the noopcss redirect #299
• Improved adjust-setTimeout and adjust-setInterval scriptlets #262
• Improved json-prune scriptlet #282
• Fixed error in prevent-element-src-loading #270
• Fixed xml-prune-related errors #289

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.13 beta 1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

There are many changes and bug fixes in this update, but first we would like to draw your attention to a bunch of new features implemented in the Advanced settings.

We’ve added as many as 17 features which can be divided into 6 groups:

• Anti DPI options allow low level modifications to be made to packets during filtering to avoid deep packet inspection
• Keep alive settings allow to configure settings to work with keep-alive connections
• Filtering exclusion settings allow excluding both Wi-Fi networks and particular subnets (specified in CIDR notation) from DNS filtering
• Application management option allows to enable filtering even if the app is not launched. The point is that in v7.12 we have changed the behavior of the AdGuardSvc.exe service so that when the service starts automatically once starting OS, it does not filter traffic but stays in a "waiting" state. But we’ve left the option to let AdGuard work "as before" by enabling this option
• DNS-related options allow to fine-tune the DNS settings
• Certificate security options allows checking websites and web services certificates by various criteria

What else? Aside from the regular CoreLibs and DnsLibs updates, we’ve updated WFP and TDI drivers and ExtendedCSS. We’ve also allowed to disable the Filter localhost advanced feature. But be aware that disabling this feature will prevent AdGuard Ad Blocker and AdGuard VPN from working simultaneously in compatibility mode.

Changelog

Functionality

• Added an option to disable DNS filtering on selected Wi-Fi networks #4578
• Added an option to disable the Filter localhost advanced setting if AdGuard VPN is also enabled #4586
• Implemented the newest TLD-to-locale mappings from the AdGuard Browser Extension repo #4620
• SafeVisit was added to the list of filtered applications #4618
• When the default settings for displaying queries in the Filtering log are changed, the filter icon is highlighted #4406
• Allowed the Ctrl+E combination to open the advanced filter editor of the currently selected DNS filter #4330
• AdGuard now backs up UI settings 4404
• Added an option to operate the dialog boxes using the Enter button#4526
• jsonprune, badfilter, removeheader and hls applied rules are displayed in the Filtering log #4536

Fixes

• AdGuard hangs after resuming from hibernation #4565
• AdGuard does not automatically import CA for Firefox #4595
• AdGuard's certificate is not deleted from the system certificate store after removing the app #4610
• After the system starts, the message The app can't reach AdGuard servers appears #4590
• WCF communication breaks after resuming from hibernation #4551
• Imperfections in the installer's dark theme #4584
• The filter editor reopens instead of focusing once the filter editor button is clicked more than once #4619
• A DNS server or filter cannot be added via the Add to AdGuard button if Parental Control is enabled and a password is set #4272
• Not possible to exit the advanced DNS filter editor by clicking the Esc button #4329
• Once the DNS Filter Editor is opened, clicking the down arrow selects not the User rules section, but the filter below it. #4333
• The up/down arrow keys do not work correctly in the DNS Filter Editor after certain actions #4362
• When attempting to create a custom filter with already used name, a notification Error while processing the custom filter appears
  #4437
• If the filter rules editor is already open, clicking on the Edit button in the User rules will bring up a window for editing the previously opened filter #4438
• With filtering disabled for an app, the browser assistant continues working as if filtering was not disabled #4379
• Cannot add a new user rule via the plus icon or by clicking on an empty line 4519
• Incorrect behavior of the Disable protection for 30 seconds feature after on/off the protection #4535
• AdGuard doesn't filter the Craving Explorer browser #4544
• If you exit AdGuard and open settings from Assistant while the service is running, AdGuard won't open #4556
• DNS filter rules are not applied after network shutdown #4588

Versions

CoreLibs

• Updated CoreLibs to v1.11.59 4630

DnsLibs

• Updated DnsLibs to v2.1.26 4629
• Added tplinkextender.net to fallback domains #183

ExtendedCSS

• Updated ExtendedCSS to v2.0.51
• Changed IAffectedElement – make content optional #163

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.12

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Two most important changes in this release: protection is turned on and off faster and DNS protection is now enabled by default. We’ve also fixed some bugs, updated CoreLibs and DnsLibs, and improved the WFP and TDI network drivers.

Protection is turned on and off faster

We’ve significantly reworked everything “under the hood”, thus improving the app performance: protection is now enabled, disabled, and reloaded much faster. Previously, because of the long startup and restart of the protection, the implementation of rules and other protection features could be delayed or could even cause a web resource to “leak” past the protection. Some connections could remain unfiltered. And after all, it was very annoying for the user to watch the long startup of the app. Starting with this version, it won’t happen again.

DNS protection is enabled by default

Now, if you have just installed AdGuard, DNS protection is automatically turned on. By default, the ISP's DNS server is used, and for security, AdGuard DNS filter is enabled: ads, trackers, and requests for malicious domains will be automatically blocked. To increase security, you can always select a DNS server from the list or add a custom one (for example, a private AdGuard DNS server) via Settings → DNS protection.
DNS filtering allows AdGuard to catch ads and trackers even before the browser tries to connect to the ad server. So this update has also helped us improve the speed and quality of ad blocking. On top of that, DNS protection makes blocking “hidden” trackers more effective.

Changelog

Enhancement

• DNS protection is enabled by default, the DNS server of the ISP is used #4534

Added

• The option to filter traffic at system start-up without launching the app #4454
• PIX-LINK router/repeater domains to fallback domains #170
• Support for Catsxp Browser #4326
• An option to delete installation logs when reinstalling the app #4493
• Dark theme for the installer app 3048

Fixed

• AdGuard doesn’t start after rebooting #4502
• AdGuard freezes after filter update #4456
• If “Blocked” is selected in the filtering log, all requests are shown #4525
• The app doesn't update automatically in the background in Windows 7 #4494
• Unable to install userscripts that include @ in the link #4397
• Metadata updating error for HaGeZi DynDNS Blocklist #4475
• The main window opens at system startup despite checkbox is unchecked #4546
• Filtering and userscripts do not work with Norton 360 installed #1712
• Compatibility issue for the google-ima3 redirect #272
• Compatibility issue between prevent-addEventListener and userscripts #271
• Issue with isEmptyObject() #268
• Error when updating/reinstalling the AdGuard Popup Blocker userscript #4574

Updated

• CoreLibs to v1.10.189 #4563
• DnsLibs to v2.0.75 #4562
• Scriptlets to v1.7.20

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.12 RC

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

​This release candidate outlines important changes that will soon appear in the release. One of them is that protection gets enabled and disabled faster. Another one is that DNS protection is now enabled by default.

DNS protection is enabled by default

Now, if you have just installed AdGuard, DNS protection is automatically turned on. By default the ISP's DNS server is used, and for security, AdGuard DNS filter is enabled: ads, trackers, and requests for malicious domains will be automatically blocked. You can always select a DNS-server from the list or add a custom one via Settings > DNS-protection.

We’ve also fixed some bugs and updated CoreLibs and DnsLibs.

Changelog

Enhancement

• DNS protection is enabled by default, the DNS server of the ISP is used #4534

Added

• The option to filter traffic at system start-up without launching the app #4454
• PIX-LINK router/repeater domains to fallback domains #170

Fixed

• AdGuard won't start with System DNS and no Internet connection 4569
• If “Blocked” is selected in the filtering log, all requests are shown #4525
• The app doesn't update automatically in the background in Windows 7 (finalized) #4494
• Unable to install userscripts that include @ in the link #4397
• Metadata updating error for HaGeZi DynDNS Blocklist #4475
• Filtering and userscripts do not work with Norton 360 installed #1712

Updated

• CoreLibs to v1.10.189 #4563
• DnsLibs to v2.0.75 #4562

Upgraded Scriptlets to v1.7.20

Fixed

• Compatibility issue for the google-ima3 redirect #272
• Compatibility issue between prevent-addEventListener and userscripts #271
• Issue with isEmptyObject() #268

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel