Thanks.
This is much appreciated.

It's more complicated.

But anyway, this request has been added to the tracker:
https://winscp.net/tracker/817

Yes, sure.

But I think you could save the ini location in the registry (I guess you save the setting if a ini file should be used in the registry too?)

So on startup the program could work like this:
1) connamdline ini option set? No:
2) use ini file option = true? Yes:
3) check registry for ini location
4) load settings.

harkman wrote:

I'm sorry I did not expect the commandline would expose settings not available in the GUI configuration panel.

INI file path has to be known before loading the configuration, so it cannot be part of the configuration :)

Great thank you.

I'm sorry I did not expect the commandline would expose settings not available in the GUI configuration panel.

Version 4.x is writting INI file to %APPDATA% due to File system redirector
https://learn.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector
So actually it is 4.x that is buggy.

If you want to force WinSCP to use another location, use /ini command line switch.
https://winscp.net/eng/docs/commandline

Hello.

In version 5 of WinSCP there is a issue with the storage location of the winscp.ini (If you switch to file based configuration).

Since the first beta of version 5 I get this error (see attachment) because the application tries to write the configuration file in the programs installation directory.

Version 4 does handle this properly and stores the file in the %APPDATA% directory.

I would love to see a option to define a custom configuration location to be able to save the configfile in my dropbox directory to sync my config file between two locations.

Thank you for this absolutely essential application.