Run command works from source and U64-compiled but fails U32-compiled - Compiler Bug?

[anaglypta]

I'm happy it worked!

Btw the explorer.exe code was to open the link files, not to open Explorer windows.
It might be worth a try.

Are there any special link files on a default Windows 10 install? So I could try. Thanks.

[JoeWinograd]

Btw the explorer.exe code was to open the link files, not to open Explorer windows.

Ah, I missed that. Yes, running the link files via explorer.exe works...but now I'm a ShellRun fan,

Are there any special link files on a default Windows 10 install?

No. The only shortcuts that gave me problems were the ones to the Microsoft Office apps.

Btw, sorry for the delayed response...was the wee hours in my neck of the woods and I packed it in for the night after my previous post. Thanks again, Joe

[guest3456]

just ran into this mind boggling issue myself

add this line before the Run command worked:

Based on what gregster said, you could try this:

Code: Select all

if A_Is64bitOS && (A_PtrSize!=8)
	DllCall("kernel32\Wow64DisableWow64FsRedirection", "Ptr*",0)

------

When you launch a shortcut file with ShellExecuteEx, most likely some code within that function executes within the current process to locate the appropriate command line and run it. If the current process is 32-bit on a 64-bit system, the command line is being run within the context of Wow64.

When you use ShellRun, explorer.exe launches the command-line. On 64-bit systems, the process is 64-bit.

if we always run ahk64-bit, then we avoid this problem altogether?