AdGuard for Windows v6.1.298 R2

Status
Not open for further replies.

vasily_bagirov

Administrator
Staff member
Administrator
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.

Ad Blocking

[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] Several apps and browsers added to the list of apps filtered by default #1230, #1236, #1274, #1280, #1344, #1347
[Fixed] Inconsistent $replace result #1358
[Fixed] Adguard now filters pages with Content-Type:application/xhtml #571
[Fixed] HTTPS exceptions do not cover subdomains #1317
[Fixed] $replace rule can now be applied along with the other rules #640
[Improved] Filters update check period is now customizable #941
[Improved] Adguard now can partially block encrypted ads without decrypting SSL protocol (if HTTPs filtering is disabled) #1233

Networking

[Changed] Switched to the DigiCert certificate #1268
[Changed] WoSign and StartCom certificates became unstrusted #1359
[Changed] Proxy mode will use IPv4 address when it is available from now on #1323
[Fixed] CSP is now handled in meta tags #797
[Fixed] Issue with invalid HTML #1222
[Fixed] "iframe" elements are not removed from the page code #1245
[Fixed] Adguard.Tools.exe heavy CPU load issue #1229
[Fixed] Opera dev ad blocker compatibility issue with Adguard Assistant #1173
[Fixed] Opera built-in VPN compatibility issue #1116
[Fixed] Certificate validity check order #1277
[Fixed] SSL exceptions aren't deleted on network API reinit #1304
[Fixed] Adguard code is injected into a non-HTML document #1316
[Fixed] WFP driver impacting DPC latency #1156
[Fixed] $empty modifier behaviour #1360
[Fixed] Stealth mode ignores $stealth exception #1362
[Fixed] Inability to apply inline style #1331
[Fixed] An empty 'style' tag is added even if there's no element hiding #1336
[Fixed] $replace modifier breaks content charset #1378
[Fixed] Adsbypasser and some other userscripts do not work properly #1363
[Fixed] "Enable safe search" function in Parental Control breaks Google #1383
[Fixed] Adguard doesn't filter HTTPs when Fiddler is switched on and in "decode https" mode #1372
[Fixed] Adding a URL to temporary HTTPs exceptions is suppressed now when connection is closed from the server side #1341
[Fixed] 'access-control-allow-origin' header console error #1381
[Improved] HTTPS is now used for safebrowsing service requests #1386
[Improved] Encrypted connection is used now with api.adguard.com #1369
[Improved] Adguard styles are now protected from removing #1272
[Improved] Content type detection #1264
[Improved] Content injection algorithm was reworked #1099, #1305

UI

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

[Changed] You can now completely remove WoT extension #1364
[Changed] Unnecessary text in 'Import rules' dialog window is removed #1349
[Fixed] Filter's name isn't copied with the rest of request details #1318
[Fixed] Button size issue on the last step of Adguard wizard #1352
[Fixed] Adguard crashes if you try to close UI while editing a filter rule #1258
[Fixed] $replace rule is shown as applied to images #1392

Install/Update

[Fixed] Deleted records from HTTPs exclusions are not restored on app update anymore #904

Many other minor fixes and changes. The full list can be found in descriptions to prior beta versions in our repository on GitHub.

NOTE: currently new version is only available through the manual update. Autoupdate will be enabled for it later.
 

aegis

Administrator
Administrator
We have just published 6.1.298.1564

This version is a hotfix for third-party filters update issue. If you were using a beta version of Adguard with some third-party filters before, you have to reinstall them (delete from the list and add back again).
 

Elementman

New Member
Is it https filtering conflict with Kaspersky program fixed with this version?I have this problem on my main PC with Win10 but on my laptop with Win7 SP1 AdGuard and KIS works fine.
 

Elementman

New Member
It's only fixed with the beta version found here: https://forum.adguard.com/index.php?threads/adguard-for-windows-beta-v6-1-303-1594.19089/

Fixed as in it works with KIS 2017 and Adguard's WFP driver without the need to disable SSL scanning.
Thanks for the replz.I just tried the beta version and the problem is still there.I wasn't able to access Google page without disabling WFP driver in Adguard.I hope that this problem will be fixed in new 6.2 version.I use KIS 2016.
 

Boo Berry

Moderator + Beta Tester
Moderator
In that case it's likely not fixed in the older KIS versions, only 2017 and above. For 2016 you'll likely need to still disable SSL scanning.
 

Elementman

New Member
Thanks again.Do you maybe know why this problem is not persistent with the same KIS version on my laptop with Win7 SP1,but only on WIn10?
 

Boo Berry

Moderator + Beta Tester
Moderator
I may be mistaken, but I think Adguard on Windows 7 will default to the TDI driver, whereas on Windows 10 it defaults to the WFP driver. Ultimately the issue is a WFP incompatibility between Adguard's WFP driver and the antivirus' drivers, which was finally addressed in at least KIS 2017 and ESET 10 (and likely not backported to the older AV releases, sadly).

https://github.com/AdguardTeam/AdguardForWindows/issues/1497

In the case of ESET Internet Security 10, I can confirm it works beautifully with Adguard's WFP driver, without needing to disable SSL scanning. :D
 

superssjdan

New Member
I can also confirm it works really well with EIS 10.0.386 as well as KIS 17.0.0.611 (c).I have not observed an issues to this point.Both machines are windows 10pro x64. Have not tested with Webroot yet.Will give that a whirl later today.All browsers seem quite snappy here: IE,Edge,Chrome,Firefox,Vivaldi.
 

Sol

New Member
Win10x64Enterprise, KIS 17.0.0.611 (c) and adguard latest beta not working for me, any suggestions what to do?
 

vasily_bagirov

Administrator
Staff member
Administrator
Win10x64Enterprise, KIS 17.0.0.611 (c) and adguard latest beta not working for me, any suggestions what to do?
What exactly is the issue? We have reports from some users that the latest beta can sometimes completely shut down the internet, and we are working on a hotfix.
 

avatar

Administrator
Staff member
Administrator
Thanks for the replz.I just tried the beta version and the problem is still there.I wasn't able to access Google page without disabling WFP driver in Adguard.I hope that this problem will be fixed in new 6.2 version.I use KIS 2016.
Guys, I suppose this may be due to another issue: https://github.com/AdguardTeam/AdguardForWindows/issues/1522.

You should try it again when newer beta is ready (it should be available in a few hours).
 
Status
Not open for further replies.
Top