@abd1111: See https://winscp.net/eng/docs/rawtransfersettings#replaceinvalidchars

@martin: Is there a way to do this via .NET Assembly on PS? I don't see an obvious TransferOptions for doing so. Thanks.

The reason behind this is that it's not trivial in Windows to create a file ending with dot. Historically it was not allowed. It's possible now, but it's complicated, so WinSCP preserves the dot this way. The same way it preserves other not-allowed characters in files names (like slashes and colons).

You can disable this in transfer settings. But you will lose the dot:
https://winscp.net/eng/docs/ui_transfer_custom#filename_modification

Using SCP I copied a file named from a remote Linux server to my local machine but the copied file got named
Then I copied a file to the remote where it got named
I expected the filenames not to change.

WinSCP 5.9 (Build 6786) on Windows 8.1 was used.