AdGuard for Windows 7.9

[Aydin]

Now we know that we can create suspense no worse than Hitchcock: since the last release, we’ve presented three versions of the app (one beta version and two release candidates). But enough is enough! Meet AdGuard 7.9 for Windows, the release we've all been waiting for. Let's list the major innovations and benefits of this version so you can savor them.

Let's start with the fact that we have worked hard on improving the performance of the application as well as its user interface. Now you'll enjoy interacting with AdGuard for Windows even more. We've also improved the advanced DNS settings by adding a bootstrap option. Don't want to use the system DNS resolver as a bootstrap? You don't have to! Now you can specify IP addresses of the DNS servers that are used to determine the address of the encrypted DNS servers.

What else? We fixed tons of bugs of different severity, including the problem with auto-activation of language filters. As a result, AdGuard's stability is improved now. Of course we couldn't avoid updating CoreLibs and DNSLibs. That's all, folks! We hope you’ll enjoy the new version of AdGuard for Windows.

Spoiler: Changelog

Changelog

• [Enhancement] Added an advanced option to set custom DNS bootstrap address #4080
• [Enhancement] Added sorting by request type `Connection` #3830
• [Enhancement] Browser Assistant's filtering log won't open when AdGuard is closed, but continues filtering #3335
• [Fixed] Language-specific filters are automatically enabled even if the Ad Blocker module is disabled #4098
• [Fixed] Pseudo-update of userscripts #4050
• [Fixed] Link to the Home page in the User rules settings #4068
• [Fixed] When adding a new rule via Filtering log, the default rule includes the name of the filter it belongs to #4045
• [Fixed] Wrong padding under filter name in the filter editor #3553
• [Fixed] A mistake in the text of the license agreement in the Installer #4060
• [Fixed] `$$` rules are not visible in the filtering log #4113
• [Fixed] Blocked requests by Parental control are shown as Stealth mode's ones in Filtering log #4074
• [Fixed] The rule counter on the main screen defines comments as active rules #3994
• [Fixed] Impossible to scroll DNS exclusions screen #4024
• [Fixed] When enabling/disabling protection "on this site" in one browser window, the Assistant's icon does not change its color in another opened browser window.
• [Fixed] localization of the `All rights reserved` string in About tab #4065
• [Other] AdGuard uses about 10% CPU on `Netflix.com` with disabled protection on this website #4003
• [Other] Reworked onboarding animation on Privacy protection slide
• [Other] The text of the error that occurs when a custom filter is added incorrectly is not translated #4026
• [Other] Info about AdGuard is left in registry after deleting #4064

Updated CoreLibs to v1.9.34

• [Enhancement] Added an ability to apply cosmetic rules to specific URLs only #124
• [Enhancement] Improved detection of content type using `Sec-Fetch-Dest` header #1382
• [Enhancement] Changed default address `Hide your IP` #1516
• [Enhancement] TLS fingerprint should not change when AdGuard is enabled #1503
• [Enhancement] Improved the HTTPS filter certificate caching algorithm #1402
• [Fixed] Authorization on `kinopoisk.ru` doesn't work when `Self-destruct third-party cookie files` function is enabled #1502
• [Fixed] If rule with `$all` modifier is applied, wrong rule appears in logs #1535
• [Fixed] AdGuard breaks the encoding on danawa.com #1534
• [Fixed] An error `net::ERR_HTTP2_PROTOCOL_ERROR` on `www.adorama.com` #1518
• [Fixed] Rules with `$third-party` modifier do not work at `worldvision.de` #1523
• [Other] AdGuard fails at pinning test on `pinning-test.badssl.com` #1526
• [Other] Validation errors on `RegEx` entries #1544

Updated DnsLibs to v1.7.4

• [Other] Started using NativeLibsCommon in DnsLibs #128

This version on Github
Download via direct link