[AdGuard for Windows] Beta v.6.0.214 R2

Status
Not open for further replies.

vasily_bagirov

Administrator
Staff member
Administrator
Hello, guys!

We have released new beta version. This beta release is mostly about network-level changes and overall stability. We hope some of the old bugs will be fixed with it, such as ones caused by lack of content detection and flaws in our WFP network driver. Also we would like to draw your attention to some big changes concerning localisation. Below you can find more details.

You can find the full description on GitHub: https://github.com/AdguardTeam/AdguardForWindows/releases

And download it at this ink: https://github.com/AdguardTeam/AdguardForWindows/releases/download/6.0.214.1066/Setup.exe

Changelog:
Code:
[SIZE=5]UI[/SIZE]

[Fixed] 'About' window content is not flickering anymore [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#954[/url] 
[Fixed] Empty strings are now removed when importing user filter [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#973[/url]
[Fixed] Error previously encountered while installing a userstyle [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#934[/url]
[Improved] Proxy name validator now recognizes domain names and not only IP addresses [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#931[/url]

[SIZE=5]Networking[/SIZE]

[Improved] HTML content detection [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#855[/url]

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 [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#844[/url]
 
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.

[Fixed] Data is now read to end after blocking a POST request [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#916[/url]

[SIZE=5]Ad Blocking[/SIZE]

[Changed] Facebook windows app added to default filtered apps list [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#974[/url]
[Fixed] Error previously encountered while parsing a style tag with embedded svg [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#977[/url]
[Fixed] Language-specific filters are now detected properly from users keyboard layouts [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#401[/url]
[Improved] Adguard now can process websites names in punycode when adding them to HTTPS exclusions [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#962[/url]

[SIZE=5]Languages & Translations[/SIZE]

[Added] Support for complex language codes [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#808[/url]

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.).

[SIZE=5]Install/Update[/SIZE]

[Fixed] Blank dialog while updating from 5.10 to 6.0 [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#924[/url]
[Fixed] CMD window is no more shown on Adguard update [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#935[/url]

[SIZE=5]Other[/SIZE]
 
[url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#914[/url], [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#927[/url],
[url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#948[/url], [url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#946[/url],
[url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#945[/url],[url=https://github.com/AdguardTeam/AdguardForWindows/issues/]#944[/url]

We wait for your comments!
 

Phonemes

Member
My Nvidia graphics driver crashed while I was updating. I started the update from Adguard's "about" window and it happened right after the download finished and Adguard's GUI closed. My screen went black for a few seconds and then it came back up with the message that the Nvidia driver had crashed and restarted. Other than that Adguard appears to have installed correctly.
I reported Nvidia crashes under a dual monitor situation a few months ago ( http://forum.adguard.com/showthread.php?8665-bluescreen-when-doubleclicking-AG-tray-icon-(AG-RC-6-0-146-791) ). I have since done away with the second monitor and haven't had any crashes since, until today.
 

mysteriously

Beta Tester & Translator
The empty space width in tray menu is not as wide as in other places.

 
Last edited by a moderator:

vasily_bagirov

Administrator
Staff member
Administrator
The empty space width in tray menu is not as wide as in other places.

We don't think it is necessary to have this field wider. I am interested in what other users think about it.

---------- Post added at 19:24 ---------- Previous post was at 19:06 ----------

My Nvidia graphics driver crashed while I was updating. I started the update from Adguard's "about" window and it happened right after the download finished and Adguard's GUI closed. My screen went black for a few seconds and then it came back up with the message that the Nvidia driver had crashed and restarted. Other than that Adguard appears to have installed correctly.
I reported Nvidia crashes under a dual monitor situation a few months ago ( http://forum.adguard.com/showthread.php?8665-bluescreen-when-doubleclicking-AG-tray-icon-(AG-RC-6-0-146-791) ). I have since done away with the second monitor and haven't had any crashes since, until today.
I added a link to your commentary to https://github.com/AdguardTeam/AdguardForWindows/issues/724
I will ask @confessor to have a look at it.
 

avatar

Administrator
Staff member
Administrator
Ok, it's 50% thinner than others, but seems to be fine :)
I've provided some details about this on github:
https://github.com/AdguardTeam/AdguardForWindows/issues/944

You know, this was bugging me since the very first AG version. For some reason .NET default tray menu component differs from windows native menu.
Thanks god today I've found a solution on strackoverflow, so I hope this will be fixed soon:)

New issue:
https://github.com/AdguardTeam/AdguardForWindows/issues/1006
 

Boo Berry

Moderator + Beta Tester
Moderator
You know, this was bugging me since the very first AG version. For some reason .NET default tray menu component differs from windows native menu.
Thanks god today I've found a solution on strackoverflow, so I hope this will be fixed soon:)
Haha, nice. :D
 

ShakedBenratzon

New Member
I am not sure but I remember you told us that you are going to rewrite the WTP drivers from the scratch and make it much better so is this it ?

Moreover what about bugs and so on .. for 6.1 update are you working on it ?

There is no progress on the GitHub

https://github.com/AdguardTeam/AdguardForWindows/milestones
88% for 6.0 R2
and AdGuard Assistance no progress also 6.1... for a few month already
 
Last edited by a moderator:

avatar

Administrator
Staff member
Administrator
I am not sure but I remember you told us that you are going to rewrite the WTP drivers from the scratch and make it much better so is this it ?
Still working on it. We are trying to fix some majors issues in the current WFP driver though.

Moreover what about bugs and so on .. for 6.1 update are you working on it ?

There is no progress on the GitHub

https://github.com/AdguardTeam/AdguardForWindows/milestones
88% for 6.0 R2
and AdGuard Assistance no progress also 6.1... for a few month already
We've decided to fix all major bugs before turning on autoupdate for those who still use v5.10 and after that we'll move on to v6.1. It appeared that there were a hell of a lot bugs and it took much time to fix all. We almost finished with it now. 10 open bugs left plus one more bug in the WFP driver (and I think I know how to fix it).

Current status:
v6.1: we'll start working on it next week. For starters we will do the proper planning, create new milestones and rearrange some issues on github.

AG Assistant: new design is ready. It will be partially used in the next browser extension version.
Also some of the work is done on extension side (Assistant and browser extension share some code).
 
Last edited by a moderator:
Status
Not open for further replies.
Top