TC 8: TCs certificate expired on Jan. 21st 2016 ?

[walker1]

I have just updated to 8.52a (from 7.04) on my new Win7 laptop.

But I still get a security warning from the system!
It looks like, the certificate for the application expired on Jan. 21st 2016!?

How do one get around that?
Or ...?

[ghisler(Author)]

Yes, the signing certificate expired on 21.1.2016. But this does NOT mean that the signature is invalid now. It only means that the certificate cannot be used to sign programs after 21.1.2016.

To verify this, the program is not only signed with the certificate, but also timestamped with the time when it was signed. Windows considers certificates as valid when the signing certificate was valid at the time when the file was signed. Totalcmd.exe and Totalcmd64.exe 8.52a were timestamped by Symantec timestamping services on 17. September 2015, well within the validity of our certificiate.

You probably have a damaged certificate store in Internet Explorer.

[walker1]

Internet Explorer? Who uses Internet Explorer?

Should I start it just for it to get something updated in Microsoft's own good time?

Or can 'whatever' be loaded from somewhere?

[ghisler(Author)]

Well, technically it's not Internet Explorer, but the Windows certificate store - and this is mainly used by Internet Explorer. Other browsers use their own certificate stores, but it's not guaranteed that any other browsers are installed.