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. Why is it so important? Read further.
So, what is there for me in this network driver, you might ask? Well, it fixes an old compatibility issue with several popular antivirus programs. It will make many of our users’ lives much easier — which means our lives too :) For sure, there are other fixes and changes as well, and you will find the whole list below.
[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.
And that’s all for now! How did the update go for you? How do you find the new version? Let us know in the comments section.