Downloads of v 1.16.2:


Last Update:

26 Jan 2022

Package Maintainer(s):

Software Author(s):

  • Hobara Rei


carotdav.install online storage tool webdav ftp sftp

CarotDAV (Install)

  • 1
  • 2
  • 3

1.16.2 | Updated: 26 Jan 2022



Downloads of v 1.16.2:



Software Author(s):

  • Hobara Rei

  • 1
  • 2
  • 3
CarotDAV (Install) 1.16.2

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install CarotDAV (Install), run the following command from the command line or from PowerShell:


To upgrade CarotDAV (Install), run the following command from the command line or from PowerShell:


To uninstall CarotDAV (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

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 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

3. Copy Your Script

choco upgrade carotdav.install -y --source="'INTERNAL REPO 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 carotdav.install -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install carotdav.install
    name: carotdav.install
    version: '1.16.2'
    state: present

See docs at

chocolatey_package 'carotdav.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.16.2'

See docs at

cChocoPackageInstaller carotdav.install
    Name     = "carotdav.install"
    Version  = "1.16.2"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'carotdav.install':
  ensure   => '1.16.2',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 26 Jan 2022.


Complied Standards, Features

  • HTTP/1.1 (RFC2616)
  • HTTPS (RFC2818)
  • DAV class 1(RFC2518), 3(RFC4918)
  • Authentication Methods: None, Basic(RFC2617), Digest(RFC2617), NTLM, Kerberos, SPNEGO(Negotiate)(Kerberos、NTLM), WSSE, Passport
  • HTTP Proxy
  • Client Certificate
  • Compression/Decompression
  • gzip (RFC1952/RFC2616)
  • zlib (RFC1950/RFC2616) / deflate (RFC1951)
  • Brotli (RFC7932) decompression only
  • FTP (RFC959)
  • FTPS (FTP over TLS) (RFC4217, RFC2228, RFC2246) (Explicit only)
  • zlib compression(IETF Draft draft-preston-ftpext-deflate-03.txt)
  • SFTP (SFTPv3 over SSHv2)
  • OneDrive
  • Dropbox
  • GoogleDrive
  • Box
  • SugarSync
  • AmazonCloudDrive
  • HubiC
  • OpenStack Swift
  • iCloud Drive
  • Host-specific file names(RFC1738)
  • support long path > MAX_PATH(260)
  • IMAP4rev1(RFC3501) ReadOnly
  • Resume
  • Download / Upload
  • Auto Split
  • Encrypt / Verify
  • Filename (AES256 CTS)
  • File contents (AES256 CBC)
  • Key and IV creation PBKDF2 (RFC2898)
  • Verification based on Hash (SHA-256)
  • Various charactor encodings (UTF-7/8/16/32, Shift-JIS, ISO-2022-JP, EUC-JP, Big5, EUC-KR, EUC-TW, etc)
  • Unicode Normalization (Unicode Standard Annex #15)
  • Master Password
  • AES256 CBC
  • Key and IV creation PBKDF2 (RFC2898)
  • SSL3.0, TLS 1.0/1.1/1.2
  • simplified WebDAV server for local use
  • GUI and CUI version


You should take care of below from the point of security / privacy.

About Security

By default, passwords are saved with no encryption.

In the setting file, there are login IDs and raw passwords. By default, it is not encrypted. If you want to avoid risk, use master password.

WebDAV server doesn't support user authentication or SSL/TLS.

Since WebDAV server of CarotDAV is designed for local use, it becomes dangerous if the settings are wrong. Use loopback address( to prevent access from others.

During OAuth procedure, CarotDAV shows the other site.

Some services needs HTTPS server during OAuth. Since this site doesn't support HTTPS, CarotDAV use this page instead. I assure that site is safe in the same way as CarotDAV.

About Privacy

CarotDAV accesses version file to confirm update on boot. Below informations are logged on the server at that time.

  • Current version of CarotDAV you use.
  • Access Time.
  • IP Address.
    I keep these logs not to be seen from others as possible. I might use or public these information after statistical processing. I might show these logs to public institution if they claim.

CarotDAV collect no other information.





This software is free of charge. You can use it personally or commercially. You are also allowed to distribute secondary, fix/alter, do reverse-engineering.
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Download:
2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'
   checksum type: sha256
   checksum32: 513B9D22F95459D1DABADCFE41CD974AE1782151F1BCA89EACC8CBABEF40A634
   checksum64: 513B9D22F95459D1DABADCFE41CD974AE1782151F1BCA89EACC8CBABEF40A634
File 'LICENSE.txt' is obtained from:
md5: 850CECF712AFAE256A84AE17D1B0FE2B | sha1: F400B11D5B66745BAEF61FC3A0D0B2AE7F009732 | sha256: 513B9D22F95459D1DABADCFE41CD974AE1782151F1BCA89EACC8CBABEF40A634 | sha512: 6190A9251A9A48DDCC395BA9D08E53E45D1642AFBA158D2046A61BC263F03612C3AF049E58F28B50E65C357985E1CD940267C083480E75335DC55E6260B090C4
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  destination = "$toolsDir"
  file        = "$toolsDir\"
Get-ChocolateyUnzip @packageArgs
Remove-Item -Path $packageArgs.file

$packageArgs = @{
  packageName  = $env:ChocolateyPackageName
  fileType     = "MSI"
  fileFullPath = "$toolsDir\CarotDAV1.16.2\CarotDAV1.16.2.msi"
  silentArgs   = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`""
Install-ChocolateyInstallPackage @packageArgs

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
CarotDAV (Install) 1.16.1 67 Sunday, December 5, 2021 Approved
CarotDAV (Install) 1.16.0 58 Saturday, December 4, 2021 Approved
CarotDAV (Install) 1.15.10 132 Friday, February 12, 2021 Approved
CarotDAV (Install) 1.15.9 210 Saturday, June 13, 2020 Approved
CarotDAV (Install) 1.15.8 294 Sunday, January 12, 2020 Approved
CarotDAV (Install) 1.15.7 151 Thursday, September 19, 2019 Approved
CarotDAV (Install) 1.15.6 101 Monday, September 16, 2019 Approved
CarotDAV (Install) 1.15.5 203 Tuesday, July 23, 2019 Approved

This package has no dependencies.

Discussion for the CarotDAV (Install) Package

Ground Rules:

  • This discussion is only about CarotDAV (Install) and the CarotDAV (Install) 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 CarotDAV (Install), 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.
comments powered by Disqus