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-
Reading this article from Raymond Chen I don't think what you're asking is possible. I would still consider making a small "trampoline" application, who's only job was to launch the given application/link, and compiling a different one for use on 32bit and 64bit systems. Either that or build two versions of your application, a 32bit and 64bit one.
Anytime you here something is impossible on a computer, think again... The key is to utilize the c:\windows\sysnative\ path to shut off the redirection.
Here is very simple code that will do what you want:
#include <windows.h>
#include <ShellAPI.h>
#include <stdio.h>
int main(int iArgc, const char *pArgv[])
{
ShellExecute(NULL, L"open", L"C:\\windows\\sysnative\\..\\..\\Program Files\\Internet Explorer\\iexplore.exe", NULL, NULL, SW_SHOWNORMAL);
BOOL bIAmWow64 = FALSE;
IsWow64Process(GetCurrentProcess(), &bIAmWow64);
printf("I am a wow64 process: %hs\n", bIAmWow64 ? "Yes": "No");
return 0;
}
I hope that is helpful.
You could spawn an explorer.exe process which calls on the LNK.
Is there a particular reason you can't compile your program as a 64bit application?
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.