No thanks, I can live without AdGuard, as you said WebView wasn't necessary in the past now it is, I don't want WebView on, Its personal choice?Just install WebView 2 and you can use Adguard again.
No thanks, I can live without AdGuard, as you said WebView wasn't necessary in the past now it is, I don't want WebView on, Its personal choice?Just install WebView 2 and you can use Adguard again.
Work on version 8.0 is in full swing — and this beta brings a cleaner Extensions section, better userscript compatibility, and a fix for a pesky issue some Windows users encountered. As usual, we’ve updated our libraries — CoreLibs and DnsLibs — as well as drivers, fixed a bunch of bugs, and fine-tuned quite a few things along the way.
Some things in life are more complicated than they should be. App onboarding is one example. Digging through AdGuard’s settings just to make it block the right stuff is another.
We decided to turn that pain into convenience. Meet the wizard — a simple, few-click setup that gets AdGuard working exactly the way you want, right from the start.
Quickly click through the options to:
- Block ads in your language and remove intrusive website self-promotions;
- Choose your tracker protection level — hardcore or just enough to stay comfy;
- Hide popups and widgets (if you prefer the Internet without them);
- Enable phishing protection to block dangerous websites;
- Turn on HTTPS filtering — essential for effective ad blocking on modern websites.
Beta number four is all about smoother setup and better control over network drivers.
In the previous beta, we added an improved setup wizard. It had some bugs that we quickly fixed, so now the onboarding process will be smooth.
We’ve also updated the network settings. The Use WFP driver radio button is now replaced with a dedicated screen where you can choose the driver you need. By default, we recommend WFP, as it’s more modern, reliable, and fully compatible with the latest Chromium-based browsers, which no longer work well with TDI.
A new network driver
Old drivers had issues: WFP could sometimes show instability for some users, and TDI is outdated and could occasionally cause filtering problems in browsers. That’s why we’ve added a new network driver — SockFilter.
What the new driver brings
SockFilter is still experimental, but it’s designed to bring real improvements over older drivers:
You can enable SockFilter in Settings → App settings → Network → Network driver. You can also switch back to WFP or TDI at any time. Feedback is welcome — it helps us make it better.
- Better compatibility with network apps: VPNs, firewalls, and antivirus software work together more smoothly, reducing conflicts.
- Lower risk of crashes: Operates in a safer part of Windows networking, helping prevent BSODs and other system errors.
- More stability overall: Handles traffic closer to how apps normally use the network, reducing complexity and making AdGuard more reliable day to day.
Windows 8 and 8.1 support ends
Starting with this beta, we’re dropping support for Windows 8 and 8.1. Why now?
These versions are no longer updated by Microsoft itself. Many libraries, development tools, and security technologies now target more modern operating systems. Continuing to support Windows 8 and 8.1 would prevent us from fully using them. By focusing on the latest Windows versions, we can speed up development and make AdGuard more stable overall.
Beta 6 focuses on squashing bugs and optimizing performance, bringing us another step closer to the official v8.0 release.
A huge thank you to everyone sending in bug reports — your feedback is exactly what helps us polish the app.