Winmerge 2.16.6 x64 and x86 signature/certificate problem

[fpr]

When we try to publish WinMerge 2.16.6 x64 and x86 version, we get the following errors:

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\eetywxs5.cbg\WinMerge-2.16.6-x64-Setup_no_support_for_per-user_installation.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:12   17812 (0x4594)

and

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\tz1xaynw.gaq\WinMerge-2.16.6-Setup.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:36   18820 (0x4984)

We are using SCCM Catalog for Updates on SCCM Server 1910 with latest hotfixes.
Is there any chance to fix it?
Thanks in advance!

[Justin Chalfant (Patch My PC)]

Unfortunately, WinMerge doesn't sign their install, so you will be unable to publish it directly using the in-console publishing feature. You can use our Publisher or SCUP as a workaround. More details about this error here: https://patchmypc.com/unsigned-updates-fail-with-error-srvmsg-sms-isvupdates-syncagent-updatecontent-trust-fail-badsig

You could also consider switching to our Publisher completely, more info here;

   What's the Difference Between Our Publishing Service and SCCM 1806+ In-Console Publishing? - https://patchmypc.com/faq-scup-catalog#publishing-service-vs-sccm-publishing

When we try to publish WinMerge 2.16.6 x64 and x86 version, we get the following errors:

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\eetywxs5.cbg\WinMerge-2.16.6-x64-Setup_no_support_for_per-user_installation.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:12   17812 (0x4594)

and

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\tz1xaynw.gaq\WinMerge-2.16.6-Setup.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:36   18820 (0x4984)

We are using SCCM Catalog for Updates on SCCM Server 1910 with latest hotfixes.
Is there any chance to fix it?
Thanks in advance!

[fpr]

Thanks for the hint!
We switched over to the publisher and that solved a lot of problems for us.
Using the publisher is really recommended in any case!