Current dir

[Mikanoshi]

Looks like 3.2.0.2 (tested Ultimate x64 version) is not setting current dir correctly when launching exe.
Dir is xplorer2 folder instead of an exe folder, which breaks programs that use relative paths.

[otlaolap]

I concur. A double-click on c:\windows\system32\cmd.exe would, using X2 3.2.0.1, open the command prompt with the current directory set to C:\Windows\System32 (I just restored a copy and tested this). With 3.2.0.2, the double-click on c:\windows\system32\cmd.exe gives me a current directory of "E:\Our Tools\Explorer Squared" (my X2 install directory).

[Mikanoshi]

Launching as admin does this too even on 3.2.0.0
All this is with "Don't lock browsed folder" option enabled. Disabling the option fixes the problem.
But still FAQ only mentions the issue with current dir in cmd, not in all programs, so it's a regression in 3.2.0.2

[nikos]

please tick off the option "don't lock browsed folder" and current dir will behave