Since newest upgrade, Integration is not reading relative [local] paths

I have an install that I share across networks, so I have paths relatively in the INI file.

In versions previous to 5.7.4, I could have "..\PuTTY\putty.exe" as my Putty integration. Since new version, it tells me "Not found". It doesn't work even if I put "PuTTY\putty.exe" (so putty dir inside WinSCP).

What should I do now?

It works for me, both with ..\PuTTY\putty.exe and PuTTY\putty.exe.
Can you post a screenshot of the configuration, the error message and the Windows explorer with the executable?
Was this introduced in 5.7.4? Does it work with 5.7.3?

Yes, prior to 5.7.4 all was good!

Here are more images since there was a limit

It's the forward slash. It won't work in any version this way. You have to use a backslash in Windows paths.

Still having issues... see attachment:

What is the error message? What is the path relative to?

Same thing before - the application "doesn't exist".

NP++ is in ......\apps\edit\Notepad++
WINSCP is in ......\apps\net\WinSCP

I mean my question is basic - I want to have the text editor in a relative path to WinSCP because I use cloud bsaed drives. This was never a problem in the past and now so many issues.

Local paths in WinSCP are resolved relatively to WinSCP startup directory. Not to a directory where WinSCP.exe is.

To make a path relative to WinSCP.exe directory, use %WINSCP_PATH%.

In your case that is: %WINSCP_PATH%\..\edit\Notepad++\Notepad++.exe

It was always like this. Nothing has changed.

See https://winscp.net/eng/docs/local_path (note that this page didn't change ever since it was created in 2009 and the behavior is actually even older).