I know, sadly this is not transparent for the user at all, but this is not what my report is about. And it seems that the file is not copied, but rather the contents of the file is copied to a new file. This results in a new modification timestamp which normally does not happen when a file is copied. I remarked that this is unwanted because a changed modification timestamp suggests a change in the contents of the file. This may cause people to wonder if the file was changed when it was installed. Furthermore, the timestamp may be used to identify the key file when people have multiple key files. For example, I have multiple key files because my address changed a couple of times. Whenever I encounter a WINCMD.KEY file anywhere on my computer or in a backup, I can identify the key file by looking at the timestamp.Double clicking the key copies it to the program folder, and when this fails due to missing rights, to %APPDATA%\GHISLER.
Obviously, overwriting a license file without the user knowing which file, at which location, is problematic. There can be multiple license files at play in different locations (program folder and appdata folder), which could potentially lead to the loss of a license file.This is done independently of whether the file already exists or not.
But my report is about when the license file is copied to itself, which makes no sense and can easily be avoided. In the best case this only changes the timestamp. In the worst case the license file can become corrupted. In my opinion, TC should never try to copy the license file to itself.
Statistics: Posted by white — 2025-01-07, 17:40 UTC