Our 32-Bit application launches Windows LNK files (Shell Links) via ShellExecute. When it tries to \"launch\" a link to a 64-Bit binary (such as the \"Internet Explorer (64-
Andrew: I gave it a shot, and the sysnative folder does not do anything that Wow64DisableWow64FsRedirection doesn't already do. The problem is that ShellExecute mistakenly assumes that the link is pointing to %programfiles(x86)%, when it is in fact pointing to %programfiles% (Even when there is no such file in %programfiles(x86)%).
Opening 64bit programs already works perfectly fine. It's .lnk files pointing to the %programfiles% directory that are the problem.