I create shortcuts to (existing) folders. This worked like a charm for many years but not people switching over to WIN 10 and reporting issues. It appears the AHK FILECREATESHORTCUT does have an issue with the folder name and create the shortcut wrongly therefore WIN 10 cannot open it.
I did check on the folder names and existence of those and this all in good order. The manually created shortcut has the identical Target link as the one create by AHK.
However it seems AHK has issues with the folder name. The target folder has a shape of
It appears the .BC) is interpreted by AHK as file instead of a folder causing this confusion.\\server\folder\AB 12345-Realization (A12-3.BC)
Since this structure is used by other software we actually have to keep it this way.
Anyone has a workaround for this? I searched the net but the only issue I can find is when the folder is not created yet. But in my case it's ensured the folder is existing since I create it earlier in the script.
During troubleshooting I challenged that to avoid racing conditions or similar but everything is in good order.
Any help is appreciated since my users getting a little upset that this does not function anymore after WIN 10 upgrades
My source code runs over 500 lines which I doubt anyone will read entirely, the line of interest looks like below (straight forward and working fine in the past until WIN10 came in).
If it's related to some settings or similar please point me to the direction and I'll post the related part of my code.
Code: Select all
FileCreateShortcut, %target_folder%, %basedir%\%folder_name_long%.lnk