How to? Error updating from 20.00.16 to 20.00.21

[casterle]

Updating via the option dialog on Win 7 x64.

Error: Update installation was blocked, digital signature mismatch.

What does this mean and how to if install the update?

 

[Charles Dye]

I would download the installer from the web site and try that:
https://jpsoft.com/downloads/v20/tcmd.exe

 

[casterle]

I would download the installer from the web site and try that:
https://jpsoft.com/downloads/v20/tcmd.exe

Thanks, that worked.

 

[Charles Dye]

Glad it worked for you. (Especially since I don't have a plan B!)

 

[K_Meinhard]

Same problem. Your solution worked for me, too, however...

Now TCMD says "the test version has expired..." and my key is no longer working. Do I need a new key?

 

[rconn]

Same problem. Your solution worked for me, too, however...

Now TCMD says "the test version has expired..." and my key is no longer working. Do I need a new key?

The registration key hasn't changed. The key is in a file in "C:\ProgramData\JP Software\TakeCommand.20.0.key" -- did you delete that file (or directory)?

 

[K_Meinhard]

No, I have the directory and file, and it says

[Take Command v20.0 Registration]
Key=US***************************B

(with most of the key edited out here)

Works as usual with my V17, not at all after the manually downloaded V21 install.

 

[rconn]

Did you try re-registering? If that doesn't work, send your key to support@jpsoft.com and I'll check to see if it's been corrupted.

 

[K_Meinhard]

Hallo Rex,

no, I didn't. The key worked fine befor with V.20.17, and does so again now that I have reinstalled that version.

And I see that I am not alone with this problem. I'll have a look again after the weekend.

 

[rconn]

no, I didn't. The key worked fine befor with V.20.17, and does so again now that I have reinstalled that version.

And I see that I am not alone with this problem. I'll have a look again after the weekend.

AFAIK, nobody else has reported a problem with the registration key after an update.

 

[MaartenG]

Glad it worked for you. (Especially since I don't have a plan B!)

A possible "Plan B" (also mentioned in another thread):

You could -as a workaround- temporary disable the Signature check:
by editing Updater.ini and then start the update procedure again

Updater.ini
;Flags=PerMachine|ShowConfigOptionsButton|VerifyDigitalSignature
Flags=PerMachine|ShowConfigOptionsButton