WinSCP cannot open files when user is not root

Root SSH access works fine in WinSCP 6.3.3.

However, specifying user spring, with correct user password, allows viewing directories and files on the remote Alma Linux/Webuzo server.

Files can be downloaded successfully.

However, an attempt to double-click a file to open it locally in Notepad fails, with the file being treated as a directory name. This failure does not happen for a site for user root.

User spring has rw access to the file.

The log is attached.

Please explain in more details, what happens when "the file being treated as a directory name".

The original WinSCP directory listing in the right-hand pane is replaced by a single entry for ".." (meaning go back up to the parent directory). So it looks like a directory listing, but no file or directory names appear after the ".." entry. A screenshot showing the error message and the resulting directory listing for the file is attached.

Haven't you disabled resolving symbolic link in your session settings?
https://winscp.net/eng/docs/ui_login_directories#directory_reading_options

I updated to 6.3.5 today and cannot upload single files, only folders from Windows to Linux server.

I'm not sure how to describe the problems (I'm not a WinSCP expert), but one is that I cannot open a file in notepad.exe by double-clicking its name.
Are any others having such problems? I think I'm going to have to go back to coreFTP.

Maybe it would help if I post a log file here. I already posted a screenshot above. Where would I find a log file?

I apologize for the complaining.

I've asked you above

Haven't you disabled resolving symbolic link in your session settings?

Did you check?

I don't understand what this is or how to do it or how it would fix my problems with WinSCP. However, I have returned to Core FTP LE, which is also free, and which works reliably. I just use the user account, its password, and its certificate and private key (not the root, so the file user is other than root). I have given up on SSH encrypted passwords, with public and private keys because they don't work with WinSCP. They do work with Core FTP.

Also, there is a problem with your forum: I got an error message "Sorry, but this username has already been taken." when trying to reply with my real winscp.net username.

Thank you for taking the time to reply. I appreciate the information.