[8.01 x64] Win8 - symlinks of networkshare -> file not fo

[lanwin]

Hi, it seems Total Commander has a problem with network shares that are linked as symbolic link on Win8 RTM. It can not start files from it (Enter or double mouse click). Instead it raises a "File not found" error. If I run the Windows Menu (via Left Mouse option) and choose open, it works as expected. It also works in Windows Explorer and on TC 8.01 on Win7 x64.

Steps to reproduce:
* Open evaluated cmd
* run mklink /D test //server/share
* cd test
* double click or enter executable or a simple text file

[ghisler(Author)]

This is indeed a bug in Windows 8, it has been there already in preview versions of Windows 8. The ShellExecuteEx function fails on such linked dirs. I added a workaround for local symbolic links, but can't for remote links (because resolving the link returns the directory on the remore machine, not the directory by which it can be accessed from the local machine).

[lanwin]

Ok, is there already a connect bug which I can up vote?

The interesting question then is why that works in explorer without any problem? I mean Microsoft is only consuming its own API there.

And then, Ive tested the following with the .Net SehllExecute api. And it worked:

Process.Start(new ProcessStartInfo(@"\network symlink\test.zip"){
UseShellExecute = true
});

[ghisler(Author)]

If it works in Explorer, you can try to open it via right click - Open (or name of the file).

[lanwin]

If it works in Explorer, you can try to open it via right click - Open (or name of the file).

Yes, as I have written above, this works. But its not very comfortable.

[lanwin]

So the intresting question is why it works in .Net and not in C? I mean the .Net API also only calls Win32.

[ghisler(Author)]

Hmm, no idea - I would have to know the exact test case, so I can try it on my installation of Windows 8. Can you give me instructions how to create the link, where to create it, and with what target? I don't need the exact names, just something I can reproduce. Thanks.

[lanwin]

Hmm, no idea - I would have to know the exact test case, so I can try it on my installation of Windows 8. Can you give me instructions how to create the link, where to create it, and with what target? I don't need the exact names, just something I can reproduce. Thanks.

Here it is:

* Open evaluated cmd (Windows+R)
* mkdir C:\test
* cd C:\test
* run mklink /D link //server/share
* cd link
* notepad test.txt
* Save it
* double click or enter executable or a test.txt

[ghisler(Author)]

Thanks, I will try it!

[lanwin]

Thanks, I will try it!

Could you reproduce the issue?

[ghisler(Author)]

Sorry, I have been busy with other things recently.

[lanwin]

Do you have any timeframe when you could investigate in this issue?

[ghisler(Author)]

I'm waiting for the release of Windows 8 devices in my country (Switzerland) to work on better compatibilty with them. They have been announced for about mid to end November.

[lanwin]

Any news on the issue?

Maybe it would help to try the evaluation version from here http://msdn.microsoft.com/de-de/evalcenter/jj554510.aspx?wt.mc_id=MEC_132_1_4.

[ghisler(Author)]

I have tested this, and the only way to reproduce it was to run TC in Windows 7 (or older) compatibility mode. It works fine when TC isn't run with any compatibility options. Please check the properties of the program and of the link by which you start TC.