AdGuard for Windows v6.1.314

Status
Not open for further replies.

vasily_bagirov

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

Networking

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

[Fixed] $popup rule bug #1504
[Fixed] QUIC protocol issue when KIS is installed #1482
[Fixed] HideUserSearch option breaks the 'maximize' button graphics #1536
[Fixed] 'Disable Fast Open' setting doesn't work in latest Insider Preview builds #1487
[Fixed] Several issues in Firefox with the default value of 'Hide you user-agent' setting #1493

Ad Blocking

[Added] $network basic rules modifier to solve the issue with loading ads through WebRTC #1297
[Changed] Extra Steam executables removed from the list of filtered apps #1468
[Fixed] Invalid executable for CentBrower #1453
[Fixed] $replace rules aren't applied to .m3u8 files content #1428
[Fixed] Regular expressions with $ aren't processed properly #1475
[Improved] Cosmetic exception rules compilation speed #1533

UI

[Added] A new advanced settings property to change the injection method - local or remote #1492
[Changed] Version history link in about section #1471
[Changed] Parental Control password protection is made separate for different Windows user accounts #1480

Other

[Changed] HTTPS exceptions list is updated #1532
[Changed] Opera Neon browser added to the list of filtered apps #1495
[Changed] Orbitum browser added to the list of filtered apps #1467
 

Boo Berry

Moderator + Beta Tester
Moderator
It really should be pointed out that it works with Kaspersky Internet Security 2017, ESET Smart Security 10 and ESET Internet Security 10. Earlier versions of KIS and ESET likely won't get any backported WFP driver fixes, so they likely won't work with Adguard's WFP driver.
 
I'm trialing the WFP network driver also. I would get the occasional Bluescreen now and again. If I get any with this version, I'll upload the dump files.
 

TravoreSX

New Member
Hello,
The new version Adguard blocks the network driver and crashes the browser firefox :-(
I installed on three different computers and the same problem. In the background i act and Comodo IS 2017
 

Blaz

Moderator & Translator
Staff member
Moderator
It really should be pointed out that it works with Kaspersky Internet Security 2017, ESET Smart Security 10 and ESET Internet Security 10. Earlier versions of KIS and ESET likely won't get any backported WFP driver fixes, so they likely won't work with Adguard's WFP driver.
Imho they should finally update business product (Endpoint Security 6) with a new WFP driver.
 

caleb59

Member
I'm trialing the WFP network driver also. I would get the occasional Bluescreen now and again. If I get any with this version, I'll upload the dump files.
I was so happy yesterday but today - random BSOD in my face - god damn...
Problem exist so I recommend to TURN OFF WFP DRIVER for now!
-------------------------
I've tried to submit a ticket on your support site but after 100% of upload my memory.dmp file (attachment) I've got "413 Request Entity Too Large" error on your support site...
 
Last edited:

aegis

Administrator
Administrator
We have just released v6.1.314.1628
It brings a hotfix for the bug #1569 that was messing with filtering when HTTPS filtering is disabled and Browsing security is enabled.
 

avatar

Administrator
Staff member
Administrator
It is not clear what's causing BSOD's yet, as stack trace points to other drivers.

However, changes in v6.1.314 might help with the issue. Have you tried it?
 

caleb59

Member
From your github:
The only change is fix for the bug #1569.
THE ONLY CHANGE so I don't want to see another BSOD, I prefer to wait for you to fix this problem - you have logs/dumps from other peoples too so I'm not the only one with this problem...
------------------
I've completely uninstalled and reinstalled AdGuard, I will test WFP driver ON again...
 
Last edited:

avatar

Administrator
Staff member
Administrator
you have logs/dumps from other peoples too so I'm not the only one with this problem...
Indeed, the problem is that the dump points at their driver, so I am not yet sure if we can fix this from our side.

Meanwhile, I have two ideas to check.

First: try switching "Use local injections" flag in Adguard's advanced settings (AG tray icon -> advanced -> settings..).
To check the second idea, we'll need to publish a new build.

Also, I have one more question. Do you have uTorrent or AceStream apps running?
 

caleb59

Member
ESET updated their software to version 10.0.390.0, I noticed that my BSOD is realted to ekrn.exe and this is ESET file...
Also in other bugchecks in your github I've noticed that someone else bugcheck is realted to Kaspersky software (avp.exe)...
All bugchecks are affect Windows netio.sys file, in my situation when WFP driver is OFF all is fine and problem is solved...

I have uTorrent but I run it once upon a time, it doesn't run in background but like I said - when WFP driver is OFF everything works OK...

For now I've uninstalled and reinstalled AdGuard and I'm testing v6.1.314.1628 with WFP driver ON...
 
Status
Not open for further replies.
Top