I did some further testing and wanted to share the results.
I checked my backed-up `WinSCP.ini` file and found that `KeepLoginAfterOpenInPutty` was set to `0`. I changed it to `1` and restored the modified configuration, which resolved the issue.
I then performed a fresh installation of WinSCP 6.7.0 from the Microsoft Store and exported its configuration. The same setting was still set to `0` in the newly exported `WinSCP.ini`.
I'm not sure whether this is intentional or whether the default behavior differs between installation scenarios. However, based on my tests, the option appears to be disabled by default, even after a fresh installation.
Perhaps it would be worth considering an explicit option in the to enable this behavior, or changing the default to `1` for new installations.
In my case, changing the value to `1` was enough to resolve the issue. I hope these findings help clarify the behavior and make the configuration easier for other users.
I checked my backed-up `WinSCP.ini` file and found that `KeepLoginAfterOpenInPutty` was set to `0`. I changed it to `1` and restored the modified configuration, which resolved the issue.
I then performed a fresh installation of WinSCP 6.7.0 from the Microsoft Store and exported its configuration. The same setting was still set to `0` in the newly exported `WinSCP.ini`.
I'm not sure whether this is intentional or whether the default behavior differs between installation scenarios. However, based on my tests, the option appears to be disabled by default, even after a fresh installation.
Perhaps it would be worth considering an explicit option in the to enable this behavior, or changing the default to `1` for new installations.
In my case, changing the value to `1` was enough to resolve the issue. I hope these findings help clarify the behavior and make the configuration easier for other users.