AdGuard పాత వెర్షన్లు డౌన్‌లోడ్

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

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

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.

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 

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

This is a technical update aimed to increase the app stability and fix minor bugs.

Here’s an additional technical update following the previous one. In it, we’ve fixed bugs and kept working on the app stability.

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

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.

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

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.

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.

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!

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

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
Mi