Quantcast
Channel: Active questions tagged windows - Super User
Viewing all articles
Browse latest Browse all 9177

WingetUI: 'the server certificate did not match the expected values' - Kaspersky Protection changes the certificate that wingetUI expects

$
0
0

The tool I use for updating all my apps on Windows 11 called wingetUI recently throws:

0x8a15005e : The server certificate did not match any of the expected values.

and it does not update the selected Apps as it is supposed to.

As it turns out my Kaspersky Protection is the source of this issue. I have to disable every single Kaspersky Protection feature so that WingetUI works properly. I have already tried to switch the enabled Kaspersky features and respectively restarting the PC, which changed nothing.

As one comment says, the issue with Kaspersky must be due to Kaspersky injecting its own certificate. This is probably because the winget enquiry is routed through a Kaspersky server on my own PC in order for the Kaspersky software to supervise it. In conclusion, wingetUI gets the server certificate of Kaspersky Protection which does not match the server certificate of the respective app and throws the error message.

Unfortunately, the issue also applies for Kaspersky Protection features that I really like to use and that actually do not supervise connections like winget e.g. Kaspersky secure payment. In conclusion, I have to wait for Kaspersky Protection to push the message 'Protection is offline' which indicates, that every single Kaspersky Protection feature is offline in order for wingetUI to work.

The issue appeared first when I enabled a few more Kaspersky Protection features than I did before. Since then, it seems like the issue appears even though I have just a single random Kaspersky Protection feature enabled, just like I described above.

Unfortunately, I don't remember which critical Kaspersky Protection features I enabled that caused the issue in the first place. However, the problem seems irreversible. So as long as Kaspersky Protection is enabled in any way, it seems to manipulate the expected server certificate.

There may be a slight chance, that the issue isn't actually due to the Kaspersky Protection features I enabled in addition to the already existing ones but to a Kaspersky Protection or WingetUI update falling on the same period. However, I find that very unlikely.

What I am trying next:

  • try if winget works fine in the shell while Kaspersky Protection is enabled, so it would be an issue exclusively for the wingetUI
  • try to enable all Kaspersky Protection features but to add wingetUI as an exception

Viewing all articles
Browse latest Browse all 9177

Trending Articles