7.17.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 patch, we’ve focused on addressing two critical issues. First, we have fixed a major bug that occurred in the filtering engine, CoreLibs. Second, after installing AdGuard v7.17 for Windows, the application would crash if you put the word in quotation marks in the Exclude app from filtering by entering the full path option. We’ve fixed it and also updated DnsLibs, along the way.

Changelog

Fixes

• Quotation marks in Exclude app from filtering option prevent AdGuard from working #5087

CoreLibs (Filtering engine)

• CoreLibs updated to v1.14.53 #5092

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.5.19 #5093

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.17

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.

Greetings, intrepid ad blocking explorers! Fasten your seatbelts, because AdGuard v7.17 for Windows is about to take you into a digital dimension where we have improved Encrypted ClientHello work and implemented on-the-fly DoH connection filtering. But one thing at a time.

In the new release, we updated CoreLibs, which brings us two important features.

Enhanced Encrypted ClientHello

AdGuard for Windows supports ECH as an experimental feature. It helps us to encrypt the very last unencrypted bit of information, thus improving your privacy level. We are working hard to resolve some technical issues so that it can become one of the default options for users. The updated CoreLibs is another step towards that goal.

On-the-fly DoH connection filtering

CoreLibs v1.14 also allows us to implement on-the-fly DoH connection filtering. Why is it so important? Previously, if you set up DoH in a browser but not in AdGuard, we had to filter requests directly in the browser and send them to the system DNS (unencrypted). This process lowered the level of security for such users. Now the situation is completely different. With on-the-fly DoH connection filtering, we can filter DNS requests in the browser without sending them to an unencrypted server.

We also made some minor fixes here and there, updated WFP and TDI drivers, as well as DnsLibs. Check out the massive changelog below and don’t forget to update!

Changelog

Improvements

• Added parsing for the # symbol #4666

Fixes

• Can’t start the protection when selecting the WFP network driver #5055
• Filter editor sometimes works incorrectly when editing a rule #5058
• Unable to start the protection after updating to v7.17 beta 3 #5060
• Setting up a custom DNS server is not always possible, fallback fails #5029
• The original installation path is changed during installation #4975
• The AdGuard directory is not removed from Program Files (x86) when updating to v7.16 x64 #4972
• Searching by type does not work in the Filtering log #4980
• Unable to start protection after updating to v7.17.0 Nightly 1 (4583) #5017
• AdguardSvc.exe is branching out into multiple threads #4874
• Certificate Info is being displayed twice #4964
• Filtered DNS requests are not displayed in the Filtering log after toggling network off/on #4941
• Time counter for filter updates doesn’t work #4974
• Enabling DNS Protection breaks the local Windows domain connection #4906
• Horizontal scrollbar in the DNS Filter Editor window does not work #4715
• Launch AdGuard at system start-up checkbox doesn’t respond after the first click #4965

CoreLibs (Filtering engine)

• CoreLibs updated to v1.14.52

Improvements

• Added an option to use | as a separator in $permissions #1850
• Added an ability to indicate if outbound proxy is used in the request processed event #1385
• Added support for passing host to outbound proxy #1386
• Added Firefox 121.0+ to the list of user agents that natively support :has() #1840

Fixes

• Cannot parse QUIC ClientHello split into two packets #1861
• VOT (voice over translation) script does not work in Google Chrome #1665
• If content type is not specified, a $permissions rule is applied to all requests #1856
• Cookie rules with [ and ] in the name are considered invalid #1843
• Cosmetic rules are not applied in some cases when AdGuard and AdGuard VPN Browser Extension are running simultaneously #1791
• $all modifier works incorrectly #1842
• AdGuard content script is not injected on mall.sk #1834
• Blocking regex rule with escaped slash in a character class does not work #1831
• Content script is not injected if there is a tag (with embed attribute) before doctype declaration #1825
• $path modifier does not work with query params #1817
• $removeparam on URL with port redirects to URL without port #1818
• AdGuard breaks the android-hilfe.de website #1800
• Cannot connect to wiki.cemu.info securely #1821

Scriptlets (JavaScript enhancement for filtering rules)

• Scriptlets updated to v1.10.1

Improvements

• Added compatibility with uBO’s set-cookie scriptlet #332
• Added new scriptlet call-nothrow.js #333
• Added new scriptlet spoof-css #317
• Added new scriptlet trusted-create-element #278
• Added new scriptlet trusted-set-attr #281
• Improved set-cookie by adding more supported values #379
• Improved google-analytics by adding ga.q property #355
• Improved google-ima3 by adding OmidVerificationVendor property #353

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.5.4 #5047

Improvements

• Support for passing hostname to outbound proxy instead of bootstrapping #197
• Improved handling of HTTPS RRType #215
• Using Happy Eyeballs for IPv4/IPv6 in DoH #217

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.17 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.

We fix the code, you enjoy the result. With the new update you will no longer have any problems when trying to start the protection. We have also fixed the errors that occurred with the filter editor and the WFP network driver. The new version of AdGuard for Windows is waiting for you. Update the app and let the code magic begin!

Changelog

Fixes

• Can’t start the protection when selecting the WFP network driver #5055
• Filter editor sometimes works incorrectly when editing a rule #5058
• Unable to start the protection after updating to AdGuard 7.17 for Windows beta 3 #5060

​Release channel

Beta channel

Nightly channel

7.17 beta 3

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.

The new (third!) beta contains a lot of changes: we fixed issues with creating custom DNS servers and, as usual, updated the CoreLibs and DnsLibs. See the changelog for more details.

Changelog

Improvements

• Added parsing for the # symbol #4666

Fixes

• Setting up a custom DNS server is not always possible, fallback fails #5029

CoreLibs

Updated CoreLibs to v1.14.38 #5052

Improvements

• Added an option to use | as a separator in $permissions #1850

Fixes

• Cannot parse QUIC ClientHello split into two packets #1861
• VOT (voice over translation) script does not work in Google Chrome #1665
• If content type is not specified, a $permissions rule applies to all requests
  #1856

Scriptlets

Updated Scriptlets to v1.10.1

Improvements

• Added compatibility with uBO's set-cookie scriptlet #332
• Added new scriptlet — 'call-nothrow.js' #333
• Added new scriptlet — 'spoof-css' #317
• Added new scriptlet — 'trusted-create-element' #278
• Added new scriptlet — 'trusted-set-attr' #281
• Improved set-cookie by adding more supported values #379

DnsLibs

Updated DnsLibs to v2.5.4#5047

Improvements

• Support for passing hostname to outbound proxy instead of bootstrapping #197
• Improved handling of HTTPS rrtype #215
• Using Happy Eyeballs for IPv4/IPv6 in DoH #217

Fixes

• Cannot use DoH DNS server that uses HTTP/1.1 after updating to version 4.3 #216

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.17 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.

Three bugs walk into a bar but never get to order a drink. Why? Because AdGuard was the bartender and fixed them before they could even take a seat.

Jokes aside, we've fixed many more bugs for this beta, including issues with installation path change, Protection activation failure and removing the AdGuard directory from Program Files (x86). We’ve also updated CoreLibs and made some improvements, so now you can enjoy seamless work of the app.

Changelog

Fixes

• The original installation path is changed during installation #4975
• The AdGuard directory is not removed from Program Files (x86) when updating to v7.16 x64 #4972
• Searching by type does not work in the Filtering log #4980
• Unable to start protection after updating to v7.17.0 Nightly 1 (4583) #5017

CoreLibs (filtering engine) updated to v1.14.16

Improvements

• Added an ability to indicate if outbound proxy is used in the request processed event #1385
• Added support for passing host to outbound proxy #1386
• Added Firefox 121.0+ to the list of user agents that support :has() natively #1840

Fixes

• Cookie rules with [ and ] in the name are considered invalid #1843
• Cosmetic rules are not applied in some cases when AdGuard and AdGuard VPN Browser Extension work simultaneously #1791
• $all modifier works incorrectly #1842
• AdGuard content script is not injected on mall.sk #1834
• Blocking regex rule with escaped slash in a character class does not work #1831
• Content script is not injected if there is a tag (with embed attribute) before doctype declaration #1825
• $path modifier does not work with query params #1817
• $removeparam on url with port redirects to url without port #1818
• AdGuard breaks the android-hilfe.de website #1800
• Cannot connect to wiki.cemu.info securely #1821

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

• Improved google-analytics by adding ga.q property #355
• Improved google-ima3 by adding OmidVerificationVendor property #353

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.17 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.

Meet the first beta of AdGuard v7.17 for Windows. In this version, we've been busy bug-hunting so you can enjoy a more stable experience.

Changelog

Fixes

• AdguardSvc.exe is branching out into multiple threads #4874
• Certificate Info is being displayed twice #4964
• Filtered DNS requests are not displayed in the Filtering log after toggling network off/on #4941
• Old directories are not deleted from the AppData directory #581
• Time counter for filters updates doesn’t work #4974
• Turning the DNS Protection on breaks the local Windows domain connection #4906

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.16

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 number is the answer to the question of life, the universe, and everything? Frankly, no clue, but AdGuard v7.16 for Windows is all about 64. We’re excited to announce that our app is now compatible with 64-bit systems.

What does it mean?

Well, most Windows computers nowadays are 64-bit, they have more resources such as processing power and memory than their 32-bit predecessors. AdGuard has been loyal to the 32-bit version, but progress marches on. It’s time to embrace 64-bit compatibility, which we hope will lead to a more responsive experience for our users and make turning filters on and off feel like pure magic.

But AdGuard still works on 32-bit computers, right?

The trusty 32-bit machines will not be forgotten. You won’t need to download a separate installer: our system will automatically detect your computer’s bitness, allowing you to install the appropriate version.

Anything new with filtering in this version?

Of course! Another big change is that we have improved HTML filtering. We’ve added support for selectors in HTML filtering rules, which helps block ads more effectively.

OK, what else you’ve got?

Our latest DnsLibs brings a new feature to AdGuard for Windows: basic HTTP authentication. Why is this useful?
Those who use the DNS-over-HTTPS protocol also benefit from the features of the HTTP protocol. For instance, when using DoH, you have an authentication option that standard DNS servers simply do not have.
But what if you have a custom DNS server and you want to restrict access to it? Surely you can do it by restricting access by IP address. However, mobile devices, for example, change networks frequently. How to deal with that? This is where HTTP authentication support comes in. Using this feature in AdGuard for Windows, you can include authentication information to connect to a custom DNS server.

This feature is currently not available in AdGuard Home and AdGuard DNS, but you will be the first to know when it is!

Surely that’s it, right?

We haven't finished yet. When it comes to HTTPS filtering, it can be difficult to сheck the original domain certificate. We’ve covered this issue in our Knowledge base. While AdGuard does (always!) verify validity, you might want to check it yourself.
To make HTTPS filtering more transparent for users, AdGuard now offers an option to view the original certificate in “Filtering log”. Here, you can check the details of any web request, see what kind of encryption AdGuard has used, and view the original certificate.



As you can see from the massive changelog, we haven’t been idle since the last release. We haven’t left the WFP and TDI drivers behind either: they’ve been freshly updated. Anyway, let’s cut the talking and go straight to updating!

Changelog

Improvements

• Indicate the HTTPS filtering state and the original certificate in the Filtering log #4812
• Enhanced uninstallation process #4428
• Improved buttons text color in installer for Active state #4887
• Removed app shortcut to the folder in Start Menu #4834
• Adapted the onboarding screen to the dark theme #4583
• Packed backup files have .bak extension #540
• Removed the second mention of the build number in the About section #4836
• Updated the Finnish translations on the updater screen #4761

Fixes

• Enable all option in the Filter editor can crash the app #4857
• AdGuard doesn’t run due to an invalid signature #4864
• The app doesn't start automatically after clean installation and reboot on Windows 7 #4760
• Blocklist and allowlist do not work properly in Parental control #4189
• Browser Assistant keeps working in the app excluded by full path #4723
• DNS exclusions are not working if Fallback servers mode isn’t system default #4822
• Long start if some domains/ports are blocked #4894
• Multiple separators appear after the app crash #327
• Since v7.15, the service can’t start normally if it fails to connect to 20.189.79.72:123 via UDP #4868
• Chinese Traditional words in the Chinese Simplified description of Web of Trust #4739
• Missing strings from the Filtering log in Crowdin #4825
• Lost selection of multiple rules when editing filters #4474
• A rule that has been cut cannot be inserted back into the field from which it was cut from #4859
• Can’t add custom DNS if address contains port number #4945
• Can’t transfer parameters related to DNS filters and license types during web reporting #4931
• Old directories are not deleted from AppData directory #4939
• Recent beta for Windows 11 left x32 in Startup that needs to be removed in registry #4940

CoreLibs (Filtering engine)

• Updated CoreLibs to v1.13.115
• Added support anti-DPI feature for Korea Telecom #1789
• Improved usage of ECH retry_configs #1793
• Removed an option to move a certificate #277
  ​

Improvements

• Added !#else preprocessor directive support #1806
• Adopted new rule priority scheme #1768
• Changed sec-ch-ua headers to match user-agent when Stealth Mode is active #1764
• Improved HTML filtering performance #1772

Fixes

• Closed active QUIC/H3 connections on protection start-up on Windows #1815
• Images are not displayed in Edge Bing Chat #1744
• Websites using SXG have no cosmetic filtering when opened from Google search #1812
• The filtering on the macperformanceguide.com website doesn’t work #1810
• UDP timeout is too small in TcpIpStack #1796
• Certificate verification fails on websites with recently updated certs #1833
• unicode.org does not load with AdGuard for Windows #1830
• One of the subdomains is not filtered due to different site certificates #1839
• Connection error when visiting smartstore.naver.com in Firefox #4960

DnsLibs (DNS filtering engine)

• Updated DnsLibs to v2.4.37
  ​

Improvements

• Added basic auth for DoH endpoints #189
• Allowed sharp comment in exact domain name rules #196
• Allowed specifying TCP-only and UDP-only DNS upstreams #208
• On-the-fly filtering of DoH connections #198

Fixes

• Possible DoS attack against the local DNS proxy when it's using a plain DNS upstream #202
• 127.0.0.1 local is incorrectly interpreted as being for all .local address, breaking mDNS #207
• DoH is trying to use stale connection for too long #200
• Made so that type=HTTPS requests are now filtered properly #199

Important for filter maintainers

• Added User rules option to the ...

7.16 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.

The cold winter weather motivates developers and filter maintainers to work even harder just to stay warm. The chilly temperatures also affect content writers, so let’s quickly talk about the second beta of AdGuard for Windows.

We’ve fixed a bunch of issues, including a major one related to certificate verification. The HTTPS filtering simply did not work on websites because AdGuard did not recognize the certificates of these websites as valid. Thanks to our CoreLibs masters, this problem was solved in the new version of the library.

It would be pointless to update only one library, though. This beta also comes with updated DnsLibs, Scriptlets, and UserscriptsWrapper. If you come across any issues while testing, please let us know on GitHub

Changelog

Fixes

• Can’t add custom DNS if address contains port number #4945
• Can’t transfer parameters related to DNS filters and license types during web reporting #4931
• Old directories are not deleted from AppData directory #4939
• Recent beta for Windows 11 left x32 in Startup that needs to be removed in registry #4940

CoreLibs (Filtering engine)

• CoreLibs updated to v1.13.104 #4954

Fixes

• Certificate verification fails on websites with recently updated certs #1833
• unicode.org does not load with AdGuard for Windows #1830
  ​

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.4.32 #4955

Improvements

• Allowed specifying TCP-only and UDP-only DNS upstreams #208
• On-the-fly filtering of DoH connections #198

Important for filter maintainers

Fixes

• The counter may not recognize the added rule #4922
• Lost selection of multiple rules when editing filters #4918
  ​

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

​#### Improvements

• Improved prevent-fetch — set response.status to 0 if responseType is set to opaque #364
• Versions of used libs are now shown on the About page #2237

Fixes

• Fixed googletagservices-gpt — setPrivacySettings() #344
  ​

UserscriptsWrapper

• UserscriptsWrapper updated to v1.2.21
  ​

Fixes

• Userscript 网盘直链下载助手 is not working with AdGuard #1780

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel

7.16 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.

What number is the answer to the question of life, the universe, and everything? Frankly, no clue, but this beta version of AdGuard for Windows is all about 64. We’re excited to announce that our app is now compatible with 64-bit systems.

What does it mean?

Well, most Windows computers nowadays are 64-bit, they have more resources such as processing power and memory than their 32-bit predecessors. AdGuard has been loyal to the 32-bit version, but progress marches on. It’s time to embrace 64-bit compatibility, which we hope will lead to a more efficient and responsive experience for our users.

But AdGuard still works on 32-bit computers, right?

The trusty 32-bit machines will not be forgotten. You won’t need to download a separate installer; our system will automatically detect your computer’s bitness, allowing you to install the appropriate version.

Anything new with ad blocking?

Another big change in this version is that we have improved HTML filtering. We added support for selectors in HTML filtering rules, which helps block ads more effectively.

OK, what else you’ve got?

Those who use the DNS-over-HTTPS protocol also benefit from the features of the HTTP protocol. For instance, when using DoH, you have an authorization option that standard DNS servers simply do not have. With the new DnsLibs v2.4, AdGuard now offers HTTP authorization when setting up a DNS server.
Why is this important? Imagine you have a custom DNS server and you want to restrict access to it. You could restrict access by IP address, but what if you have a mobile device and frequently change networks?
This is where HTTP authorization support comes in. Currently, there are not many DNS servers that offer this feature. Even AdGuard Home and AdGuard DNS do not have it yet. However, it will be available soon, and you will be the first to know!

Surely that’s it, right?

As you can see from the changelog, we haven’t been idle since the last release. What has been done:

• Updated our beloved libraries: CoreLibs, DnsLibs, Scriptlets, — you name it — to ensure effective ad blocking and provide an even better user experience
• Didn’t leave behind the WFP and TDI drivers: they’ve also been freshly updated
  However, thorough testing is crucial, and we’d appreciate it if you’d take a look at this beta version and share your feedback.

Changelog

Improvements

• Indicate the HTTPS filtering state and the original certificate in the Filtering log #4812
• Enhanced uninstallation process #4428
• Improved buttons text color in installer for Active state #4887
• Removed app shortcut to the folder in Start Menu #4834
• Adapted the onboarding screen to the dark theme #4583
• Packed backup files have .bak extension #540
• Removed the second mention of the build number in the About section #4836
• Updated the Finnish translations on the updater screen #4761

Fixes

• Enable all option in the Filter editor can crash the app #4857
• AdGuard doesn’t run due to an invalid signature #4864
• The app doesn't start automatically after clean installation and reboot on Windows 7 #4760
• Blocklist and allowlist do not work properly in Parental control #4189
• Browser Assistant keeps working in the app excluded by full path #4723
• DNS exclusions are not working if Fallback servers mode isn’t system default #4822
• Long start if some domains/ports are blocked #4894
• Multiple separators appear after the app crash #327
• Since v7.15, the service can’t start normally if it fails to connect to 20.189.79.72:123 via UDP #4868
• Chinese Traditional words in the Chinese Simplified description of Web of Trust #4739
• Missing strings from the Filtering log in Crowdin #4825
• Lost selection of multiple rules when editing filters #4474
• A rule that has been cut cannot be inserted back into the field from which it was cut from #4859

CoreLibs (Filtering engine)

• Updated CoreLibs to v1.13.88
• Added support anti-DPI feature for Korea Telecom #1789
• Improved usage of ECH retry_configs #1793
• Removed an option to move a certificate #277
  ​

Improvements

• Added !#else preprocessor directive support #1806
• Adopted new rule priority scheme #1768
• Changed sec-ch-ua headers to match user-agent when Stealth Mode is active #1764
• Improved HTML filtering performance #1772

Fixes

• Close active QUIC/H3 connections on protection start-up on Windows #1815
• Images are not displayed in Edge Bing Chat #1744
• The 网盘直链下载助手 user script is not working with AdGuard #1780
• Websites using SXG have no cosmetic filtering when opened from Google search #1812
• The filtering on the macperformanceguide.com website doesn’t work #1810
• UDP timeout is too small in TcpIpStack #1796

DnsLibs (DNS filtering engine)

• Updated DnsLibs to v2.4.17
  ​

Improvements

• Added basic auth for DoH endpoints #189
• Allowed sharp comment in exact domain name rules #196

Fixes

• Possible DoS attack against the local DNS proxy when it's using a plain DNS upstream #202
• 127.0.0.1 local is incorrectly interpreted as being for all .local address, breaking mDNS #207
• DoH is trying to use stale connection for too long #200
• Made so that type=HTTPS requests are now filtered properly #199

Important for filter maintainers

• Added User rules option to the filtering log #4560
• Removed the unnecessary period in the pattern when creating a DNS rule from “Unblock” #4872
• Filter editor: rule state shouldn’t change while editing/typing #4910
• Incorrect behavior after exiting inline editing mode #4850
• Incorrect behavior of the first rule in the User Rules filter #4885
• Detect website locale based on HTML "lang" attribute and language request HTTP headers #1736
• Increased limit for $replace rules #1802
• Added $extension modifier disabling specific userscript #1706
• Added support for cap_html_filtering condition #1758
• $denyallow does not allow blocking documents #1809
• $stealth exceptions do not work on the TCP stack level where we block STUN/TURN #1737
• Content script is not injected into elements loaded in object tag #1769
• Improved HTML filtering rules $$ and allowed CSS-like selectors #94

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v1.9.96

Improvements

• Handle uBO's syntax $redirect priorities #59
• Improved xml-prune — su...

7.15.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.

This quick release addresses a critical issue affecting Firefox users. With AdGuard enabled, some websites would not load and would display the error about a potential security risk. Also, the app now uses less CPU compared to the version 7.15.

Changelog

Fixes

• HSTS/SSL errors in Firefox
  #4866

CoreLibs (Filtering engine)

• CoreLibs updated to v1.12.83 #4866

AdGuard for Windows direct download links:

​Release channel

Beta channel

Nightly channel