LNK files get their timestamp updated whenever they are executed
Posted: 24.03.2026, 11:32
Issue:
When an LNK shortcut to an executable or script file is executed from FreeCommander, the Modified timestamp of this LNK gets unwantedly updated to current date and time
Symptoms:
● This does not happen when executing the very same LNK file from Windows Explorer, Dual Commander, XnView MP, Everything and other file handling programs
● Shortcuts pointing to folders do not change their timestamp - except when using the shell command >>Open in FreeCommander<<
● This has nothing to do with Settings - because things are the same when I am using default ones
● Sysinternals Process Monitor shows multiple CreateFile events and one WriteFile on an LNK performed by >>FreeCommander.exe<< during its execution - that WriteFile updates the Modified timestamp
● If an LNK file is set to read-only, then executing it from FreeCommander no longer changes its timestamp
● This started happening way back before I started using Build 912 64-bit Donor Portable and Build 901 32-bit Public Installed on Windows 10 Enterprise 20H2 x64 (10.0.19042) and continues now when using Build 946 64-bit Donor Portable and Build 941 32-bit Public Installed on Windows 10 IOT Enterprise LTSC 21H2 x64 (19044.6691)
Questions:
Why does FreeCommander write to the shortcut file when executing it, instead of apparently passing it directly to the shell like e.g. Windows Explorer does? And can this be changed / fixed with an update?
When an LNK shortcut to an executable or script file is executed from FreeCommander, the Modified timestamp of this LNK gets unwantedly updated to current date and time
Symptoms:
● This does not happen when executing the very same LNK file from Windows Explorer, Dual Commander, XnView MP, Everything and other file handling programs
● Shortcuts pointing to folders do not change their timestamp - except when using the shell command >>Open in FreeCommander<<
● This has nothing to do with Settings - because things are the same when I am using default ones
● Sysinternals Process Monitor shows multiple CreateFile events and one WriteFile on an LNK performed by >>FreeCommander.exe<< during its execution - that WriteFile updates the Modified timestamp
● If an LNK file is set to read-only, then executing it from FreeCommander no longer changes its timestamp
● This started happening way back before I started using Build 912 64-bit Donor Portable and Build 901 32-bit Public Installed on Windows 10 Enterprise 20H2 x64 (10.0.19042) and continues now when using Build 946 64-bit Donor Portable and Build 941 32-bit Public Installed on Windows 10 IOT Enterprise LTSC 21H2 x64 (19044.6691)
Questions:
Why does FreeCommander write to the shortcut file when executing it, instead of apparently passing it directly to the shell like e.g. Windows Explorer does? And can this be changed / fixed with an update?