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

[ghisler(Author)]

It's indeed a calculation error in one of the assembly functions to check the key. I had to expand a variable from 32-bit to 64-bit to fix it. The fix will be in the next beta.

[Boofo]

Strange that it didn't affect everyone. Looking forward to the next version, sir.

[ghisler(Author)]

Could you please check whether your key works now too? I got some feedback from other users that their key works now.

[Boofo]

Yes, sir, it works fine now and accepts the key file.

[ghisler(Author)]

Thanks for your feedback!

[Boofo]

Sorry it was late.

[Thierry785]

I also have the same problem, my key is recognized and works under Windows XP, but is not recognized and can not be imported under Windows 7 Home Premium 64 bit. Can you tell me what I can do? Thanks a lot.

[ghisler(Author)]

2Thierry785
I don't think that this has anything to do with this bug report. Please write on command line:
cd %commander_path%
and press ENTER. This brings you to the directory where you need to place the wincmd.key file.

In some rare cases, the key doesn't work in the Total Commander directory due to user right problems. In this case, please do the following:
1. Delete the wincmd.key file from the Total Commander directory
2. Look in menu Help - About Total Commander where wincmd.ini is stored
3. Copy the wincmd.key there

[secureinoz]

2Thierry785
I don't think that this has anything to do with this bug report. Please write on command line:
cd %commander_path%
and press ENTER. This brings you to the directory where you need to place the wincmd.key file.

In some rare cases, the key doesn't work in the Total Commander directory due to user right problems. In this case, please do the following:
1. Delete the wincmd.key file from the Total Commander directory
2. Look in menu Help - About Total Commander where wincmd.ini is stored
3. Copy the wincmd.key there

For new install of Win7 Pro 64-Bit, unlike other posts early in this thread I am not getting any error message.

But with wincmnd.key in the directory where I got the installer to install Total commander, i.e., c:\Program Files\totalcmd, I too get the logon nag screen...meaning my wincmnd.key is not being recognized.

So, I tried steps 1 to 3 above, and I still get the nag screen.

I look forward to advice of a fix.

Thanks Steve

[ghisler(Author)]

Try Alt+Enter on the key, then give everyone read rights to the key file.

[secureinoz]

Try Alt+Enter on the key, then give everyone read rights to the key file.

Alt+Enter on wincmd.key shows:

* file and path: \Users\MyUserName\AppData\Roaming\GHISLER\wincmd.key and

* 'Group or User Names' are: SYSTEM, MyUserName (not my actual user name) and Administrators.

However, Total Commander shows the file and path as c:\Users\MyUserName\AppData\Roaming\Ghisler\wincmd.key...i.e., 'Ghisler' is not in capital letters. Could this difference cause the problem?

For all 3 'Group or User Names' ALL permissions were already ticked 'Allow'...so everyone already has read rights.

And User 'MyUserName' is Administrator.

---------

As moving wincmd.key to c:\Users\MyUserName\AppData\Roaming\GHISLER\ did not solve the nag screen problem, should I now move it back to c:\Program Files\totalcmd...with everyone having read rights?

[ghisler(Author)]

Could this difference cause the problem?

No, Windows isn't case-sensitive. Only Linux and Netware servers are in some functions.

Try adding use "Everyone" and give it rights "Full control" just to check whether it's a rights issue or not.

[secureinoz]

Try adding user "Everyone" to file wincmd.key and give user "Everyone" rights "Full control" just to check whether it's a rights issue or not.

Done. No change, i.e, I still get the logon nag screen.

[ghisler(Author)]

Sorry, I have no idea then. The workaround is to delete the key, and put it in the same directory as wincmd.ini (See menu Help - About Total Commander).

[Flint]

secureinoz
Do you have a backup of your wincmd.key? If yes, please, try to compare it with the key file your TC is using. Couple of times I bumped into similar problem and discovered that 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. (I wanted to report it but found no way to reproduce it, neither was there any specific action I performed before it happened.)