wincmd.key not recognized in 64-bit and error on startup

[HolgerK]

2secureinoz
Another possibility:
Do you really use the totalcmd.exe from the place where you installed it ( and placed the key-file), or did you copy (by accident) Totalcmd.exe to the desktop, start menu, .. and start this copy instead?

Regards
Holger

[ghisler(Author)]

That's why I asked him to execute
cd %commander_path%

This will bring him automatically to the right location.

[HolgerK]

Yep, but so far he did not answer to your suggestion.

But with wincmnd.key in the directory where I got the installer to install Total commander

Regards
Holger

[secureinoz]

That's why I asked him to execute
cd %commander_path%

This will bring him automatically to the right location.

Thanks HolgerK and ghisler.

Sorry I did not make this clear. cd %commander_path% takes me to c:\Program Files\totalcmd\ which is where in initially had the wincmd.key file.

[Flint]

secureinoz
What about this?

[secureinoz]

secureinoz
my wincmd.key became corrupted for unknown reason (different binary contents), so I just replaced it from my backup copy and everything started working smoothly.

Thanks Flint. It worked...I just copied a backup copy of the key from my old PC over the key on my new PC and the problem disappeared.

Thanks.

[Flint]

So, it wasn't my local exclusive problem…

Christian, could you please look your code for snippets that could write into wincmd.key? (There should be at least one, when pasting the key from buffer.) It seems that TC sometimes can call them at wrong times and overwrite wincmd.key with garbage.

[ghisler(Author)]

The only time TC writes to a key is when you press Ctrl+V and the clipboard contains the key in a special text form. However, the key is written only when the key is exactly 1024 bytes, and the 4 byte checksum is correct. Therefore this cannot cause a bad key.