https://bugs.winehq.org/show_bug.cgi?id=49748
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Created attachment 68050 --> https://bugs.winehq.org/attachment.cgi?id=68050 Test case
Adding a small test case. The problem here is ShellExecute.
When there are two executables with the same name, and one is in a subfolder, the shell execute logic messes up.
AFAIK there's two problems here: 1) Shell execute with a relative path doesn't work properly, because it passes the same relative path to CreateProcessW 2) When normalizing the path, CreateProcessW searches in the current directly before the specified directory, leading to the exe starting itself endlessly
Can someone with more experience than me please look into that? Loading path order is pretty complicated...