TOTALCMD64.EXE v11: with admin right shows "Unknown Publisher"

[RobX]

First, thanks a lot for Total Commander release v11.00 !

I am not sure if this is a problem of our company IT rules or of TC v11.00:

After upgrading to version 11.00 (from v10.52), when I start TC with admin rights, I get a warning message, saying that the publisher of "TOTALCMD64.EXE" is unknown.

I have to do an additional security login to get it started in admin mode.

In earlier versions the publisher was recognized as "Ghisler Software GmbH" and no extra login was necessary.

I upgraded two company computers to TC 11.00, same behavior on both machines.

Anybody else faced the same problem?

Thanks and best regards,
Robert

[Stefan2]

Hi and welcome 2RobX


Do it read Defender Smart Screen?

Else tell more about that dialog or ask your IT.



 

[umbra]

Confirmed. In TC 11 final, TOTALCMD64.EXE is missing a digital signature. TOTALCMD.EXE has it.

[Horst.Epp]

Confirmed
TOTALCMD64.EXE has no digital signature

[KozakMak]

Confirmed
probably, need to be moved in bug reports

[white]

Confirmed for both combined installer and 64-bit installer.

Moderator message from: white » 2023-08-03, 09:06 UTC

Moved to Bug reports forum.

[ghisler(Author)]

Confirmed, sorry for the mistake. If this is a problem for you, you can now re-download the installer with the signed exe inside.

[petermad]

Confirmed that totalcmd64.exe in the updated installers are now signed.

[Impeeza]

Confirmed, sorry for the mistake. If this is a problem for you, you can now re-download the installer with the signed exe inside.

Don't be sorry is a innocent misshapen, with tne new version no problem at all.

[RobX]

Confirmed - no more warning massage after reinstalling TC 11.00 with today's installer !
Thanks a lot for the quick action!

Although it was just a little annoyance for now, our corporate IT tightens security rules day by day.
They might block execution of programs from unknown publishers completely in near future.
And TC is THE essential program for me to get my daily work done smoothly

Best regards,
Robert

[ghisler(Author)]

I have now added a line to the batch file which builds the CAB for the installer which checks whether the executable is signed or not, and show a warning and don't build the CAB when it's unsigned. This should prevent this mishap in the future.

[Stefan2]

I have now added a line to the batch file which builds the CAB for the installer which checks whether the executable is signed or not, and show a warning and don't build the CAB when it's unsigned. This should prevent this mishap in the future.

Well done



 

[white]

I have now added a line to the batch file which builds the CAB for the installer which checks whether the executable is signed or not, and show a warning and don't build the CAB when it's unsigned.

I have seen a report where the unsigned TC was considered possible ransomware by F-Secure. The problem was solved by redownloading Total Commander (signed version).

[JOUBE]

I have now added a line to the batch file which builds the CAB for the installer which checks whether the executable is signed or not, and show a warning and don't build the CAB when it's unsigned. This should prevent this mishap in the future.

Well done

Yes, well done. Because such mistakes can always happen.