Microsoft Edge Certificate Prompt changes to 'Windows Security' after Kaspersky install

[paul_33]

This may be a bit of a niche issue but I wanted to see if anyone had a solution.

We use a government website that requires you to login using an Entrust PKI and when you first access the site Edge will prompt you to select your certificate. The prompt normally appears right below the Edge address bar and is easy to see.

After installing Kaspersky the prompt no longer appears in Edge, it opens a 'Windows Security' prompt that asks you to pick a certificate. After choosing one and entering your password into Entrust, it then prompts AGAIN for the same certificate despite logging in. You can even cancel this box and continue to use the site. Not the end of the world, but its going to confuse our users. Worse is that the windows security boxes open without any focus and minimized in the taskbar, so people are going to miss it entirely. 

Is there a way to disable this behaviour and go back to Edge handling the certificates? The issue does not happen until Kaspersky is installed. I tried using the Web Threat Exclusion list but it doesn't make any difference. 

[Tahmeed702]

38 minutes ago, paul_33 said:

This may be a bit of a niche issue but I wanted to see if anyone had a solution.

We use a government website that requires you to login using an Entrust PKI and when you first access the site Edge will prompt you to select your certificate. The prompt normally appears right below the Edge address bar and is easy to see.

After installing Kaspersky the prompt no longer appears in Edge, it opens a 'Windows Security' prompt that asks you to pick a certificate. After choosing one and entering your password into Entrust, it then prompts AGAIN for the same certificate despite logging in. You can even cancel this box and continue to use the site. Not the end of the world, but its going to confuse our users. Worse is that the windows security boxes open without any focus and minimized in the taskbar, so people are going to miss it entirely. 

Is there a way to disable this behaviour and go back to Edge handling the certificates? The issue does not happen until Kaspersky is installed. I tried using the Web Threat Exclusion list but it doesn't make any difference. 

Can you share some screenshots of the issue or prompt it is showing 

[paul_33]

Yes - this first one (EdgePrompt) shows how Edge normally prompts. The second (WindowsSecPrompt) shows the windows security prompt that comes up with Kaspersky installed.

On my test machines the more I cancel the prompts the issue seems to 'solve itself' for that login. Which isn't really a great fix for 100+ users

[Tahmeed702]

1 hour ago, paul_33 said:

This may be a bit of a niche issue but I wanted to see if anyone had a solution.

We use a government website that requires you to login using an Entrust PKI and when you first access the site Edge will prompt you to select your certificate. The prompt normally appears right below the Edge address bar and is easy to see.

After installing Kaspersky the prompt no longer appears in Edge, it opens a 'Windows Security' prompt that asks you to pick a certificate. After choosing one and entering your password into Entrust, it then prompts AGAIN for the same certificate despite logging in. You can even cancel this box and continue to use the site. Not the end of the world, but its going to confuse our users. Worse is that the windows security boxes open without any focus and minimized in the taskbar, so people are going to miss it entirely. 

Is there a way to disable this behaviour and go back to Edge handling the certificates? The issue does not happen until Kaspersky is installed. I tried using the Web Threat Exclusion list but it doesn't make any difference. 

Please raise a ticket https://companyaccount.kaspersky.com/

[JL - KL DACH]

Hello Paul_33,

Kaspersky Endpoint Security uses "Encrypted Connection Scan" by default.
Maybe this is the component causing the issue. Goto the policy or local settings under General Settings -> Network Settings and disable this component completely just for a test. Check if the problem happen again. If not configure it with Exclusions or use the own certificate store settings to configure your own cert.