Free, safe and secure SFTP, SCP and FTP client for Windows

WinSCP

WinSCP 5.21.6

  -  10.94 MB  -  Open Source
  • Latest Version

    WinSCP 6.3.5

  • Operating System

    Windows XP / Vista / Windows 7 / Windows 8 / Windows 10

  • User Rating

    Click to vote
  • Author / Product

    WinSCP Team / External Link

  • Filename

    WinSCP-5.21.6-Setup.exe

  • MD5 Checksum

    cd1145484994bc7fdf513366a5882c96

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of WinSCP 5.21.6.


For those interested in downloading the most recent release of WinSCP or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • WinSCP 5.21.6 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    WinSCP 5.21.6 Screenshot 1
  • WinSCP 5.21.6 Screenshot 2
  • WinSCP 5.21.6 Screenshot 3
  • WinSCP 5.21.6 Screenshot 4
  • WinSCP 5.21.6 Screenshot 5

What's new in this version:

- TLS/SSL core upgraded to OpenSSL 1.1.1s
- XML parser upgraded to Expat 2.5.0
- Translation updated: German
- Setting $PSNativeCommandArgumentPassing to Legacy in generated WinSCP scripting PowerShell commandline, which is needed for PowerShell 7.3 compatibility
- Added new ap-south-2, eu-central-2 and eu-south-2 AWS regions and doubling region drop-down height

Fixed:
- Moving WebDAV transfer to background aborts the transfer if the server commits the interrupted foreground transfer
- Failure when saving edited file while current tab is not connected
- When the current session is encrypted, saved edited file was uploaded using the current session instead of its source session. When the current session is not encrypted, edited files opened in any encrypted session was uploaded on the background, possibly leading to data inconsistent files
- When reattaching edited file to re-connection session, the file was always attached to the current session instead of the possibly non-active re-connected session