Check for Updates fails with error 80092013

Version 5.9 (Build 6786)

Choose Help > Check for Updates from the menu.

Error:

Certificate not trusted.
Error: 80092013, Chain index: 0, Element index: 0
Server certificate verification failed: issuer is not trusted

Thanks. We will take a look.

@shaun.merrill: I have the same issue

@shaun.merrill: I have the same issue.

Recently install same versión on two differents Windows 7 computers, on 64 bits doesn't works but on 32 bits works fine.

Are you all getting the exactly same error message? Including the Error: 80092013?

Do you have some 3rd party firewall or other security solution?

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

@martin: Created an account, got your email, sending you some details shortly.

We disabled SSL inspection for the WinSCP.net site on our firewall, and the check update function completes successfully.

Certificate not trusted.
Error: 80092013, Chain index: 0, Element index: 0
Server certificate verification failed: issuer is not trusted

Hello.

I have upgraded to the latest version 6.1 build 13674 on Windows 10 22H2 on a corporate network with proxy enabled.

When triggering the option to check for updates I get the following dialogue box

Error checking for application updates

Certificate not trusted
Error:80092012 Chain index: 0, Element Index: 0
Server certificate verification failed: issuer not trusted

Best regards,
Stelios

@steliosh: Do you mean the problem is new in 6.1? If you downgrade, does it go away?

No same issue was with previous version as well…

Hello.
Is there any update on why Windows 10 workstation on a corporate network with proxy enabled can not get WinSCP to update to the latest version?

Best regards,
Stelios

@steliosh: I'm sending you an email to the address you have used to register on this forum.

Hello Martin,

Have sent you an email the log file that you requested.
Seems like there is a TLS failure.

Tried to copy the certificate into a crt file and then import it into the Trusted Root Certification Authorities but the problem still persists.

Best regards,
Stelios

I have added this issue to the tracker:
Issue 2212 – Updates check fail because winscp.net certificate cannot be validated
You can vote for it there.

Hello.

Is the issue with updating the application behind corporate firewall fixed?
I have copied the certificate posted in GitHub and save it in a crt file, tried installing this onto the workstation but it still doesn’t work, same error Check for Updates fails with error 80092013"

This is happening when the corporate firewall replaces certificates of websites. And for some reasons Windows certificate store fails to validate the winscp.net replacement certificate – at least when queries the store the way WinSCP does.

Hello Martin,

Can you please elaborate on the following post (in bold)?

I cannot seem to update the application on windows 10 which is behind a corporate firewall.

Certificate not trusted.
Error: 80092012 (The revocation function was unable to check revocation for the certificate), Chain index: 0, Element index: 0
Server certificate verification failed: issuer is not trusted

But you can also use custom path via CertificateStorage value in HKCU\SOFTWARE\Martin Prikryl\WinSCP 2\Configuration\Interface.

@stelios71gr: I assume you are referring to this post:
WinSCP update certificate error

What do you want to elaborate on? What part is not clear? What do you want to achieve?

Please disregard the message. Application updated behind corporate proxy.