keypath not reading registry properly
Moderators: Hacker, petermad, Stefan2, white
keypath not reading registry properly
Hello, i work for a school and and wanted to add license keys to the registry so the file key would not be needed. Adding keypath=$ in wincmd.ini worked at first, but now every time i start total commander it doesnt register the key. I tried adding it into HKCU, HKLM, WOW6432Node, but it refuses to read the key for some reason. I am using version 9.12.
Re: keypath not reading registry properly
2nomis
There have been a few changes regarding having the license key in the Registry since version 9.12 - so maybe a new version will solve your problem.
Maybe it is time for you to update your more than 7 year old TC - we are at version 11.51 now - updates are free and always backwards compatible.I am using version 9.12.
There have been a few changes regarding having the license key in the Registry since version 9.12 - so maybe a new version will solve your problem.
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Re: keypath not reading registry properly
I updated to newest version & still the same thing, i tried adding Log=1 into wincmd.ini thinking it should make a log and nothing happenedpetermad wrote: 2025-02-25, 15:08 UTC 2nomisMaybe it is time for you to update your more than 7 year old TC - we are at version 11.51 now - updates are free and always backwards compatible.I am using version 9.12.
There have been a few changes regarding having the license key in the Registry since version 9.12 - so maybe a new version will solve your problem.
Re: keypath not reading registry properly
64Bit, the WOW6432 node isnt anything of significance i just wanted to put it to every possible readable directory in case it has a problem but i want it primarily in HKLM & thats where it worked before. I am doing it on a single computer but it stopped working after it was pushed on most school pcs.white wrote: 2025-02-25, 15:13 UTC32-bit or 64-bit?
Are you aware that a license is valid for all TC versions?
You mentioned WOW6432Node. Am I right to assume you are using a 64-bit Windows version?
Are you talking about a single computer?
Re: keypath not reading registry properly
Sorry that I deleted my post. I thought I found something and did not notice you replied already.nomis wrote: 2025-02-25, 15:18 UTC64Bit, the WOW6432 node isnt anything of significance i just wanted to put it to every possible readable directory in case it has a problem but i want it primarily in HKLM & thats where it worked before. I am doing it on a single computer but it stopped working after it was pushed on most school pcs.
For TC 9.12 64-bit the license should be under HKCU or HKLM (WOW6432 for the 32-bit version). Newest versions check all registry keys and you don't even have to use the KeyPath entry in wincmd.ini.
If it really stopped working after it was pushed on most school pcs, it would have nothing to do with Total Commander. It should still work.
Perhaps you'll find my tool TC key.cmd useful to check if license in the registry was somehow altered. Place the tool and your license file in the same folder and run the tool. It will show if the key in registry and in the file are the same.
Re: keypath not reading registry properly
it seems the licences were indeed not matching even though i checked multiple times. Your tool helped me resolve this issue, thank you very much.white wrote: 2025-02-25, 15:53 UTCPerhaps you'll find my tool TC key.cmd useful to check if license in the registry was somehow altered. Place the tool and your license file in the same folder and run the tool. It will show if the key in registry and in the file are the same.nomis wrote: 2025-02-25, 15:18 UTC64Bit, the WOW6432 node isnt anything of significance i just wanted to put it to every possible readable directory in case it has a problem but i want it primarily in HKLM & thats where it worked before. I am doing it on a single computer but it stopped working after it was pushed on most school pcs.