martin wrote:

WinSCP reads settings from HKCU hive of the Registry. Each user has its own copy of that hive. It's not shared anyhow. WinSCP settings/sites cannot appear there magically. Someone had to put them there.
There's something missing in your description.
For the old users, when you/they start WinSCP, what configuration storage do you see in the preferences? And what do you see for the new user?

I found the problem. This user was the only one using the Windows Registry option for config. storage. The rest are using the custom configuration and are sharing the same .ini file.
Thank you very much for your persistence!

Doug

WinSCP reads settings from HKCU hive of the Registry. Each user has its own copy of that hive. It's not shared anyhow. WinSCP settings/sites cannot appear there magically. Someone had to put them there.
There's something missing in your description.
For the old users, when you/they start WinSCP, what configuration storage do you see in the preferences? And what do you see for the new user?

martin wrote:

You still didn't explain what did you do to make the site "set up for them".

I didn't do anything specific. The app is installed on the workstation and I put a shortcut to it on the Public Desktop so it is available for all. Any user who opens it sees the same site settings. I assumed that is because of the Windows Registry Configuration storage option. All have been able to use the app. so far. The new user cannot and I don't understand why - nothing is different that I can tell.

You still didn't explain what did you do to make the site "set up for them".

Sorry I was not more precise with my explanation. On the Storage Page in the Preferences there is an option for Configuration Storage. I am using the Windows Registry option.
I have WinSCP installed on a single workstation but made it available to all users. When they open it up they are able to see the site which has been set up for them. So far all users have been able to take advantage of this to transmit files to the single site we are working with. Now one newer user is unable to do what everyone else has been able to do - open the app with the custom connection config. Instead he sees a blank list with only New Site. He was able to import the .ini file manually.
I have not tried putting the .ini file I was putting in all the user profiles when I was using the Automatic .ini file option into his profile yet. If I did that I would have to go back to putting that .ini file in all new users profiles - which was an extra step I was trying to avoid.
I hope this makes the problem more clear. If there is a log file I can include for the new user I would be glad to look it up. In this case it is just the initial connection which does not seem to be working.

The "try using the registry" is rather vague. So what did you do to "share" the registry between the users? I'm not sure it's even possible.

We have been using WinSCP for several years. Until recently I was having the site settings - ftp address, password etc. - stored on the user profile. All users shared the same setting for the sole site we upload to. With the last major update I decided to try using the registry so I would not have to configure each new user.
This worked fine until we had a new user added to the team. All of the other accounts work as expected - the site settings are all being shared successfully. The new user is not getting that however. I deleted his windows profile and had him log in again but no luck. When he opens the app there are no sites listed. I still have the old .ini file and he can use the tools menu to import it but I would like for him to be able to just open the app like all the rest do.
I am not sure what info I can post that would help. I might try copying that .ini file to his profile to see if maybe the 'get ini from registry' setting maybe is not working, but?? Any other possibilities?