Good news, everyone!
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 Adguard 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.
Below you can read about all the fixes and additions introduced in the new version. Most important of them, as usual, are described in detail.
We couldn’t select any one of these changes, as they are all small enough improvements, but make a noticeable ‘quality-of-life’ difference once put together.
[Changed] Adguard uses native-style tray menu now #1006
[Changed] Adguard window is now opened with a single click on tray menu #1030
[Fixed] ‘About’ window content is not flickering anymore #954
[Fixed] Empty strings are now removed when importing user filter #973
[Fixed] Error previously encountered while installing a userstyle #934
[Improved] Proxy name validator now recognizes domain names and not only IP addresses #931
[Improved] Added $stealth modifier that disables Stealth Mode for the specified website #339
As we already mentioned in our blog, separate whitelist for Stealth Mode is on our roadmap. It is a much needed feature for anyone who actively uses Stealth Mode. We are not quite there yet, but we made a big step in the right direction by implementing $stealth modifier. It works similar to all other modifiers, just add it to any exception rule and it will disable Stealth Mode for that website specifically, even if the module itself is enabled.
You can find more information about rules formatting on our website: adguard.com/filterrules.html
[Changed] Facebook windows app added to default filtered apps list #974
[Changed] $replace rules should now have higher priority than other basic rules #1023
[Fixed] Adguard does not try to filter data: URLs any more #1007
[Fixed] $domain modifier now does work for blocking WebSocket connections #998
[Fixed] Adguard now doesn’t ignore tag href attribute while constructing absolute URL #978
[Fixed] Bug when parser builds wrong absolute URL #1021
[Fixed] Error previously encountered while parsing a style tag with embedded svg #977
[Fixed] Language-specific filters are now detected properly from users keyboard layouts #401
[Improved] Adguard now can process websites names in punycode when adding them to HTTPS exclusions #962
[Added] Support for complex language codes #808
We have completely reworked applications localization system. This allowed us to significantly increase number of languages we can potentially support (this mostly concerns various dialects, alternative alphabets etc.).
[Added] Croatian language
[Improved] HTML content detection #855
Content type detection was significantly improved. This effectively means that Adguard will not interfere with those types of traffic which do not require filtering, decreasing the number of potential conflicts.
[Fixed] Web interface of TP-Link router is broken #844
Some of our users encountered problems with accessing TP-Link routers’ interface with enabled Adguard. Upon investigating this issue we discovered a serious issue with WFP driver which resulted in problems with displaying some websites. As a result, we have improved communication with some specific web-servers.
[Added] Support for HTTP method REPORT #1020
[Fixed] Adguard can now detect HTML if there is an xml declaration at the document start #011
[Fixed] ESET compatibility issue when Chrome browser would randomly hang #899
[Fixed] Data is now read to end after blocking a POST request #916
[Fixed] Issue with unexpected connection reset with TDI driver #1025
Again, nothing to put emphasis on, but we put much effort to ensure the update to v.6 will go smoothly.
[Fixed] Blank dialog while updating from 5.10 to 6.0 #924
[Fixed] CMD window is no more shown on Adguard update #935
[Fixed] An issue when update errors were shown as valid updates in tray notification #993
[Fixed] Adguard now detects Chrome in ‘Filtered apps’ on Windows 10 insider build #972
Keep in mind that the update to Adguard 6 will now be automatic, but you can still download this version directly at this link: setup.exe
We hope you like our new features, and if you were unlucky to encounter any problems before, we hope they are gone with this new version!
UPDATE: as it often happens, there turned out to be a couple of unnoticed bugs in the last version. So we released a hotfix v.6.0.226. It contains just a couple of fixes, most noticeable is
#1042: a bugfix for indefinite loading of some routers’ pages
[Fixed] Rare problem when Adguard crashes after clicking on tray menu icon #1045
[Fixed] Adguard will not crash any more if you switch tabs while have active search on ‘Settings’ screen #1043
[Fixed] Adguard now detects HTML correctly for all websites if there is an xml declaration at the document start #1011
This version can be downloaded at this link.