# Download AdGuard > AdGuard is a unique adblock program for Windows that has all the necessary features for the best web experience. - Canonical page: https://everyversion.net/adguard/ - Publisher: Adguard Software Ltd - Latest: Windows 8.0.5587, macOS 2.20.3.2633 (Windows build released 2026-10-22) - Platforms: Windows, macOS - License: Proprietary (https://adguard.com/eula.html) - Price: Not stated in winget-pkgs - Website: https://adguard.com/adguard-windows/overview.html - Support: https://adguard.com/support.html - winget ID: AdGuard.AdGuard - Homebrew cask: adguard - Verification: level 1 — Hashes re-computed from the publisher’s download: 2 of 2 installers match the upstream manifest. Checked by Cristian Gonzalez Guasch. - Source (Windows): winget-pkgs @ 7ba156ba3b98370906bafbaa35808b8d6cfe55f1 — https://github.com/microsoft/winget-pkgs/tree/7ba156ba3b98370906bafbaa35808b8d6cfe55f1/manifests/a/AdGuard/AdGuard - Source (macOS): Homebrew cask @ 4075b2218ff4073f481d7a9299faa66ea2435943 — https://github.com/Homebrew/homebrew-cask/blob/4075b2218ff4073f481d7a9299faa66ea2435943/Casks/a/adguard.rb ## Overview 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. ## Windows ### What the installer does - Delivered as a WiX Burn bootstrapper (.exe) for x86. - Installs for all users on the PC, which normally requires administrator rights. - Supports unattended install with `-quiet`. - Declared install modes: interactive and silent. - Registers the `adguard://` and `sdns://` link protocol. - Upgrades install over the existing version. ### Versions (newest first) #### 8.0.5587 — 2026-10-22 - x86 burn (machine): setup-8.0.5587.exe - url: https://static.adtidy.org/windows/setup-8.0.5587.exe - sha256: 7f499a0e196f9b09ee1a2d87c98e418e6b44caa381cfa4ea29ed9d9d48b54949 Release notes: In response to the eMudhra certificate authority incident, we’ve blacklisted the compromised certificates. HTTPS filtering will not work on domains using these certificates — such connections will be validated by the browser itself. Safe choices include: Chrome, Edge, Opera, Brave, Vivaldi (revoked via Google CRLSet) Firefox (revoked via Mozilla OneCRL) Changelog CoreLibs (Filtering engine) CoreLibs updated to v1.22.31 #6279 Pin: `winget install --id AdGuard.AdGuard --version 8.0.5587 --exact` #### 8.0.5584 — 2026-10-01 - x86 burn (machine): setup-8.0.5584.exe - url: https://static.adtidy.org/windows/setup-8.0.5584.exe - sha256: c8dca400f03018bdd82482ec070a31b2dd9a9c25b72e463162cf583781866a1d Release notes: Here’s an additional technical update following the previous one. In it, we’ve fixed bugs and kept working on the app stability. Changelog Fixes AdGuard v8.1.0 nightly (5671) fails to start after update with SockFilter enabled #6225 Pin: `winget install --id AdGuard.AdGuard --version 8.0.5584 --exact` #### 8.0.5570 — 2026-09-09 - x86 burn (machine): setup-8.0.5570.exe - url: https://static.adtidy.org/windows/setup-8.0.5570.exe - sha256: 4bda0c632c9f25011e65ee025e9a1ba2d1fb7b4c96c96e8ac0b743e56da04ac9 Release notes: Not all updates are flashy, but they’re still important. This release focuses on the small but crucial fixes that keep things running as they should. Pin: `winget install --id AdGuard.AdGuard --version 8.0.5570 --exact` #### 8.0.5560.0 — 2026-08-20 - x86 burn (machine): setup-8.0.5560.0.exe - url: https://static.adtidy.org/windows/setup-8.0.5560.0.exe - sha256: f17289461f74c3dedee4eb615d8ce719019dd655a7763394423a4881a239da9c Release notes: A brand-new version, a new major number, a fresh design — and, most importantly, truly system-wide protection. AdGuard for Windows v8.0 doesn’t just look different: it gives you clearer control over the traffic on your computer and makes the most important settings easier to reach. Truly system-wide protection Alongside the DNS filtering you already had, AdGuard offers full-fledged network-level filtering. This means stronger protection and more control: you can filter all Internet traffic on your device, so your protection is system-wide. AdGuard uses a special network driver that handles the actual sending and receiving of data, allowing us to filter traffic from every app on your device. While DNS filtering is still there, it is less flexible, and some tracking requests can still get through. This is where HTTPS filtering becomes essential. With it enabled, AdGuard can inspect traffic within Windows apps. This allows us to distinguish between legitimate content and tracking requests, even when they come from the same domain. By decrypting the traffic, AdGuard can identify the full URL and block only the tracking requests while leaving the rest of the app working just fine. While HTTPS filtering is enabled for browsers by default, it is disabled for most other apps to ensure better compatibility. You can always enable it for extra protection: just select the application you want to filter in App management and toggle on Filter HTTPS traffic. See what your apps are doing and take control To make managing traffic easier and give you a clear picture of what’s happening on your device, we’ve added two new sections: App management and Statistics. App management App management lets you control how each app accesses the Internet. By default, AdGuard filters everything. As soon as an app goes online, it appears in App management, and its traffic is routed through AdGuard. From there, you can configure what to do with the app and how to filter it: Decide which apps have their traffic routed through AdGuard Choose to block ads and trackers in specific apps Enable HTTPS filtering in apps of your choice We’ve also introduced Filter unknown apps, a new setting for handling apps that are not yet in the compatibility or exclusion lists. It’s on by default — new apps get regular filtering, while HTTPS interception stays off to avoid affecting app behavior. Statistics Statistics show detailed network activity. The Companies section provides a perspective on all the companies that your device has sent requests to, while in Apps and Domains you see the stats specific traffic data for every app routed through AdGuard. You can quickly identify and block anything suspicious. Not only inside updates: A complete redesign AdGuard for Windows has been completely redesigned. Our focus was on simplicity and ease of use. The most important tools are now front and center, while advanced settings are still available — just tucked away so they don’t overwhelm new users. Key settings in plain sight The app is designed to let you enable everything you need straight from the first screen. Just click the symbols you see — they stand for blocking ads and trackers, handling cookie notices and similar annoyances, and DNS protection. Fine-tune your protection: Head to the Protection section, where settings are clearly categorized, explained in simple terms, and enabled by one toggle. Tracking protection: Choose a level of protection — from a simple, comfortable experience to a more advanced one, which includes deleting cookies for enhanced privacy. There is also a custom level where you can freely fine-tune everything to suit your preferences: like blocking notifications from websites or enabling anti-DPI protection. Advanced approach to filtering: You can find low-level and network settings in Settings → App settings. For more details on new features, check the Knowledge Base. It’s been a huge overhaul, and we can’t wait to hear what you think. Share your thoughts and send improvement ideas via GitHub Issues. Pin: `winget install --id AdGuard.AdGuard --version 8.0.5560.0 --exact` #### 7.22.5282.0 — 2026-06-16 - x86 burn (machine): setup-7.22.5282.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5282.0.exe - sha256: 4fa87d3638f503e119deeea171239bd519831d5b8b950bc926a54f99771127b0 Release notes: "Dear developers, can we get a bugfix pronto?" Of course you can! Right after the release, we serve you a hotfix with a resolved problem #6035 and fine-tuned operation. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5282.0 --exact` #### 7.22.5279.0 — 2026-06-08 - x86 burn (machine): setup-7.22.5279.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5279.0.exe - sha256: 7399948be295d3c07016454e63f6c6ceaa5bb62836b7e69cfa4d88931687ad7a Release notes: This is a technical update aimed to increase the app stability and fix minor bugs. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5279.0 --exact` #### 7.22.5271.0 — 2026-04-20 - x86 burn (machine): setup-7.22.5271.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5271.0.exe - sha256: 8b09d78befec25e36062d0686e7ad2a5bb535286bbd17b52095a97e705310009 Release notes: Here’s an additional technical update following the previous one. In it, we’ve fixed bugs and kept working on the app stability. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5271.0 --exact` #### 7.22.5267.0 — 2026-03-19 - x86 burn (machine): setup-7.22.5267.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5267.0.exe - sha256: 2e1a2acb5da64b199494ef89cc675bec343afacac68960dd00169fff8babf461 Release notes: Your feedback helps us improve faster. This patch addresses issues reported during the use of the experimental SockFilter driver introduced in v7.22.4, including BSOD reports on GitHub and problems affecting Discord. We’ve also updated the WFP driver to improve overall stability and performance. Changelog Fixes BSOD occurrences when using the SockFilter driver Issues with Discord voice and video calls when SockFilter is enabled Improvements Updated the WFP driver Pin: `winget install --id AdGuard.AdGuard --version 7.22.5267.0 --exact` #### 7.22.5262.0 — 2026-03-05 - x86 burn (machine): setup-7.22.5262.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5262.0.exe - sha256: 351ed5aad47a7d3415c8c7196581945eea59f26f89b883853b2a723c28f6be2d Release notes: Have you ever noticed how the app crashes even when you have a freshly updated version? Well, notice no more! This hotfix solves that problem. From now on, just pure ad blocking all the way. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5262.0 --exact` #### 7.22.5257.0 — 2026-02-26 - x86 burn (machine): setup-7.22.5257.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5257.0.exe - sha256: a28695aeb0224c27583abb9c42f723d128105774b0ac327e0b039484e8af5caf Release notes: This is one of those moments where a patch deserves the same attention as a full release: v7.22.4 introduces SockFilter, a new, experimental lightweight network driver for AdGuard for Windows. While still far from perfect (you will probably find a few bugs here and there), we’re confident in its potential to make AdGuard better in the future. Why introduce a new driver at all? Until now, AdGuard for Windows relied mostly on a WFP driver. WFP is powerful, but it also comes with complexity, compatibility challenges, and stability issues. The TDI driver used to be an alternative, and while it is still available, it’s an outdated solution and may lead to filtering issues in some versions of Google Chrome. A temporary workaround exists, but it’s not a reliable long-term solution. The conclusion was simple: it was time for a change. That’s why we’re introducing SockFilter — it brings a different approach that works especially well for ad blocking, plus it’s the solution we’ve been waiting for to finally put these problems behind us. The advantages of SockFilter When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers. Right now, it’s still experimental and unstable, so you might not see all the benefits yet. But here’s a look at what’s possible in the future: Better interaction with other network apps: SockFilter is designed to cooperate smoothly with VPNs, firewalls, and antivirus software. By avoiding clashes over network control, it can help prevent connection issues and make everything work together more reliably. Lower risk of system crashes: SockFilter works in a safer part of Windows networking, which can help it avoid deep system errors that can sometimes cause sudden blue-screen crashes. In practice, this can result in better stability and fewer chances of your system unexpectedly crashing while AdGuard is running. On track for better stability: SockFilter works closer to how apps normally use the Internet, instead of dealing with low-level network data, resulting in the potential to reduce complexity behind the scenes and making AdGuard more reliable in everyday use. Known issues So far, a small number of users have reported an issue with SockFilter: the new driver appears to interfere with voice and video calls on Discord. The problem was described on GitHub. Our QA team has successfully reproduced the issue and is actively working on a fix. If you notice any related problems or have additional details to share, please let us know. Your feedback helps us resolve this faster. How to start using it Other issues may appear when using SockFilter, after all, Experimental mode means that it’s ready for testing and that there may be bugs. We’d love your help in finding them! To test it, go to Settings → Network → Traffic filtering, enable traffic filtering, and select SockFilter (Experimental) from the list of available options. If you notice anything unusual, unexpected, or just plain broken, you can switch back to TDI or WFP at any time. In that case, please report the issue on GitHub — your feedback directly helps shape the future of AdGuard for Windows. Changelog Improvements Added SockFilter driver #5780 Pin: `winget install --id AdGuard.AdGuard --version 7.22.5257.0 --exact` #### 7.22.5240.0 — 2025-12-11 - x86 burn (machine): setup-7.22.5240.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5240.0.exe - sha256: e7d8247eb61694ae18d86ab635dacb006857fa37bfcb68f324ad81306e11a3dc Release notes: In this hotfix, we’re automatically migrating all users from the outdated TDI driver to the more reliable WFP driver. This change comes as a solution to an issue reported by users, ensuring filtering works with the latest versions of Chrome-based browsers, which aren’t fully compatible with TDI. TDI isn’t going away completely — you can still enable it if you want to. But if you do, the app will show you a clear warning explaining the potential issues and how to temporarily fix them. For all the details, check out our Knowledge Base. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5240.0 --exact` #### 7.22.5228.0 — 2025-11-14 - x86 burn (machine): setup-7.22.5228.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5228.0.exe - sha256: db51830a467ca2cd1c77d15a27d13d39414c7588e28022bf9126541247d633af Release notes: A small bug has crept into the release. That’s why we’re publishing a hotfix today: so you can enjoy the service, and we can get on with some bigger tasks. Pin: `winget install --id AdGuard.AdGuard --version 7.22.5228.0 --exact` #### 7.22.5226.0 — 2025-11-06 - x86 burn (machine): setup-7.22.5226.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5226.0.exe - sha256: 27ae2a4c31f90a187dd50a74d9b415dd58236381902f15d4031761958d546146 Release notes: Oh no, we missed the bugs! In this hotfix, we got rid of not one, but two nasty problems. They for sure won’t be missed — ba-dum-tss! Pin: `winget install --id AdGuard.AdGuard --version 7.22.5226.0 --exact` #### 7.22.5225.0 — 2025-10-02 - x86 burn (machine): setup-7.22.5225.0.exe - url: https://static.adtidy.org/windows/setup-7.22.5225.0.exe - sha256: a754227e9e01a6c60980e02460c46e5248ac6615fa152854252dff77404ed268 Release notes: This update brings exciting improvements to make your AdGuard experience even better: you now get more customization with our improved userscript compatibility. Behind this change is CoreLibs v1.19, AdGuard’s filtering engine and technical core. Although not strictly tied to this release, we also have something worth celebrating: AdGuard is now available in the Microsoft Store, making installation more convenient and, we dare say, easier than ever. Improved userscript compatibility Some userscripts are designed to work on Single Page Applications (SPAs), such as YouTube. Until now, these scripts often failed to load correctly: if a user opened YouTube’s homepage first, the script wouldn’t inject, and it wouldn’t trigger when navigating to other pages where it was supposed to work. With this update, AdGuard fixes that limitation by ensuring such scripts are properly executed across SPA websites, making AdGuard even more flexible for advanced customization options. This enhancement also allows us to confidently recommend useful tools like the SponsorBlock userscript, which automatically skips sponsored segments in YouTube videos. To try it out: 1. Go to https://mchangrh.github.io/sb.js/. 2. Click Generate link. 3. Copy the link that appears. 4. Open AdGuard and go to Extensions → Add extension → Import from file or URL. 5. Paste the copied link and confirm. AdGuard is now in the Microsoft Store You can now download AdGuard directly from the Microsoft Store, making it quick and secure to install, update, and manage alongside your other apps. Subscriptions and payments are still handled directly through AdGuard’s website, ensuring flexibility and full control over your license. Product updates for builds downloaded from the Microsoft Store will work the same way as in the regular builds. In other words, the store version is simply a new distribution channel, and the update process remains unchanged. Support for Comet browser We’ve added full compatibility for Perplexity’s Comet browser. Now you can now enjoy the same reliable ad blocking and privacy protection in Comet as you do in other supported browsers. Changelog Improvements - Added Perplexity Comet to the list of supported browsers #5625 - Added a warning when userscripts require modifying the CSP Fixes - The option “Exclude Wi-Fi SSID from the DNS filtering” does not work #5535 - Microsoft Recall is enabled by default on Windows 10 Pro 22H2 #5580 - User rules counter appears at app’s launch #5558 - Active tabs in the Filtering log are not visually highlighted in dark theme #5563 - False “Error” status is shown during update check despite filters being updated successfully #5614 - The filter version and the date information are not shown in Custom filters #5557 DnsLibs (DNS filtering engine) - DnsLibs updated to v2.6.20 #5636 CoreLibs (Filtering engine) - CoreLibs updated to v1.19.34 Improvements - Added wildcard and regexp support to the $app modifier #1906 - Added support for the ALPS extension #1987 Fixes - Content-type modifiers cannot be used with the $urltransform modifier #1978 - XHR timeout with “immersivetranslate” userscript #2000 - Filtering is disabled because it may affect websites’ performance #1994 - Some extensions stopped working after updating to v2.17 #1993 - $removeparam does not work in pair with $domain #1999 Scriptlets (JavaScript enhancement for filtering rules) - Scriptlets updated to v2.2.10 Improvements - Added new scriptlet — trusted-replace-argument #405 - Added support for uBO arguments for href-sanitizer #493 Fixes - prevent-element-src-loading — TrustedScriptURL is not defined in Firefox #514 - trusted-replace-node-text — some quotes are incorrectly escaped #517 - Scriptlets compilation error in Safari 15 due to unsupported regex #519 - trusted-set-cookie-reload — infinite reload for constantly changing values #489 Pin: `winget install --id AdGuard.AdGuard --version 7.22.5225.0 --exact` #### 7.21.5089.0 - x86 burn (machine): setup-7.21.5089.0.exe - url: https://static.adtidy.org/windows/setup-7.21.5089.0.exe - sha256: 765de92beb84ce23142c074642157b4c22e8a085335926b2361c58ef384aa290 Release notes: https://adguard.com/versions/windows/release.html#version-72150890 Pin: `winget install --id AdGuard.AdGuard --version 7.21.5089.0 --exact` #### 7.21.5086.0 - x86 burn (machine): setup-7.21.5086.0.exe - url: https://static.adtidy.org/windows/setup-7.21.5086.0.exe - sha256: 4bdaf226abe9a821995f689c5ff00fee5ac68e2a1077232dfd046752120ae281 Release notes: https://adguard.com/versions/windows/release.html#version-72150860 Pin: `winget install --id AdGuard.AdGuard --version 7.21.5086.0 --exact` #### 7.21.5081.0 - x86 burn (machine): setup-7.21.5081.0.exe - url: https://static.adtidy.org/windows/setup-7.21.5081.0.exe - sha256: ba134015d330c2cdbb443ab6e9bf500122bb54cd403066e1c2de6b631b34566d Release notes: https://adguard.com/versions/windows/release.html#version-72150810 Pin: `winget install --id AdGuard.AdGuard --version 7.21.5081.0 --exact` #### 7.21.5079.0 - x86 burn (machine): setup-7.21.5079.0.exe - url: https://static.adtidy.org/windows/setup-7.21.5079.0.exe - sha256: 080fa93051738f4581175a0be95c28369d1f19dd0a0a7406f4ae52bda64dcba5 Release notes: https://adguard.com/versions/windows/release.html#version-72150790 Pin: `winget install --id AdGuard.AdGuard --version 7.21.5079.0 --exact` #### 7.20.4994.0 - x86 burn (machine): setup-7.20.4994.0.exe - url: https://static.adtidy.org/windows/setup-7.20.4994.0.exe - sha256: c428c4d90142e8186f8d2d7505b9741c60df0c1540d9b60d2772e90c3f2a4861 Release notes: https://adguard.com/versions/windows/release.html#version-72049940 Pin: `winget install --id AdGuard.AdGuard --version 7.20.4994.0 --exact` #### 7.20.4988.0 - x86 burn (machine): setup-7.20.4988.0.exe - url: https://static.adtidy.org/windows/setup-7.20.4988.0.exe - sha256: 55d79268627428904b50a2d8bb3f5024d969d2732aac8b4ac847727b929e34a4 Release notes: https://adguard.com/versions/windows/release.html#version-72049880 Pin: `winget install --id AdGuard.AdGuard --version 7.20.4988.0 --exact` #### 7.20.4966.0 - x86 burn (machine): setup-7.20.4966.0.exe - url: https://static.adtidy.org/windows/setup-7.20.4966.0.exe - sha256: a39d5e97a971dd820bebfb210298e0d9971b20dec834fdb1b150db1b2b73c5c7 Release notes: https://adguard.com/versions/windows/release.html#version-72049660 Pin: `winget install --id AdGuard.AdGuard --version 7.20.4966.0 --exact` #### 7.20.4960.0 - x86 burn (machine): setup-7.20.4960.0.exe - url: https://static.adtidy.org/windows/setup-7.20.4960.0.exe - sha256: fdb9bbd8e8f37399c9cc9fbdd7b6e7471993d71f55b830cd2de4e606377429a2 Release notes: https://adguard.com/versions/windows/release.html#version-72049600 Pin: `winget install --id AdGuard.AdGuard --version 7.20.4960.0 --exact` #### 7.19.4853.0 - x86 burn (machine): setup-7.19.4853.0.exe - url: https://static.adtidy.org/windows/setup-7.19.4853.0.exe - sha256: 520a7e1083744c33d69a6325643ec3e2f923823e35ac7c0e3322ad94a1e735a6 Release notes: https://adguard.com/versions/windows/release.html#version-71948530 Pin: `winget install --id AdGuard.AdGuard --version 7.19.4853.0 --exact` #### 7.18.4778.0 - x86 burn (machine): setup-7.18.4778.0.exe - url: https://static.adtidy.org/windows/setup-7.18.4778.0.exe - sha256: a8a030c14012fc42bd4d4fa2ad4c4631be9b3747aeccaca075383fa0b99aa005 Release notes: https://adguard.com/versions/windows/release.html#version71847780 Pin: `winget install --id AdGuard.AdGuard --version 7.18.4778.0 --exact` #### 7.18.4774.0 - x86 burn (machine): setup-7.18.4774.0.exe - url: https://static.adtidy.org/windows/setup-7.18.4774.0.exe - sha256: e339b60881bec42fb4dcd030906ce21138dc1f8d21b511539436fdd23d509310 Release notes: https://adguard.com/versions/windows/release.html#version71847740 Pin: `winget install --id AdGuard.AdGuard --version 7.18.4774.0 --exact` #### 7.17.4712.0 - x86 burn (machine): setup-7.17.4712.0.exe - url: https://static.adtidy.org/windows/setup-7.17.4712.0.exe - sha256: 04860110e3e2c7d3f255455c7deb46e86f836527c30f945b7de7845bfdcff6b7 Release notes: https://adguard.com/versions/windows/release.html#version71747120 Pin: `winget install --id AdGuard.AdGuard --version 7.17.4712.0 --exact` #### 7.17.4709.0 - x86 burn (machine): setup-7.17.4709.0.exe - url: https://static.adtidy.org/windows/setup-7.17.4709.0.exe - sha256: a1a7770a4a95ec62a4c87d8ab463a908cc7bd94b60cd374f504727c2b1f2eb19 Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.17.4709.0 --exact` #### 7.17.4705.0 - x86 burn (machine): setup-7.17.4705.0.exe - url: https://static.adtidy.org/windows/setup-7.17.4705.0.exe - sha256: fa2e1b4a0ad073778dcba1fad7e311ce5b1a05bbbf5167535f3fbcf4bd812930 Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.17.4705.0 --exact` #### 7.16.4542.0 — 2023-12-22 - x64 exe (machine): setup-7.16.4542.0.exe - url: https://static.adtidy.org/windows/setup-7.16.4542.0.exe - sha256: 0e9a49cb0322126cd09c24d4642f2b0578f400e096363eb0c9463e0e6a2cf276 Release notes: 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.Filtering log *mobileAs 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 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 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 Scriptlets to v1.9.101 Improvements Handle uBO's syntax $redirect priorities #59 Improved xml-prune — support xpath for text content matching #325 Improved json-prune — stack #348 Improved prevent-xhr — multiple requests #347 Added API method to convert redirects based on their name #346 Added new trusted scriptlet trusted-prune-inbound-object #372 Added more supported values for set-cookie #375 Improved set-local-storage-item, set-session-storage-item — added support “on” and “off” #366 Improved storage item scriptlets — added regexp support for items removing #256 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 set-constant scriptlet breaks vimeo.com #380 Fixed set-constant scriptlet when maximum call stack size is exceeded #373​* Fixed set-constant — no value override #330 Fixed trusted-replace-xhr-response — breakage on music.youtube.com #359 Improved m3u-prune — content is not pruned if contains carriage return #354 Improved trusted-replace-fetch-response — do not replace content if URL is set by Object.defineProperty #367 Escaped commas in the params during conversion to uBO rules #343 Fixed googletagservices-gpt — setPrivacySettings() #344​ UserscriptsWrapper ​* Updated UserscriptsWrapper to v1.2.21 The 网盘直链下载助手 userscript is not working with AdGuard #1780 Pin: `winget install --id AdGuard.AdGuard --version 7.16.4542.0 --exact` #### 7.15.4386.0 — 2023-10-24 - x86 burn (machine): setup-7.15.4386.0.exe - url: https://static.adtidy.org/windows/setup-7.15.4386.0.exe - sha256: 3d2db17155efd9b8b2a603db621340e99b71a2070dd78edcfdc111f2bdcff5a9 Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.15.4386.0 --exact` #### 7.15.4385.0 - x86 burn (machine): setup-7.15.4385.0.exe - url: https://static.adtidy.org/windows/setup-7.15.4385.0.exe - sha256: 51ea9b79789de4d6f53e2c53c196e5003a11d8942f90ea6816ce994e8e54a6fa Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.15.4385.0 --exact` #### 7.14.4316.0 — 2023-07-27 - x86 burn (machine): setup-7.14.4316.0.exe - url: https://static.adtidy.org/windows/setup-7.14.4316.0.exe - sha256: 8f537d20133e2dcafe4cf8abba995288ac98400c783b81070093fea6347176c1 Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.14.4316.0 --exact` #### 7.13.4287.0 - x86 burn (machine): setup-7.13.4287.0.exe - url: https://static.adtidy.org/windows/setup-7.13.4287.0.exe - sha256: 7303b19949322b903629e7adf4c98e3e214c08d2d3024085091e07c92b3514c0 Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.13.4287.0 --exact` #### 7.13.4278.0 - x86 burn (machine): setup-7.13.4278.0.exe - url: https://static.adtidy.org/windows/setup-7.13.4278.0.exe - sha256: 82f4b9a2caf64baef51b68a13c3c60ccb55bfbe4744f451c0b2cc57cc69bc34a Release notes: https://adguard.com/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.13.4278.0 --exact` #### 7.13.4266.0 - x86 burn (machine): setup-7.13.4266.0.exe - url: https://static.adtidy.org/windows/setup-7.13.4266.0.exe - sha256: e6acb13fa04fd37249a600eb2b376eaa3832b4c75bf21d28c9a3b526307e1658 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.13.4266.0 --exact` #### 7.12.4170.0 - x86 burn (machine): setup-7.12.4170.0.exe - url: https://static.adtidy.org/windows/setup-7.12.4170.0.exe - sha256: 904513f212a7dc2d9232c85e924ad002f1003410190e0e6ae1b299f2e5562a65 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.12.4170.0 --exact` #### 7.11.4107.0 - x86 burn (machine): setup-7.11.4107.0.exe - url: https://static.adtidy.org/windows/setup-7.11.4107.0.exe - sha256: b4ca6d6d7db4137bb2ad7dd844cca7665abe984f2191f4c3f8eab5fe47ca7462 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.11.4107.0 --exact` #### 7.11.4095.0 - x86 burn (machine): setup-7.11.4095.0.exe - url: https://static.adtidy.org/windows/setup-7.11.4095.0.exe - sha256: e859977815b9cda027fba99b1e775a86a3802b6b0f12252b2bdabf15b8a7fab7 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.11.4095.0 --exact` #### 7.11.4078.0 - x86 burn (machine): setup-7.11.4078.0.exe - url: https://static.adtidy.org/windows/setup-7.11.4078.0.exe - sha256: 43b30f8d8ef5d51af6cec19073b39b8d39907136baea1e49e3ae602fbd5352f8 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.11.4078.0 --exact` #### 7.10.3961.0 - x86 burn (machine): setup-7.10.3961.0.exe - url: https://static.adtidy.org/windows/setup-7.10.3961.0.exe - sha256: 8f43832cf2688181f92719d53a700a0a1fe7f6736a34d6b1acdcbeb431b8e8c1 Release notes: https://adguard.com/en/versions/windows/release.html Pin: `winget install --id AdGuard.AdGuard --version 7.10.3961.0 --exact` ## macOS ### What the installer does - Delivered as a disk image (.dmg) for Apple silicon and Intel. - Runs the installer package `AdGuard.pkg`; package installers usually ask for an administrator password and can place files anywhere on the system. - Requires macOS 12 or later. - The app updates itself, so it may be newer than the version Homebrew lists. - On uninstall, Homebrew asks the app to quit, stops background services, forgets installer package receipts, and deletes 3 extra files. - A full “zap” removal also deletes up to 14 support, cache and preference locations in your home folder. ### Versions (newest first) — Homebrew lists only the current release #### 2.20.3.2633 - universal dmg: AdGuard-2.20.3.2633.dmg - url: https://static.adguard.com/mac/release/AdGuard-2.20.3.2633.dmg - sha256: 8a9126a4fa60e2344dd8a7d9859ecea2e97a6131a7effcf799900a6c9b6a9a9d Install: `brew install --cask adguard`