Releases: AdguardTeam/AdguardForWindows
6.2.436.2170 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.
The first build (release candidate) after the major release brings some quick UI and compatibility fixes.
Networking
[Fixed] Connect to 66.ru failed: ERR_CONNECTION_CLOSED #1991
[Fixed] Can't send pictures in desktop Viber app #1990
Other
[Fixed] Fix the translation for the 'Get Premium' tile #1999
[Fixed] Baofeng video software compatibility issue #1993
[Fixed] Several userscripts compatibility issues #1986
6.2.433.2167
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
Hello! You'd better hold on something because we are about to drop the biggest changelog you have ever seen! It may be overwhelming if you haven't monitored the beta releases — we reworked Filtering log and Filter editor, gave Assistant a new look, integrated AdGuard with Windows 10 notifications center, majorly improved several extensions... The list goes on and on. Just hop in and see for yourself.
Let's start with UI changes. Both Filtering log and Filter editor have been seriously redesigned. We need to say a big 'thank you' to everyone who has expressed his or her opinion because few changes depend as heavily on users' feedback as these.
[Changed] Filtering log rework #96
We know for certain that quite a few of our users are actively using Filtering log — both for creating new custom rules and generally knowing what's going on. So why not help them a bit? It has undergone a major renovation. New Filtering log overlaps with Filter editor a great bit, for example, you can create new rules and unblock blocked requests right therefrom.
There are more details to see about each request, too. The request details dialog window is very reminiscent of the Developer tools in Chrome browser. All in all, the new Filtering log is much more than a simple list of which requests are blocked and which are not.
[Changed] Filter editor rework #1293
Filter editor has also changed for the best. The addition of an 'Edit mode' allows replacing the data grid with a text area. This lets you copy/paste/delete many rules at once without having to bother with export/import.
Basic hotkeys are now available, which will speed up the process of working with the filter editor. There are many other quality of life changes, especially to the UI, which will draw your attention as soon as you launch the new version.
[Added] Integration with Windows 10 notifications center #1554
Many Windows 10 users find the Notification center to be helpful when it comes to tracking the activity of their apps. We have finally decided to take advantage of it and integrated AdGuard with the center. AdGuard has a surprisingly decent amount of various notifications. Just to name a few: notifications related to the license/trial period, automatic filter activations, new rules in User filter, Safebrowsing triggers, update checks results, etc. If you use Windows 10, you'll be able to find them all in one place now, thus making it much easier to keep up with what's going on with AdGuard.
[Changed] Network settings moved to a separate settings tab #1404
This one is rather straightforward. Previously, all network settings were crowding inside the 'General settings' tab making it harder to scroll up in down, searching for the one setting you need. Adding a separate first-level tab makes it easier to navigate through the app.
Assistant and other extensions
While not being an integral part of AdGuard for Windows, some extensions (or userscripts) have grown over time to become strongly associated with it. And we showed them some love!
AdGuard Assistant
A lot has been done in terms of improving AdGuard Assistant, and a lot more is planned for the future, so we decided to allocate it a separate, own GitHub repository: https://github.com/AdguardTeam/AdguardAssistant/
By the way, you may notice that the 'Report website' button now leads to a whole new page. Basically, what you see is a web reporting tool that allows you to easily send us a report on anything from a missed ad to a false positive. More about this later.
What else is done already? The biggest change is the ability to drag the Assistant icon across the page and place it wherever you see fit. Moreover, AdGuard will memorize the position of the Assistant icon for each website separately, so you can really customize it according to your taste and preferences.
The Assistant interface overall has become smaller but retained full functionality compared to earlier versions. There is even one new feature: a switch for toggling the filtering on the website on and off. Previously, the Assistant wasn't shown on websites with disabled filtering, and you had to go to User filter to enable it back.
Oh, and we could use your help with translating the new Assistant. Did you know that anyone can volunteer as a translator? If you feel confident, head right here and find your native language. Don't forget to read through the translator's memo.
AdGuard PopupBlocker
[Added] AdGuard PopupBlocker extension v2.1 #1883
For quite a while now, AdGuard works as a userscript manager — you can install any script via AdGuard to use it in any browser. PopupBlocker has always been one of the 'native' userscripts that are installed by default, alongside AdGuard Assistant. Its purpose is clear — to block any unwanted pop-ups.
Previous version (v1.0) was functional but very little beyond that. We have completely redesigned the PopupBlocker. It now has advanced pop-up detection, compared to its predecessor and its alternatives, restores the initial click behavior and is invisible to other scripts. All in all, new PopupBlocker is a solid addition to your online protection suite.
By the way, it is available as a standalone script that can be used on its own with any other userscript manager. To find more information about PopupBlocker, visit its GitHub repository.
Reports web app
[Added] Integration with Reports Web App #1964
When it comes to keeping our filter lists updated, we owe our users a big one. Thanks to their timely reports of missed ads, false positives etc., AdGuard filters are always up-to-date. We want to make the process of reporting a website easy for users and informative for filter developers, that’s why we decided to integrate AdGuard for Windows with a special web reporting tool.
When you see any problem like missed ad or annoyance, click on the Assistant icon and choose “Report this website”. You will be taken to a new page and asked to fill in some information about your AdGuard settings and the nature of the problem. Good thing is that AdGuard pre-fills most of the fields automatically, so most of the job is already done for you :)
We hope this change will strengthen the feedback from our users and allow AdGuard filters to stay at the cutting edge of ad blocking technology.
Userscripts handling
[Changed] The way AdGuard handles userscripts #1714
A lot of effort has been put into improving (better to say, rethinking) the way AdGuard works with userscripts. This actually has two different aspects:
First, from now on, the communication between AdGuard and Assistant is based on WebSocket, which results in better performance. This is also perfectly applicable to AdGuard Browser extension, when it is working in the integration mode with AdGuard for Windows.
Second, we have taken a whole complex of measures that allow for any external userscripts that you install via AdGuard to show higher speed and execution stability.
Other important changes
[Added] Settings export/import #1405
A lot of users were asking for this, and finally we deliver. Now you can save your settings configuration into a file and then use it to set up AdGuard on another machine exactly how you prefer. Another implication of this is to quickly switch between different settings profiles without having to feverishly click through a dozen of tabs and checkboxes.
[Improved] A complete "Exit AdGuard" functionality was added #1509
Now users have a choice between closing AdGuard as they usually do, and closing it completely. That means closing the Windows service as well as UI, and when UI is getting started again, the service will start as well (you may be asked for the admin privileges, though).
**[Added] An option to create custo...
6.2.433.2167 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.
We know we promised the previous RC would have been the last one, but the latest Chrome update served as a cause for another bug that we felt needs to be fixed. The changes are minor.
Anyway, this version is already available for download on the website, and will be pushed to release update channel very soon.
[Fixed] content-length
duplicate header issue #1982
[Improved] GM_openInTab
to handle data URLs in chrome #1971
6.2.432.2166 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 is the last release candidate to end them all, we promise. The release is right behind the corner. The only change here is about compatibility issues with different antiviruses — a routine that has to be done before any release.
[Changed] HasConflictWithWpf
flag values have been updated #1976
6.2.431.2165 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.
Presumably, the last release candidate before the inevitable coming of AdGuard v6.2. The highlight of this version is integration with a reports web app. Read below to see what it is and why is it so cool. AdGuard default userscripts have been updated (Assistant, PopupBlocker), and other minor changes have been made too.
[Added] Integration with Reports Web App #1964
When it comes to keeping our filter lists updated, we owe our users a big one. Thanks to their timely reports of missed ads, false positives etc., AdGuard filters are always up-to-date. We want make the process of reporting a website easy for users and informative for filter developers, that’s why we decided to integrate AdGuard for Windows with a special web reporting tool.
When you see any problem like missed ad or annoyance, click on the Assistant icon and choose “Report this website”. You will be taken to a new page and asked to fill in some information about your AdGuard settings and the nature of the problem. Good thing is that AdGuard pre-fills most of the fields automatically, so most of the job is already done for you :)
We hope this change will strengthen the feedback from our users and allow AdGuard filters to stay at the cutting edge of ad blocking technology.
Ad blocking
[Fixed] Chromium is not filtered by default #1956
UI
[Fixed] Ctrl + Z
does not work in any input field #1960
[Fixed] Filter editor bug #1969
[Fixed] User filter is always empty when "Filter editor" is opened for the first time #1970
Other
[Changed] Localizations have been updated
[Fixed] Userscript is not injected #1958
[Fixed] Problematic userscript prevents others from working #1962
6.2.424.2123 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.
This beta version has a strong emphasis on extensions handling. Besides the re-introduction of AdGuard PopupBlocker userscript (that has been improved a good amount, by the way), we have changed the way we handle external userscripts. AdGuard Assistant and the integration mode of AdGuard Browser extension have been shown some love too.
That’s not the only news, of course. Four new localizations have been added, and then all the usual suspects: bugfixes, compatibility issues, minor UI tweaks.
[Added] AdGuard PopupBlocker extension v2.1 #1883
For quite a while now, AdGuard works as a userscript manager — you can install any script via AdGuard to use it in any browser. PopupBlocker has always been one of the 'native' userscripts that are installed by default, alongside AdGuard Assistant. Its purpose is clear — to block any unwanted pop-ups.
Previous version (v1.0) was functional but very little beyond that. We have completely redesigned the PopupBlocker. It now has advanced pop-up detection, compared to its predecessor and its alternatives, restores the initial click behavior and is invisible to other scripts. All in all, new PopupBlocker is a solid addition to your online protection suite.
By the way, it is available as a standalone script that can be used on its own with any other userscript manager. To find more information about PopupBlocker, visit its GitHub repository.
[Changed] The way AdGuard handles userscripts #1714
A lot of effort has been put into improving (better to say, rethinking) the way AdGuard works with userscripts. This actually has two different aspects:
First, from now on, the communication between AdGuard and Assistant is based on WebSocket, which results in better performance. This is also perfectly applicable to AdGuard Browser extension, when it is working in the integration mode with AdGuard for Windows.
Second, we have taken a whole complex of measures that allow for any external userscripts that you install via AdGuard to show higher speed and execution stability.
Related issues:
[Added] @noframes
attribute support #1895
[Fixed] Userscript wrapper breaks window functions #1869
[Fixed] GM_addStyle
implementation is not reliable #1759
[Fixed] @grant none
is not being applied #1870
[Fixed] Userscript does not run on cross-origin iframes #1892
[Fixed] cloneInto
, createObjectIn
, exportFunction
support #1875
[Fixed] instanceof
event does not work as expected #1871
[Fixed] Errors in browser console #1740
[Added] New localizations #1882
Thanks to volunteers who continuosly do an amazing job translating AdGuard into other languages, we were able to add even more localizations, such as:
- Arabic
- Bulgarian
- Danish
- Persian
Other languages localizations have been updated too.
Ad blocking
[Added] "Block third-party authorization header" Stealth Mode option #698
[Added] An option to hide Java and Flash support #1064
[Changed] The $important
modifier is now applied to rules created by enabling/disabling filtering via Assistant #1924
Networking
[Fixed] DNS is unreachable when using AdGuard #1918
[Fixed] HTTPS filtering on dropbox.com does not work sometimes #1902
[Fixed] AdGuard breaks local HTTPS connections #1896
[Fixed] Wrong ciphers order #1884
[Fixed] AdGuard 6.2.390 on Windows 10 stops browsing until user kill the process #1901
[Fixed] SHA-1 intermediate issue #1702
UI
[Added] "Storage" and "Reinstall" buttons on “Extensions” screen #1893
[Changed] Interface has been optimized for screen readers #352
[Changed] Update channel is now set to "Beta" if you install or update AdGuard to beta version #196
[Fixed] Filtering log and Filter editor windows have different styles #1920
[Fixed] Cancel button is missing #1899
[Fixed] Cannot close "validation error" dialog when editing a userscript #1894
[Fixed] Log export does not work #1900
[Fixed] A “new line” symbol is added after copying a rule in Filter editor #1878
[Fixed] Changing Advanced settings does not lead to network filtering restart #1800
Other
[Changed] Spotify app has been added to the list of apps filtered by default #1904
[Fixed] "Add application" tool in “Filtered Apps” can't detect installed Viber #1559
[Fixed] Several third-party userscripts compatibility issues
6.2.390.2018 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.
One more beta version before we are ready to present a release candidate. The biggest functionality change in this version is the new option to create custom filters which are not tied to any local file or URL - you will find more in the description.
Ad blocking
[Added] An option to create custom filters not backed with a file #1669
In addition to the usual option of adding any list by URL or loading it from a local file, you can now create independent new filters from scratch. It is possible to create several such filters, give each of them their own name and fill with any rules. As a result, you can create a set of specified filters which can be separately enabled, disabled and edited.
[Fixed] No filtering with TCP Fast Open enabled in Firefox Nightly #1867
[Improved] "ExtendedCss" module has been upgraded to v1.0.8 #1823
[Improved] Multiple filters can be automatically enabled as language-specific at once now #1758
Networking
[Changed] WoSign and StartCom Certificates have been completely deprecated #1359
[Fixed] Invalid gzip causes connection to hang #1817
[Fixed] Adguard cannot handle huge chunks properly #1772
[Fixed] Impossible to set custom IP in Stealth Mode #1828
[Improved] WebRTC detection #1831
[Improved] The strong key exchange within secure connections has been enforced #1728
UI
[Added] "Adguard service" description #422
[Changed] Program logo and "About" screen have been updated #1812
[Changed] The EULA has been updated #1824
[Changed] Graying out the disabled modules has been uniformed across the app #1827
[Fixed] Search tooltip bug #1830
[Fixed] Complete exit functionality bugs #1826
[Fixed] Remote address bug in Filtering log #1852
[Improved] Support for the PT-PT localization has been added #1640
Other
[Changed] The list of HTTPS exclusions has been updated
[Fixed] Typos #1825
[Fixed] Adguard crashes when you block a request in the filtering log #1868
6.2.379.1984 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.
New Adguard for Windows beta version is at the doorstep. Of the new additions worth highlighting is the integration with Windows 10 Notification center - find the details below. We have also paid a lot of attention to the UI - bugs fixing and general improvements.
[Added] Integration with Windows 10 notifications center #1554
Many Windows 10 users find the Notification center to be helpful when it comes to tracking the activity of their apps. We have finally decided to take advantage of it and integrated Adguard with the center. Adguard has a surprisingly decent amount of various notifications. Just to name a few: notifications related to the license/trial period, automatic filter activations, new rules in User filter, Safebrowsing triggers, update checks results, etc. If you use Windows 10, you'll be able to find them all in one place now, thus making it much easier to keep up with what's going on with Adguard.
Ad blocking
[Added] "Pure URL" functionality has been added to the Stealth Mode #356
[Changed] $webrtc rules are being ignored now #1776
[Changed] X-Requested-With
is being used now to detect object-subrequest content type #1435
[Changed] The script is not getting removed anymore if there is an $empty modifier in a rule #1789
[Fixed] Error while parsing filtering rules of a particular type #1558
[Fixed] Duplicate filtering rules #1686
Networking
[Fixed] A page is broken in IE #1591
[Fixed] Disabling HTTPS filtering breaks local.adguard.com #1792
[Fixed] Incorrect encoding was being used for the preview purposes #1741
[Improved] Custom filter updates are being validated now #1765
UI
[Added] A tooltip has been added to the "Support" window #1432
[Added] A warning in the "Filtered apps" section when Adguard is in the proxy mode #942
[Changed] Filtering log scrolling behavior #1791
[Changed] Prevent closing the editor after editing a userscript #1632
[Changed] License key symbols in the 'License' section are hidden now #627
[Changed] More details have been added to the "Adguard service" description #422
[Changed] Expiration date in the 'License' section has been made more distinguishable #674
[Fixed] Search does not work in userscript editor #1814
[Fixed] Default filters could have been deleted in filter editor #1786
[Fixed] User Filters search doesn't work in 'advanced editor' mode #1821
[Fixed] Disabling HTTPS filtering leads to duplicate entries in the filtering log #1793
[Fixed] There was a sequence of actions that could lead to the removal of User filter #1787
[Fixed] An incorrect message is shown upon checking for the updates w/o an Internet connection #1552
[Improved] More filter editor tweaks and fixes #1750, #1778
Install/Update
[Fixed] Sometimes Adguard UI is not started after an app update #1784
Other
[Changed] Whale browser has been added to the list of apps filtered by default #1770
[Changed] Swing browser has been added to the list of apps filtered by default #1769
[Changed] Bandizip app has been added to the list of apps filtered by default #1680
[Improved] Version check algorithm for filters added by URL #1431
6.2.369.1938 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.
In this beta version, we mainly concentrated on the UI changes, as we go on with tweaking the Filtering Log interface. A couple of other notable tasks here as well, for example, the addition of a complete 'Exit Adguard' functionality.
[Improved] A complete "Exit Adguard" functionality was added #1509
Now users have a choice between closing Adguard as they usually do, and closing it completely. That means closing the Windows service as well as UI, and when UI is getting started again, the service will start as well (you may be asked for the admin privileges, though).
Ad Blocking
[Fixed] Notification API isn't blocked properly #1706
[Fixed] $replace rules are applied to HTTPS sites even when HTTPS filtering is disabled #1752
UI
[Changed] Multiple Filtering Log UI changes #1750
We continue to hone the Filtering Log UI to make it as convenient for you to use, as possible. We thank everyone from Adguard forums who contributed to the discussion for their feedback.
[Added] A "Reset to defaults" button to the Extensions settings #1473
[Added] A "Preview" feature for the blocked requests in Filtering Log #1695
[Changed] Dutch localization was updated #1663
[Changed] Hebrew localization was updated #1548
[Changed] The maximum number of records in the Filtering Log was limited #1723
[Changed] All elements in Filter Editor UI are now shown as disabled until rules are fully loaded #1638
[Changed] The Filter Editor does not allow switching to other filters now when you're in the edit mode #1656
[Fixed] "Support" contact form is missing #1753
[Fixed] Crash after exiting Adguard via the tray menu #1697
[Fixed] Filters content is being written to the application log #1703
[Fixed] UI crash when disabling the service with opened Filtering Log #1751
[Fixed] Can't use 0
as a value for self-destructing cookies setting #1642
[Fixed] Closing the right pane for a blocked request in Filtering Log does not highlight the entry #1729
[Improved] Speed of searching in Filter Editor and Filtering Log was increased #1725
Networking
[Fixed] Adguard cannot filter Edge HTTPS traffic when TCP Fast Open is turned ON #1093
[Improved] Adguard doesn't recognize userscript updates when the version string is too long #1541
Other
[Fixed] Assistant settings are reset with the 3.0 -> 4.0 update #1738
[Fixed] Adguard Assistant breaks Chrome Web Store AdguardTeam/AdguardAssistant#26
[Improved] Data is now being preprocessed before the import/export #1691
[Improved] The log file is now being validated before importing #1722
[Improved] Log columns were reordered #1779
6.2.357.1887 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.
Hotfix update for version 6.2.356.1877 Beta.
- [Fixed] Sometimes it is not possible to save Assistant settings: #1718