Windows – How to Fix Symlink to Executable Not Opening by Double Click

Since the only other answer doesn't really "fix" the issue, just acknowledges it, I think it's worth saying I had this same issue, and discovered the problem.

The issue for me was relative vs absolute symlinks. I use Link Shell Extension.

When creating absolute symlinks, Explorer works fine. When creating relative links, Explorer chokes on them.

I can only guess that this is somehow related to how Explorer calculates the working directory? Maybe some slash problems?

_{(Note that on Win7 x64, at least, you may have to open LSEConfig.exe after installing the extension, and toggle Absolute and then Relative to get it to make relative links, as the default config is somewhat unpredictable, sometimes relative, sometimes absolute.)}

Let me illustrate the problem with an example. I created a simple one-line batch file Test.bat in C:\Program Files with the following contents:

@echo Batch dir = "%~dp0"

Now from D:\ if I invoke the batch file with C:\Program Files\Test, it says:

Batch dir = "C:\Program Files\"

If I modify the PATH using set path=%path%;C:\Program Files and invoke the batch file with a simple Test, it says:

Batch dir = "C:\Program Files\"

Finally if I create a symlink using mklink Test.bat "C:\Program Files\Test.bat" and invoke it with a simple Test, it says:

Batch dir = "D:\"

As you can see the current working directory is different in this case. No wonder your apps are complaining about files they expect in the executable's directory being missing.

If you don't want to add lots of directories to the PATH just add one that contains batch files for each of your apps.