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.

Options
Add an Attachment

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

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

Options

Topic review

Elwood

Ok.
Attached.

File is "Verif-reboot.bat" (just an example as it does the same for other files if I change them)

Side note: when I use debuglevel=2, the log includes the full credentials in a "Parameter" line.
This should be avoided IMO, as the command line help says "add * to enable password logging" and I did not include "*" ;-)

Note: if required, I can provide a Windows 2025 VM for you to test.
martin

Re: Synchronize does not work on Win2025

Please attach a full session log file showing the problem. And give us a name of a file you believe should have been synchronized, but was not.

To generate the session log file, use /log=C:\path\to\winscp.log command-line argument. 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.
Elwood

Synchronize does not work on Win2025

Hi,

Any problem on Win2025, even with WinSCP 6.5.4?
I use the same script I used on several servers 2019 or 2022. It does:
WinSCP.com /command "option batch continue" "option confirm off" "open ftp://login:pass;x-utf=1@ftp.ftp.fr" "synchronize local -delete \mydir /remotedir -filemask=|.stfolder/;.stversions/ -resumesupport=500" exit

Only on Win2025, both with WinSCP.com or WinSCP.exe GUI, it doesn't synchronize an existing file that was changed. It synchronizes/download new files or it deletes local files. But with a file that is present on both side, if I update the local copy, it is not overwritten by WinSCP. No error, the command line just say "Nothing to synchronize".
I never had such problem on Windows 2022 so it might be something new on 2025.

Any hint?
Thanks.