AdGuard for Windows - 7.12 RC


Quality Assurance
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.


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

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

  • 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

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

Upgraded Scriptlets to v1.7.20

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

This version on Github
Download via direct link