This update might not be the biggest one, in a sense it doesn't feature any revolutionary additions or the immense number of changes. But it's surely a unique one, and it's because it is by far the most influenced by the user feedback. We sincerely thank everyone who has helped us!
It is super important for two big reasons, both concern networking/compatibility: we have *finally* fixed the compatibility issue with KIS/ESET and, also, we've fixed a certificate issue in modern Chrome versions (59+). Details below.
[Fixed] Compatibility with KIS/ESET #1565
Adguard used to have compatibility issues with such antivirus software like Kaspersky and ESET. Users had to seek for compromises: disabling SSL scanning in antivirus, disabling WFP driver or even HTTPS filtering in Adguard. The core of the problem was the WFP network driver incompatibility, and we had had plans to develop a new driver for what now seems like an eternity.
We'd already claimed to have this fixed in the previous releases, but things turned out to be more complicated. We've come through countless iterations, test builds, and driver updates, and now we are confident enough to say that this time the problem is fixed for real. No more BSODs and other funny stuff when you run Adguard alongside with KIS or ESET.
And again, we can't thank enough everyone who was willing to cope with raw test builds and provided invaluable feedback in order to help us make things right. Just look at the task - it is blowing up with comments. We are happy to have such users, you are awesome.
[Fixed] Compatibility with Chrome 59+ #1597
With big news which WFP driver compatibility fix is it could be easy to neglect other changes. And that would be so wrong! This fix, in particular, is of utmost importance. It ensures Adguard will run without problems on modern (v59+) Chrome versions. Otherwise, there would be troubles with Adguard certificate validation.
UPD: hotfix update 6.1.314 brings a fix for the bug #1569, messing with filtering when HTTPS filtering is disabled.
It was quite a while since the last Adguard for Windows release. And there are other reasons for that apart from the Christmas/New Year holidays: we'd been extensively testing the new network driver before, finally, we felt ready to include it in the new release version. But what is there for me in this network driver, you might ask? Well, it fixes an old compatibility issue with several antivirus programs. For sure, there are other fixes and changes as well, and you will find the whole list below.
You can also find all relevant information about this release (and discuss it) in our blog.
[Improved] WFP driver was updated to fix compatibility issues with KIS and ESET #1497
Previously, it was not unusual at all that Adguard would have compatibility issues with some antiviruses, and KIS and ESET being the most common ones. The workarounds existed but were far from ideal - you had had to sacrifice some parts of functionality on either Adguard or antivirus side. With updated WFP driver these conflicts will be no more, allowing users to run Adguard alongside with KIS and ESET.
[Improved] The way we respond to HTTP protocol violation #1452
It would take too long to explain technical nuances, but effectively this fixes the problem some users might have come across before: when you try to open a page and it is downloaded as a file instead.
This version should be considered as a revision of the Adguard for Windows 6.1 release. This is why you will not spot many 'major' changes - mostly bugfixes, small changes, improvements etc. More drastic changes will come eventually with 6.2 version.
[Added] $important modifier #1312
This new addition is an important one (no pun intended), but mostly relevant for creators of custom filter rules. With it's help you can give certain rules higher priority.
[Changed] WOT extension is now disabled by default #1364
Recently, an article was posted in one of the popular technology blogs, claiming that Web of Trust is selling its users' browser history to third-parties. WoT extension is preinstalled in Adguard for Windows, and although it was developed by us and is not sending any of your data to WoT, we can not leave this without a reponse. For this reason we make WoT extension disabled by default in Adguard for Windows. You can read our official stance regarding these news in our blog.
Many other minor fixes and changes. The full list can be found in descriptions to prior beta versions in our repository on GitHub.
Briefly about new Adguard for Windows version: Stealth Mode got new useful options, userscripts work better now, ad blocking became more advanced and our network drivers - more stable. All the details are below.
[Added] "Self destructing cookies" option in Stealth Mode #678
Previously Stealth Mode module provided only the option to completely block third-party cookies. Now you will not only have an ability to differ first- and third-party cookies, but also the ability to set the exact time which cookies will be kept alive for. Important note: you can still block cookies alltogether, just set the keep-alive time to '0'.
[Added] Added an option to block "Browser location API" #139
[Added] Added an option to block "Browser notifications API" #1121
Normally browsers may detect your location and use this information to prioritize specific search results or make other various suggestions based on it. With browser location API blocked this will be impossible.
Blocking browser notifications API feature works somewhat similar, but rather prevents browser from showing things like news or social media frames that pop-up in the corner of your browser.
[Improved] Content injection algorithm #1099
We completely redesigned content injection algorithm. First and foremost, this should solve issues with scripts that start when the page opens, resolve some of the known conflicts (AdsBypasser, YouTube+), and also optimize usage of scripts and ad blocker styles. Overall, a technical, but very important change.
[Added] Userscripts handling #1172
We adopted a new way of handling user.js (userscript) files. Now Adguard will automatically detect when user.js file was processed. If it is a valid userscript, Adguard will open a dialog window, offering user to install it. Of course, this setting will be optional and possible to turn off through settings.
We continue to make Adguard more easily accessible for users all over the world. This time we add two more new localizations and fix some mistakes in already existing ones.
[Improved] Network SDK was updated #1179
In reality, this implies many various fixes that concern our network drivers. It would be hard to list them all here, and most of them are rather technical anyway. For example, the WFP driver - Windows Defender compatibility issue was addressed.
[Added] Support for extended selectors #1225
This is a technical term, but what hides behind it? With extended selectors support, we can much more easily create some rules that were very, very hard to create earlier. Notably, this concerns rules required to block such things as 'Sponsored posts' on Facebook.
[Added] Extended CSS support https://github.com/AdguardTeam/ExtendedCss
This is a very important addition in terms of future (and present) possibilities that it opens for ad blocking. Extended CSS is a module for applying CSS styles with extended selection properties. Basically, it means that we will be able to select and, therefore, block some elements that we would not be able to block otherwise. Currently we support following pseudo-classes: -ext-has (:has), -ext-contains (:contains), [-ext-matches-css (:matches-css).
Dozens of minor fixes and improvements.
A hotfix after last weeks release. Previously there turned out to be several problems, including router page loading problem and other. These bugs are fixed with this version.
Good news, everyone! We haven't seen any new bugs since the latest beta version, and it means nothing else but the new stable release is arriving. During the last couple of months that had passed since the 6.0 release we were able to track quite a lot of bugs and defects, which were crucial to fix. So we concentrated on them for a while. Finally, everything seems to be fixed and we are ready to turn on the autoupdate for all our users who still use Adgguard 5.10. We were looking forward to this moment! Even if you were already using Adguard 6 and you are not as excited by these news, you should be. This release means we can finally put all our efforts into implementing cool new features you might have or have not seen in our [roadmap]. In case you missed last beta releases and respective release notes, you can catch up and read about all the fixes and additions below. Most important of them, as usual, are described in detail.
Languages and Translations
[Fixed] Issues in Windows 10 Insider Preview build caused by SHA-1 certificate used for network drivers. https://github.com/AdguardTeam/AdguardForWindows/issues/915
Let us elaborate a little on this one, since this change stands out as the most important one in this update. Recently we have noticed, with the help of our beta testers, that SHA-1 certificate previously used to sign our network drivers, was in a process of being deprecated. Effectively this means that users of Windows 10 Insider Preview were not able to enable Adguard protection. We have signed our network drivers with new certificates, and now all users will be able to run Adguard without any problems.
Languages and translations
https://github.com/AdguardTeam/AdguardForWindows/issues/883, https://github.com/AdguardTeam/AdguardForWindows/issues/852, https://github.com/AdguardTeam/AdguardForWindows/issues/839, https://github.com/AdguardTeam/AdguardForWindows/issues/873, https://github.com/AdguardTeam/AdguardForWindows/issues/868, https://github.com/AdguardTeam/AdguardForWindows/issues/851, https://github.com/AdguardTeam/AdguardForWindows/issues/898, https://github.com/AdguardTeam/AdguardForWindows/issues/848
A new update to the recently released Adguard 6 is available. It mostly contains fixes to some minor bugs we missed during the beta test. You are able to update to the latest version from your client.
It is finally time to release Adguard 6! We have put a lot of time and effort into its development, and you will see this reflected in the release notes. A lot was added, even more was improved compared to Adguard 5. New version became much more intuitive in use, functional and diverse.
You can read about new version in detail in our blog: https://blog.adguard.com/en/adguard-news/adguard-6-official-release.html
Important notice about Logjam. We do not protect you from it, just ignore such connections. Browser decides what to do with it further. So make sure you are using the latest version of your browser.
You can discuss the latest version in our blog: here.
You can discuss the latest version in our blog: here.
You can discuss the latest version in our blog.
You can discuss the latest version in our blog: here.
You can discuss this version in our blog.
Short list of important changes: greatly reduced memory usage, we introduced convenient addition of new ad filters, integration with WoT is now a separate extension, added support for new browsers, fixed conflicts with popular programs and defects in the processing of requests and more.
We have significantly optimized memory usage in 5.10. Now, even if you use an old computer or a weak netbook, Adguard will work silently in a background without slowing down your device. We compared memory footprint with the one of the preceding version. And we must say 5.10 showed a result several times lower.
In addition, Adguard has became an even more comprehensive program. Now users can install any ad filters. What does it mean? In addition to the filters that are already installed in Adguard by default, you can add third-party ones, such as a list of filters that allow Adguard to block ads in different segments of the Internet - websites in different languages, in particular. All of this can be done directly in the program, simply by selecting a filter you want and clicking on the "Add selected" button.
Integration with Web of Trust is now brought out in the separate extension, which can be disabled. Also a warning when visiting a suspicious website has changed. With the help of WoT, our Adguard is able to notify you instantly about the reputation of websites and show the reasons for which the site is considered to be suspicious. "Categories of suspicion" can be, in particular: scam, potentially illegal, misleading claims or unethical, poor customer experience, privacy risks and others.
Version 5.9 brings a large number of changes to Adguard.
In version 5.9, there is an opportunity to install extensions (userscripts). They are designed to extend the functionality of websites. How exactly will the functionality be extended depends on the particular userscript. This can be a pop-up blocking, blocking of flash requests, possibility to download music and video from social networks and much more.
You can learn more from this post in our blog.
In this version, Adguard learned to recognize most of the video ads on its own without relying on filter databases.
During the existence of the program, we have received many requests from our users about implementing the "Parental Control" in it. Many parents found Adguard helpful, because when using it the child didn’t see inappropriate advertising.
Finally, in the version 5.9 we are ready to introduce “Parental Control” - a separate module of the program.
You can learn more from this article.