7.4 beta 1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Here comes the first beta for AdGuard for Windows v.7.4! The bottom line is we’re replacing our current Assistant with a separate browser extension called AdGuard Browser Assistant. The new Assistant has easy-to-use functionality, plus, we’ve added new UI features that make it more pleasant in use. Spoiler: you no longer need the previous browser extension. Download this new one and, paired with the main app, it will turn into a magic Assistant.

Browser Assistant

By developing this new product, we've resolved a couple of pretty important issues:

1. Ensured that the bundle of the main AdGuard app and this new browser extension is fully functional
2. Added settings in the main AdGuard app making it super easy to download or check if the extension is enabled right from it.
3. The improved onboarding process for those who downloads AdGuard for the first time.

[Added] Browser Assistant #2985

Meet our new AdGuard Browser Assistant! From a mere user script in AdGuard desktop programs it has evolved to become a full-fledged browser extension!

Obviously, new Assistant has the functions of the old one included but it’s far more cool and user-friendly. And it came in extremely handy, helping us solve three major problems at once:

• Former AdGuard Assistant was a dependent user script able to communicate with the program using a certain protocol. On the contrary, the new BA is independent: it’s installed in a browser, and you don’t need to wait while user script would be injected into the filtered web page. Putting it simply, it is more autonomous and it doesn’t depend on the main AdGuard app. The app is required for the full capacity but technically the new BA can be used without the app.
• When desktop AdGuard program and browser extension were used in integration mode, they could hamper each other’s work. Some websites would stop being protected by the desktop program and be backed up only by the extension which has less possibilities. With the new Assistant, there is no more need to install our regular browser extension, which means there is no risk of an incompatibility.
• Some people said older Assistant’s presence at any webpage disturbed them – now the green shield icon won’t be there.

[Added] Browsers tab #3118

From now on, you can open this tab and get the Assistant for a browser you use in one click. We support all popular browsers, but in case you didn’t find your one, you can use the legacy non-extension version – it works everywhere.

[Improved] Onboarding process #3119

AdGuard determines your default browser and prompts you with a download link for the new Assistant. If your browser is not compatible with AdGuard, the legacy Assistant is automatically enabled.

Ad Blocking

[Added] Experimental filter is enabled for beta and nightly testers #3027

Network

• [Fixed] Compatibility issues
• [Fixed] AdGuard not responding after resuming from sleep mode on laptop #2861
• [Fixed] Support button returns 400 Bad Request #3155
• [Improved] Enabling HTTPS filtering for a portable FF is now easier #2735

UI

• [Added] Filtering log is on pause while import #1997
• [Added] Description for the "Launch AdGuard at system start-up" option #3082
• [Changed] Description about opening AG main window at system start-up has been reformulated #3016
• [Fixed] Advanced Editor clears user rules #2142
• [Fixed] Crash on viewing request details in filtering log #3074
• [Fixed] Wrong highlight for Stealth Mode exclusions in filtering log #3123
• [Fixed] Some windows are not centered #3127
• [Fixed] Scroll issue with touchpad in language combobox #3129
• [Fixed] Can't add apps from Blitz's subdirectory #3141
• [Fixed] License activation dialog design issues #3145
• [Fixed] No longer able to add filters that do not have a .txt extension #3165
• [Fixed] Unnecessary colon is displayed for Yandex-Turbo redirect userscript #3176
• [Improved] AdGuard GUI unnecessarily raising Windows platform timer resolution #2734

Other

• [Added] An option to hide blocked QIUC records in the filtering log #2912
• [Added] Wizard's provided filters to the pre-downloaded defaults #3162
• [Added] "What's new" screen after the major app update #3169
• [Changed] Some items have been renamed or added in the tray menu #3103
• [Fixed] Cannot report a website from Assistant when UI is not running #2138
• [Fixed] Wrong date on statistics #3015
• [Fixed] Some processes are active after AdGuard update bug installer #3126
• [Fixed] Individual userscript incompatibility #3201
• [Fixed] Browsing security notifications don’t work #3203
• [Improved] Using the current browser for the webpage opening #2099
• [Improved] Update Advanced Uninstall Utility #2940
• [Improved] Get rid of double negative in "filter EV" section #3133
• [Improved] Handling the well-known errors during installation is made more user-friendly #3163
• [Improved] Send Console and Host logs to the Sentry among with the Service logs #3172

7.3 RC 2

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

One more release candidate with some minor UI and other fixes + another CoreLibs update.

• [Fixed] Wrong request type in the filtering log #3059
• [Fixed] Buttons on the main screen are overlapping #3135
• [Fixed] Date format is incorrect with specific system language settings #3136
• [Fixed] AdGuard certificate gets installed before the user enables HTTPS filtering #3125
• [Improved] CoreLibs has been updated to v1.5.163 #3139

7.3 RC 1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

This is a textbook release candidate: a heap of bugfixes thrown together to make the current beta build more suitable for regular users. We also updated localizations and the CoreLibs engine.

Ad Blocking

• [Fixed] False link interception #3117
• [Fixed] Disabling HTTPS filtering for an app works incorrectly #3111
• [Fixed] Cookies time-to-live resets to zero #3115
• [Fixed] Automatic apps filtering gets disabled after an app update #3076

UI

• [Added] Add HTTPS filtering step to the initial wizard #3125
• [Changed] Checkbox for new rule is now shown as disabled in Filter editor #2893
• [Fixed] Diagonal resizing by dragging the bottom corners is flawed #2943
• [Fixed] Extra error entries in the log file #2875
• [Fixed] Filter descriptions in Filter editor lack spaces in Traditional Chinese localization #2853
• [Fixed] Main window now correctly reflects the time of the last filters update check and not the time of the last actual filters update #2982
• [Fixed] Incorrect placement of proxy configuration warning #3065
• [Fixed] UI performance drops when you use search on the “Add filter” screen #3090
• [Fixed] Main window is shown next to the settings wizard #3100
• [Fixed] Poor line break on Browsing Security screen #3101
• [Fixed] Repeated clicks on “Debug mode” in tray menu bring up the slow filtering warning #2996
• [Improved] Centering of icons in Settings #2727

Networking

• [Fixed] Firefox Private Network issue #2981

Other

• [Changed] AdGuard now explicitly asks the user to activate trial period #2980
• [Fixed] Crash after locale change #3108
• [Fixed] Filters metadata is not updated for some filters #3036
• [Fixed] AdGuard occasionally doesn’t delete old log files #2874
• [Fixed] Adguard.Core.Tools crashes on the app uninstall #3097
• [Improved] AdGuard now adapts its time&date format according to system settings #2945
• [Improved] CoreLibs has been updated to v1.5.151

7.3 beta 2

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

The second beta of AdGuard 7.3 for Windows focuses on fixing UI-related bugs and other UI changes.

• [Changed] Flag icons removed from the languages selector #2905
• [Changed] “Too many filters” warning now requires more enabled filters to trigger #3056
• [Changed] Legacy and regular Microsoft Edge executables separated in “Filtered Apps” #3061
• [Fixed] Reset statistics feature works incorrectly #2923
• [Fixed] Settings reset doesn’t set window mode to its default state #2924
• [Fixed] Atom text editor package installer doesn't work when protection is enabled #2988
• [Fixed] Unable to remove Spotify from the list of filtered apps #3091
• [Fixed] Several apps with the same name can’t be added to the list of filtered apps #3092

7.3 beta 1

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

As the tradition requires, the first beta for any AdGuard for Windows version is usually the biggest one, with the most amount of meaningful changes. For today, we have a long list of fixes and UI improvements. But for starters let’s have a look at the most interesting stuff: CoreLibs-related changes that will further enhance ad blocking quality, a new (but at the same time somewhat old) mode of filtering and a new option to activate AdGuard.

[Added] Scriptlets support

Scriptlets is a powerful ad blocking instrument. You can say that scriptlet is an internal script (a mini-program) that we install with the app, and then execute that script with the help of filtering rules. Putting it simply, scriptlets allow us to modify how the code of the web page behaves. As for the practical use, this helps to fight adblock circumvention, for example, and is also useful in some other cases.

[Added] $redirect and $rewrite modifiers support

They are practically the same modifiers, and they allow to substitute resources. If you are not a custom filtering rules aficionado, don't bother with it. Just know that it is yet another instrument in the hands of filter developers that helps to block ads more efficiently.

We should mention that both $redirect and $rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.

[Improved] Proxy mode can now be used alongside automatic traffic filtering #2696, #3055

Previously, you had to choose between using AdGuard to filter all traffic on the current system, or setting it up as an HTTP proxy to funnel traffic of particular apps or devices through AdGuard (but without filtering it).

Now you can have the best of both worlds, and even more: filter application and browser traffic on the current PC and at the same time use AdGuard as a filtering proxy for other devices (yes, now their traffic will be filtered too). To select the configuration you want go to Network settings.

[Added] Activating AdGuard by linking personal Account #2931

Something we’ve tested in other AdGuard products and found positive feedback is an option to activate AdGuard by linking the app with your adguard.com account. In this case, instead of entering the license key, you put in your Account credentials (login/password). The app automatically looks for a valid license key in your Account and uses it to activate AdGuard.

Ad blocking

• [Added] Enable the HARs writing as an advanced option #2402
• [Fixed] Userscript working in pre version 7 releases not working in post version 7 releases. #2937
• [Fixed]Error occurred while reloading protection, doesn't change the filtering status #2965
• [Fixed] Cannot find the file specified #2969
• [Fixed] Incompatibility between AdGuard and HTTP Debugger #2979
• [Fixed] Cannot add executable from %Appdata% to the filtering #3023
• [Fixed] Some problems with user filter #3044
• [Fixed] Cannot add $network rules to the user filter #3058
• [Fixed] Atom package installer doesn't work when protection enabled #2988
• [Fixed] Firefox Private Network issue #2981
• [Improved] Change the approach to the way how we start cert installer #2973
• [Improved] Handle SHA-1 issues #3041

Networking

• [Improved] We should check the internet availability before sending a support request #2925
• [Improved] Restore using port 0 for auto-selecting listen ports #2989

UI

• [Added] Import-export advanced settings #2964
• [Added] Trial period should be started explicitly #2980
• [Fixed]Buttons Collapse, Expand, Close look bad #2722
• [Fixed] Userscript is reported as updated if version contains a letter #2819
• [Fixed] It seems that it lacks spaces in the front & back of from" in filters editor while UI is Traditional Chinese (zh-TW)." #2853
• [Fixed] Drag&Drop issue #2961
• [Fixed]Filtering log doesn't show applied rules #2998
• [Fixed] Dark theme inner window issue #3033
• [Fixed] Wrong request type in the filtering log #3059
• [Improved] Microsoft Edge Beta cannot be added to filtered app in AFW #3060
• [Improved] Remove old strings from translations #2926
• [Improved] Improve the license check window #2939
• [Improved] AdGuard Personal CA keeps coming back #1306
• [Improved] Re-design About" screen" #2675
• [Improved] There is no link to the list of changes in the latest versions #2715
• [Improved] The text is not centered on the main screen #2716
• [Improved] Use custom adguard: scheme for adding userscripts #2838
• [Improved] Hover on maximize button looks bad #2840
• [Improved] Strip identifying information from the logs when doing export #3022

Other

• [Added] New versioning system #2896
• [Fixed] Logs rotation does not work occasionally #2874
• [Fixed] File or folder is corrupted #2984
• [Fixed] Filters metadata is not updated while filters update #3036
• [Improved] Adguard GUI unnecessarily raising Windows platform timer resolution #2734
• [Improved] Transfer GM property when the user changes the userscript's name #2739
• [Improved] Improve the Advanced Settings logic #2915
• [Improved] Get rid of obsolete /f command from tools #2920
• [Improved] Filter installer's crash report names #2971
• [Improved] Pass the empty parameter's value in the query string #3038
• [Improved] Test the release build of the new Microsoft Edge #3061

7.2.2936

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Some users reported critical compatibility issues in AdGuard 7.2, mainly with Emsisoft software. This is a hotfix that will solve these problems, and we also seized the opportunity to update CoreLibs and make some other changes.

You can help us make sure such incidents won't happen again by joining our beta testing program. Millions of AdGuard users will thank you (and you'll even get a beta tester's license key for free)!

• [Fixed] WFP driver incompatibility with Emsisoft software #2957
• [Fixed] E-mail text field issue in Support window #2951
• [Fixed] Issue on the protection startup #2952
• [Fixed] Window buttons tooltip localization #2953
• [Fixed] Couldn't enable the proxy mode #2974
• [Fixed] The port field is always highlighted #2976
• [Fixed] Advanced settings translation #2944
• [Improved] Additionally inform users about required reboot #2946
• [Improved] Added a data limit to the length of sent logs in the installer crash reporter #2968

7.2.2920

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

It’s showtime: let’s welcome AdGuard 7.2 for Windows official release.

For several months, we have been working in full swing on everything - design, performance, compatibility issues with other programs, general filtering improvement and much more. And now it’s time to tell you in detail what the new version is capable of. So let’s take a look at all changes in this update.

[Changed] Installer redesign #2574

When the visual style of your app’s installer doesn’t fit the visual style of the app itself, it’s not good. Same as wearing sandals with socks. So we fixed it!

The new installer looks so good, sometimes we uninstall AdGuard just to look at it once more. Hope you like it just as much as we do! And if not, no big deal: you’re not going to come across it too often, hopefully.

[Added] Installer crash reporting tool #2566

One of the most annoying types of crashes, both for users and developers, is when the app crashes during the installation. Our usual crash reporting tool was useless in such cases. What’s the logical solution? Correct, to give the installer its own reporting tool!

As you can see, it looks almost exactly the same. Nothing will be sent without your consent, and you can also add a comment with the description of the problem to help our developers fix the crash faster.

[Added] “Filter localhost" advanced setting #2830

Some apps, for example antiviruses, may use localhost for interactions between their components. In rare cases it could lead to compatibility problems. Now it’s possible to manage filtering of localhost with the help of the new setting.

Be sure that you know what you’re doing before messing with any of the advanced settings!

You can find this setting among advanced settings. By default, it’s disabled. We advise to try to enable it only if you experience very serious issues, e.g. when web pages don’t load or there’s no internet connection.

Ad blocking

• [Fixed] Stealth mode settings reset after the app update #2839
• [Fixed] HTTPS filtering is disabled by default for the newly added applications #2846
• [Improved] Automatic filters detection algorithm #2692
• [Improved] Automatic detection of certificate issues in Firefox #2782
• [Fixed] AdGuard does not filter Iridium browser #2918
• [Fixed] Incompatibility with Epic Browser #2927
• [Improved] Update Assistant and Wot to 4.3.18 and 1.1.16 respectively #2942

Networking

• [Fixed] AdGuard closes connections after a reconfiguration #2841
• [Fixed] Connection errors on Windows 10 #2843
• [Improved] WFP/TDI drivers have been updated #2889

UI

• [Changed] Selector color in dark mode #2749
• [Changed] Now separate windows are used for Support and About dialogues #2619
• [Changed] Blocked stun/turn requests now have a prefix in the Filtering log #2638
• [Changed] Users can now access Settings, About and Support windows even when protection failed to start #2892
• [Changed] “Use localhost for injections” setting has been renamed to “Intercept TCP connection requests" #2859
• [Fixed] Minor interface issues #2761
• [Fixed] Issues with accessibility for visually impaired users #2682
• [Fixed] Cropped text on the filters update screen #2698
• [Fixed] AdGuard GUI unnecessarily raises Windows platform timer resolution #2734
• [Fixed] Some text is not visible in dark theme #2767
• [Fixed] Date on the filters update screen goes beyond the frame #2849
• [Fixed] Fixed support menu window (UI) #2910
• [Improved] Check for email validation before submitting a support request #2911
• [Fixed] Uninstallation via uninstall shortcut #2916
• [Improved] UI elements should be aligned #2922

Other

• [Changed] Atom browser has been added to the list of apps filtered by default #2688
• [Changed] Localizations have been updated
• [Fixed] Post-installation notification sequence #2750
• [Fixed] Switching between update channels is carried out improperly #2806
• [Fixed] The application doesn’t start after the update #2798
• [Fixed] AdGuard hangs after the update #2856
• [Fixed] Information about old installers is stored in %ProgramData% #2869
• [Fixed] Filter update notification does not disappear on Windows 7 #2873
• [Fixed] AdGuard does not handle alphanumeric versions properly #2876
• [Fixed] Compatibility issues
• [Improved] Handling of filter subscription detections #2517
• [Improved] Translations update

7.2.2916.1 RC

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

This release candidate contains small but important changes - all major fixes were in the previous Beta. This time we focused on improving the user interface and worked with compatibility with some browsers.

• Fixed support menu window (UI) #2910
• Check for email validation before submitting a support request #2911
• Failed test: Uninstallation via uninstall shortcut #2916
• AdGuard does not filter Iridium browser #2918
• UI elements should be aligned #2922
• Incompatibility with Epic Browser #2927

7.2.2903.6 Beta

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Time to move our Windows app forward! In the first v7.2 beta we introduce such absolute bangers as new installer design, installer crash reporting tool and new “Filter localhost” setting. Joking aside, while those might be not the most exciting changes, they are certainly useful and overall nice to have. We also did a good amount of dirty work in terms of bug hunting, crash fixing and so on.

[Changed] Installer redesign #2574

When the visual style of your app’s installer doesn’t fit the visual style of the app itself, it’s not good. Same as wearing sandals with socks. So we fixed it!

New installer looks so good, sometimes we uninstall AdGuard just to look at it once more. Hope you like it just as much as we do! And if not, no big deal: you’re not going to come across it too often, hopefully.

[Added] Installer crash reporting tool #2566

One of the most annoying types of crashes, both for users and developers, is when the app crashes during the installation. Our usual crash reporting tool was useless in such cases. What’s the logical solution? Correct, to give the installer its own reporting tool!

As you can see, it looks almost exactly the same. Nothing will be sent without your consent, and you can also add a comment with the description of the problem to help our developers fix the crash faster.

[Added] “Filter localhost" advanced setting #2830

Some apps, for example antiviruses, may use localhost for interactions between their components. In rare cases it could lead to compatibility problems. Now it’s possible to manage filtering of localhost with the help of the new setting.

Be sure that you know what you’re doing before messing with any of the advanced settings!

You can find this setting among advanced settings. By default, it’s disabled. We advise to try to enable it only if you experience very serious issues, e.g. when web pages don’t load or there’s no internet connection.

Ad blocking

• [Fixed] Stealth mode settings reset after the app update #2839
• [Fixed] HTTPS filtering is disabled by default for the newly added applications #2846
• [Improved] Automatic filters detection algorithm #2692
• [Improved] Automatic detection of certificate issues in Firefox #2782

Networking

• [Fixed] AdGuard closes connections after a reconfiguration #2841
• [Fixed] Connection errors on Windows 10 #2843
• [Improved] WFP/TDI drivers have been updated #2889

UI

• [Changed] Selector color in dark mode #2749
• [Changed] Now separate windows are used for Support and About dialogues #2619
• [Changed] Blocked stun/turn requests now have a prefix in the Filtering log #2638
• [Changed] Users can now access Settings, About and Support windows even when protection failed to start #2892
• [Changed] “Use localhost for injections” setting has been renamed to “Intercept TCP connection requests" #2859
• [Fixed] Minor interface issues #2761
• [Fixed] Issues with accessibility for visually impaired users #2682
• [Fixed] Cropped text on the filters update screen #2698
• [Fixed] AdGuard GUI unnecessarily raises Windows platform timer resolution #2734
• [Fixed] Some text is not visible in dark theme #2767
• [Fixed] Date on the filters update screen goes beyond the frame #2849

Other

• [Changed] Atom browser has been added to the list of apps filtered by default #2688
• [Changed] Localizations have been updated
• [Fixed] Post-installation notification sequence #2750
• [Fixed] Switching between update channels is carried out improperly #2806
• [Fixed] The application doesn’t start after the update #2798
• [Fixed] AdGuard hangs after the update #2856
• [Fixed] Information about old installers is stored in %ProgramData% #2869
• [Fixed] Filter update notification does not disappear on Windows 7 #2873
• [Fixed] AdGuard does not handle alphanumeric versions properly #2876
• [Fixed] Compatibility issues
• [Improved] Handling of filter subscription detections #2517

7.1.2817

Disclaimer AdGuard for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

Usually, new stable versions are preceded with a number of betas and take longer than a month to develop. But this one is a bit different, its purpose is mainly to fix some incompatibilities (such as Windscribe VPN), so it makes a lot of sense to release this version as soon as possible. It should also spark interest in Firefox users, as we addressed several certificate-related problems unique to that browser.

Ad blocking

• [Fixed] Manual blocker options bug #2677

Network

• [Fixed] AG certificate is not removed on the app uninstall or reinstall #2772
• [Fixed] Certificate gets installed into the wrong system storage #2756
• [Fixed] Compatibility issues with Sophos AV #2710
• [Fixed] Cookies are getting removed even though self-destructing cookies options are disabled #2714
• [Fixed] Windscribe extension compatibility #2703

UI

• [Changed] Domain name is now shown in the filtering log in all cases when it's detected #2691
• [Changed] Translations have been updated #2697
• [Fixed] AdGuard settings respond slowly when Parental Control is enabled #2687
• [Fixed] Release channel label is missing #2695

Other

• [Fixed] "Hide User-Agent" flag state is not passed properly to web reporter #2732
• [Fixed] AdGuard crashes randomly when you open settings #2685
• [Fixed] Userscripts' update channels don't match app's release channel #2694