Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
61,595
Downloads of v 5.4.1.20150827:
1,742
Last Update:
31 Aug 2015
Package Maintainer(s):
Software Author(s):
- itefix
Tags:
rsync ssh ssh-keygen- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

RSync for Windows
This is not the latest version of RSync for Windows available.
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
61,595
Downloads of v 5.4.1.20150827:
1,742
Maintainer(s):
Software Author(s):
- itefix
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
RSync for Windows 5.4.1.20150827
This is not the latest version of RSync for Windows available.
All Checks are Passing
2 Passing Test
To install RSync for Windows, run the following command from the command line or from PowerShell:
To upgrade RSync for Windows, run the following command from the command line or from PowerShell:
To uninstall RSync for Windows, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download rsync --internalize --version=5.4.1.20150827 --source=https://community.chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://community.chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade rsync -y --source="'STEP 3 URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade rsync -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure rsync installed
win_chocolatey:
name: rsync
state: present
version: 5.4.1.20150827
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'rsync' do
action :install
version '5.4.1.20150827'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: rsync,
Version: 5.4.1.20150827,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller rsync
{
Name = 'rsync'
Ensure = 'Present'
Version = '5.4.1.20150827'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'rsync':
provider => 'chocolatey',
ensure => '5.4.1.20150827',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install rsync version="5.4.1.20150827" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved by moderator ferventcoder on 28 Dec 2015.
Rsync uses a delta-transfer algorithm which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand. At first glance this may seem impossible because the calculation of diffs between two files normally requires local access to both files.
This packages provides rsync.exe, ssh.exe, and ssh-keygen.exe.
<#
.SYNOPSIS
Create a .ignore file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to ignore a particular binary by creating a file
at the same path with the same name as the binary to ignore, except ending
with the file extension ".ignore".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to ignore.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
New-IgnoreBin -Path "foo.exe"
.EXAMPLE
New-IgnoreBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | New-IgnoreBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function New-IgnoreBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).ignore" -Type "File" -Force | Out-Null
}
}
}
<#
.SYNOPSIS
Create a .gui file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to treat a particular binary as a GUI application,
meaning it will START the binary in a separate process and not block the
console, by creating a file at the same path with the same name as the binary,
except ending with the file extension ".gui".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to treat as a GUI application.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
New-GuiBin -Path "foo.exe"
.EXAMPLE
New-GuiBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | New-GuiBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function New-GuiBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).gui" -Type "File" -Force | Out-Null
}
}
}
$tools = Split-Path $MyInvocation.MyCommand.Definition
$package = Split-Path $tools
$content = Join-Path $package 'cwRsync_5.4.1_x86_Free'
. $tools\bins.ps1
Install-ChocolateyZipPackage `
-PackageName 'rsync' `
-Url 'https://www.itefix.net/dl/cwRsync_5.4.1_x86_Free.zip' `
-UnzipLocation $package
# This package requires the RSYNC_HOME directory on the PATH and a HOME
# environment variable. This cannot be provided with Chocolatey's automatic
# shimming. I have to shim custom batch files.
Get-ChildItem $tools\*.bat | %{ Install-BinFile -Name $_.BaseName -Path $_ }
Get-ChildItem $content\*.exe | New-IgnoreBin
$tools = Split-Path $MyInvocation.MyCommand.Definition
# This package requires the RSYNC_HOME directory on the PATH and a HOME
# environment variable. This cannot be provided with Chocolatey's automatic
# shimming. I have to shim custom batch files.
Get-ChildItem $tools\*.bat | %{ Uninstall-BinFile -Name $_.BaseName -Path $_ }
@ECHO OFF
SETLOCAL
SET RSYNC_HOME=%chocolateyInstall%\lib\rsync\cwRsync_5.4.1_x86_Free
SET PATH=%RSYNC_HOME%;%PATH%
IF NOT DEFINED HOME SET HOME=%USERPROFILE%
rsync %*
@ECHO OFF
SETLOCAL
SET RSYNC_HOME=%chocolateyInstall%\lib\rsync\cwRsync_5.4.1_x86_Free
SET PATH=%RSYNC_HOME%;%PATH%
IF NOT DEFINED HOME SET HOME=%USERPROFILE%
ssh-keygen %*
@ECHO OFF
SETLOCAL
SET RSYNC_HOME=%chocolateyInstall%\lib\rsync\cwRsync_5.4.1_x86_Free
SET PATH=%RSYNC_HOME%;%PATH%
IF NOT DEFINED HOME SET HOME=%USERPROFILE%
ssh %*
Log in or click on link to see number of positives.
- rsync.5.4.1.20150827.nupkg (4b2ee48670c1) - ## / 56
- cwRsync_5.4.1_x86_Free.zip (a200c7f26931) - ## / 56
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version | Downloads | Last Updated | Status |
---|---|---|---|
cwRsync (Free Edition) 5.5.0.20190204 | 35091 | Monday, February 4, 2019 | Approved |
cwRsync (Free Edition) 5.5.0.20180618 | 6051 | Tuesday, June 19, 2018 | Approved |
cwRsync (Free Edition) 5.5.0.20180530 | 2797 | Wednesday, May 30, 2018 | Approved |
cwRsync (Free Edition) 5.5.0.20160518 | 10703 | Wednesday, May 18, 2016 | Approved |
cwRsync (Free Edition) 5.5.0 | 633 | Friday, April 22, 2016 | Approved |
RSync for Windows 5.4.1.20150827 | 1742 | Monday, August 31, 2015 | Approved |
RSync for Windows 5.4.1.1 | 1838 | Friday, April 10, 2015 | Approved |
RSync for Windows 5.4.1 | 651 | Monday, March 23, 2015 | Approved |
This package has no dependencies.
Ground Rules:
- This discussion is only about RSync for Windows and the RSync for Windows package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or RSync for Windows, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.