WinSCP does not notice a changed file timestamp at download?

I download some files regularly from a remote system to my local PC, because I'm editing the files on the remote system, so I keep WinSCP open on that directory.
However, WinSCP warns me about the local file already existing showing the information about the 'New' and 'Existing' file, with the *same* timestamp, although I just edited it and saved it...
I need to explicitly click 'Refresh' to get the timestamp right !? Come on... what is this? Ridiculous.
As soon as I click 'copy' it should get the up-to-date timestamp.
This seems to me something so basic, and it should work like that by default!

It's actually even worse:
if I don't click 'Refresh' the remote file timestamp remains the same,
but the copied file does get the file's *actual* timestamp,
so that when I click 'Copy' again it says I'm replacing
a newer version of the file with an older one
(which is not true, because now the files -local and remote- have in fact the same timestamp).

Btw: I'm using WinTCP version 4.3.2.

What protocol are you using?

martin wrote:

What protocol are you using?

When I look at the saved profile for my session
there is a drop-down box containing choices SFTP,SCP and FTP,
in which SFTP is selected.
However, I didn't select that; probably it is the default.

This issue has been added to tracker:
https://winscp.net/tracker/810