HTTPS fails in Edge with AdGuard after Win 10 Anniversary Update

[Andrija Kovačević]

After installing Windows 10 Anniversary Update, all HTTPS requests from Microsoft Edge are failing (as if there's no Internet connection).
HTTPS is regularly working from other browsers (including Internet Explorer 11).

When AdGuard is turned off, Edge starts working correctly.
AdGuard version is 6.1.258.1302.

Not sure if it's related, but the automatic update to 6.1.258.1302 failed to install (tried several times - download always stopped at 98%). Instead, I downloaded the latest version from the website, and installed it manually (without any issues).
The AdGuard update was applied just before Windows 10 Anniversary Update was installed. I'm not sure if Edge was working properly after the AdGuard update (tried it only after the Windows Update)

 

[aegis]

Hi. Do you have any antiviruses installed? They might scan HTTPS\SSL and break the filtering for us, try disabling this feature.

 

[Andrija Kovačević]

I do have Kaspersky Anti-Virus 2016 installed, but the problem with Edge is there even if I disable it.
In other browsers (Opera, Firefox, Internet Explorer) Adguard is filtering HTTPS without issues with KAV enabled, so I doubt KAV is the cause.

 

[avatar]

Please check Edge advanced settings. Is "Enable TCP FastOpen" checked or not?

 

[Andrija Kovačević]

It was not checked. I tried checking it, but it didn't make any difference.

 

[ram1220]

I had the same problem with Win 10 while using Kaspersky Anti Virus. I ended up uninstalling Kapersky and installing Eset Anti Virus. I then had the same problem. The only way to solve it was to turn off https filtering in Eset. Making changes within Adguard had no effect. I think something is conflicting with Adguard and other Antivirus programs. But like I said turning off https filtering in Eset and leaving it enabled in Adguard solved the problem. OP might try disabling https filtering in Kaspersky.

 

[avatar]

but the problem with Edge is there even if I disable it.

The whole Kaspersky protection? It may be that disabling "SSL scanning" may still be necessary.

 

[avatar]

In fact it would be better if you record Adguard debug log, in this case i'll be able to say something for sure.

To do it:
1. AG tray menu -> advanced -> logging level -> debug
2. Reproduce the issue
3. Send a message from the Adguard application (with logs attached)

I'll need to know your customer ID to find the ticket.

 

[avatar]

According to the log it looks like server closes connection immediately after receiving the very first data packet with "ClientHello" (part of the SSL handshake).

I still think the issue is caused by Adguard-Kaspersky SSL scan incompatibility.

Here is how to turn it off in KIS:
https://github.com/AdguardTeam/AdguardForWindows/issues/459#issuecomment-155412405

Could you please try it?

 

[Andrija Kovačević]

Yep, apparently that's the issue. After disabling KAV HTTPS filtering Edge started working again.
I see that the fix is in the pipeline, has is passed the alpha stage yet?

 

[avatar]

I see that the fix is in the pipeline, has is passed the alpha stage yet?

The problem here is that it cannot be simply "fixed" as this is a WFP technology bug.

To circumvent it we are developing new driver working on a lower level. I suppose it will take a month or so till this new driver is ready for the alpha test.