Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

martin

Re: The timestamp function is not available

2026-10-19

You are using SCP protocol. While you have possibly selected SFTP (I cannot tell as you didn't post a complete log file), the server rejects SFTP session. So WinSCP falls back to SCP protocol. With the SCP protocol, preserving directory timestamps is not supported.

. 2026-10-16 16:53:22.439 [Background 1] Opening main session channel
. 2026-10-16 16:53:22.556 [Background 1] Opened main channel
. 2026-10-16 16:53:22.561 [Background 1] Primary command failed; attempting fallback
. 2026-10-16 16:53:22.568 [Background 1] Started a shell/command
. 2026-10-16 16:53:22.568 [Background 1] --------------------------------------------------------------------------
. 2026-10-16 16:53:22.568 [Background 1] Using SCP protocol.

Wei

Re: The timestamp function is not available

2026-10-16 10:08

The attached file is the log file generated during the SFTP file transfer.

The context option in the gray box is still not working. Directory timestamps cannot be preserved, although file timestamps can be preserved.

martin

Re: The timestamp function is not available

2026-10-12

Preserving timestamps is not available with all protocols and servers. For details, see:
https://winscp.net/eng/docs/ui_transfer_custom#common
https://winscp.net/eng/docs/protocols#timestamp
If you need further help, please specify what protocol are you using and attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.