Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Validation Testing Passed

Verification Testing Failed


There are versions of this package awaiting moderation . See the Version History section below.

This package was rejected on 11 Oct 2020. The reviewer chocolatey-ops has listed the following reason(s):

chocolatey (maintainer) on 06 Sep 2020 00:12:03 +00:00:

User 'chocolatey' (maintainer) submitted package.

chocolatey-ops (reviewer) on 06 Sep 2020 00:43:36 +00:00:

vim has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.


Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 06 Sep 2020 07:15:08 +00:00:

vim has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 26 Sep 2020 07:17:27 +00:00:

We've found vim v8.2.1620 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 11 Oct 2020 07:19:01 +00:00:

Unfortunately there has not been progress to move vim v8.2.1620 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.


Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems.

Vim is often called a programmer's editor, and so useful for programming that many consider it an entire IDE. It's not just for programmers, though. Vim is perfect for all kinds of text editing, from composing email to editing configuration files.


  • Vim: Vim terminal(CLI) application can be used from Powershell and Command Prompt.

  • GVim: The GUI version of Vim provides full featured Windows GUI application experience.

  • Terminal Integration: Batch files are created to provide vim, gvim, evim, view, gview, vimdiff, gvimdiff and vimtutor command on terminal use.

  • Shell Integration: Vim is added in Open with ... context menu. And by default Edit with Vim context menu is created to open files whose extensions are associated with other applications.

Package parameters

  • /InstallDir - Override the installation directory. By default, the software is installed in $ChocolateyToolsLocation, it's default value is C:\tools. You can include spaces. See the example below.
  • /RestartExplorer - Restart Explorer to unlock GVimExt.dll used for Edit with Vim context menu feature.
  • /NoDefaultVimrc - Don't create default _vimrc file.
  • /NoContextmenu - Don't create Edit with Vim context menu.
  • /NoDesktopShortcuts - Don't create shortcuts on the desktop.

Example: choco install vim --params "'/NoDesktopShortcuts /InstallDir:C:\path\to\your dir'"


  • This package uses the ZIP build to install to provide installation parameters.
  • All compilation of the software is automated and performed on Appveyor. The building status is open.
  • This package provides an official build. Similar package vim-tux is from a well-known unofficial vim building project. Unlike vim-tux, this package can take some installation parameters.
  • See for more information.




I)  There are no restrictions on distributing unmodified copies of Vim except
    that they must include this license text.  You can also distribute
    unmodified parts of Vim, likewise unrestricted except that they must
    include this license text.  You are also allowed to include executables
    that you made from the unmodified Vim sources, plus your own usage
    examples and Vim scripts.

II) It is allowed to distribute a modified (or extended) version of Vim,
    including executables and/or source code, when the following four
    conditions are met:
    1) This license text must be included unmodified.
    2) The modified Vim must be distributed in one of the following five ways:
       a) If you make changes to Vim yourself, you must clearly describe in
          the distribution how to contact you.  When the maintainer asks you
          (in any way) for a copy of the modified Vim you distributed, you
          must make your changes, including source code, available to the
          maintainer without fee.  The maintainer reserves the right to
          include your changes in the official version of Vim.  What the
          maintainer will do with your changes and under what license they
          will be distributed is negotiable.  If there has been no negotiation
          then this license, or a later version, also applies to your changes.
          The current maintainer is Bram Moolenaar <[email protected]>.  If this
          changes it will be announced in appropriate places (most likely
, and/or comp.editors).  When it is completely
          impossible to contact the maintainer, the obligation to send him
          your changes ceases.  Once the maintainer has confirmed that he has
          received your changes they will not have to be sent again.
       b) If you have received a modified Vim that was distributed as
          mentioned under a) you are allowed to further distribute it
          unmodified, as mentioned at I).  If you make additional changes the
          text under a) applies to those changes.
       c) Provide all the changes, including source code, with every copy of
          the modified Vim you distribute.  This may be done in the form of a
          context diff.  You can choose what license to use for new code you
          add.  The changes and their license must not restrict others from
          making their own changes to the official version of Vim.
       d) When you have a modified Vim which includes changes as mentioned
          under c), you can distribute it without the source code for the
          changes if the following three conditions are met:
          - The license that applies to the changes permits you to distribute
            the changes to the Vim maintainer without fee or restriction, and
            permits the Vim maintainer to include the changes in the official
            version of Vim without fee or restriction.
          - You keep the changes for at least three years after last
            distributing the corresponding modified Vim.  When the maintainer
            or someone who you distributed the modified Vim to asks you (in
            any way) for the changes within this period, you must make them
            available to him.
          - You clearly describe in the distribution how to contact you.  This
            contact information must remain valid for at least three years
            after last distributing the corresponding modified Vim, or as long
            as possible.
       e) When the GNU General Public License (GPL) applies to the changes,
          you can distribute the modified Vim under the GNU GPL version 2 or
          any later version.
    3) A message must be added, at least in the output of the ":version"
       command and in the intro screen, such that the user of the modified Vim
       is able to see that it was modified.  When distributing as mentioned
       under 2)e) adding the message is only required for as far as this does
       not conflict with the license used for the changes.
    4) The contact information as required under 2)a) and 2)d) must not be
       removed or changed, except that the person himself can make

III) If you distribute a modified version of Vim, you are encouraged to use
     the Vim license for your changes and make them available to the
     maintainer, including the source code.  The preferred way to do this is
     by e-mail or by uploading the files to a server and e-mailing the URL.
     If the number of changes is small (e.g., a modified Makefile) e-mailing a
     context diff will do.  The e-mail address to be used is
     <[email protected]>

IV)  It is not allowed to remove this license from the distribution of the Vim
     sources, parts of it or from a modified version.  You may use this
     license for previous Vim releases instead of the license that they came
     with, at your option.
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from GitHub and can be verified like this:

1. Download the following zips:
  32-Bit: <>
  64-Bit: <>
2. You can use one of the following methods to obtain the SHA256 checksum:
  - Use powershell function 'Get-FileHash'
  - Use Chocolatey utility 'checksum.exe'

  checksum32: EA8E883F34E5B2B7558B3F2BC102588285BC49156F980E35D932F3666DB60667
  checksum64: C80AA8EC5CE33580010BB03F00610C8A12287C79CE2F3D3A19249F4787F641D3
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installDir = Get-Content "$toolsDir\installDir"
$shortversion = '82'
try {
  # Is dlls locked?
  Remove-Item "$installDir\vim\vim$shortversion\GvimExt32\gvimext.dll", "$installDir\vim\vim$shortversion\GvimExt64\gvimext.dll" -ErrorAction Stop
} catch {
  # Restart explorer to unlock dlls
  Write-Debug 'Restarting explorer.'
  Get-Process explorer | Stop-Process -Force
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$shortversion = '82'
$pp = Get-PackageParameters

. $toolsDir\helpers.ps1
$installDir = Get-InstallDir

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $installDir
  file          = "$toolsDir\"
  file64        = "$toolsDir\"

$installArgs = @{
  statement = Get-Statement
  exeToRun  = "$installDir\vim\vim$shortversion\install.exe"

'$installDir', ($installDir | Out-String), '$packageArgs', ($packageArgs | Out-String), '$installArgs', ($installArgs | Out-String) | ForEach-Object { Write-Debug $_ }

Install-ChocolateyZipPackage @packageArgs
Start-ChocolateyProcessAsAdmin @installArgs
Copy-Item -Path "$installDir\vim\vim$shortversion\vimtutor.bat" -Destination $env:windir
Set-Content -Path "$toolsDir\installDir" -Value $installDir
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installDir = Get-Content "$toolsDir\installDir"
$shortversion = '82'
$statement = '-nsis'
$exeToRun  = "$installDir\vim\vim$shortversion\uninstall.exe"
# From vim-tux.install.  Make input.
Set-Content -Path "$env:TEMP\vimuninstallinput" -Value 'y'
Start-Process -FilePath $exeToRun -ArgumentList $statement -RedirectStandardInput "$env:TEMP\vimuninstallinput" -Wait -WindowStyle Hidden
Remove-Item "$env:TEMP\vimuninstallinput"
Remove-Item "$env:windir\vimtutor.bat"
Remove-Item "$installDir\vim" -Recurse -Force
md5: 5334BB4DCA071C12CF25A63406BD7B12 | sha1: BAE8BE87DF489B858A6A66FFA7AFC1B34DDD28FA | sha256: C80AA8EC5CE33580010BB03F00610C8A12287C79CE2F3D3A19249F4787F641D3 | sha512: 32356E1BE710594EA9A9E2DA22A6B71321EB012200A8F935E25AB206CAF7DBB76F49729F90A2D401AF76DA31AAD60536AC2B600752FE11D624AB657C617C09DE
md5: 3509111B73295D9A63573937649997B7 | sha1: 8DDFF3C16E2D09077AFE94A34519197D38718D3B | sha256: EA8E883F34E5B2B7558B3F2BC102588285BC49156F980E35D932F3666DB60667 | sha512: 9E7FC68715A6F04D194F872D6613EC4696DB6079CAB2DF0800E1B57F15E763AAF2953CCCD61B695D35C238ADE650A7560E7407B77E17BABBB1B2F5A56F0981BE
function Get-InstallDir()
  if ($pp['InstallDir']) {
    Write-Debug '/InstallDir found.'
    return $pp['InstallDir']
  return Get-ToolsLocation
function Get-Statement()
  $options      = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff -install-openwith -add-start-menu'
  $createvimrc  = '-create-vimrc -vimrc-remap no -vimrc-behave default -vimrc-compat all'
  $installpopup = '-install-popup'
  $installicons = '-install-icons'
  if ($pp['RestartExplorer'] -eq 'true') {
    Write-Debug '/RestartExplorer found.'
    Get-Process explorer | Stop-Process -Force
  if ($pp['NoDefaultVimrc'] -eq 'true') {
    Write-Debug '/NoDefaultVimrc found.'
    $createvimrc = ''
  if ($pp['NoContextmenu'] -eq 'true') {
    Write-Debug '/NoContextmenu found.'
    $installpopup = ''
  if ($pp['NoDesktopShortcuts'] -eq 'true') {
    Write-Debug '/NoDesktopShortcuts found.'
    $installicons = ''
  return $options, $createvimrc, $installpopup, $installicons -join ' '
# Replace old ver dir with symlink
# Use mklink because New-Item -ItemType SymbolicLink doesn't work in test-env
# Use rmdir because Powershell cannot unlink directory symlink
function Create-SymbolicLink()
  Get-ChildItem -Path "$installDir\vim" -Exclude "vim$shortversion" -Attributes Directory+!ReparsePoint | ForEach-Object { Remove-Item $_ -Recurse ; New-Item -Path $_ -ItemType Directory }
  Get-ChildItem -Path "$installDir\vim" -Exclude "vim$shortversion" -Attributes Directory | ForEach-Object { $_.Name } | ForEach-Object { cmd /c rmdir "$installDir\vim\$_" ; cmd /c mklink /d "$installDir\vim\$_"  "$installDir\vim\vim$shortversion" }

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.

Version Downloads Last Updated Status
Vim 8.2.1920 1388 Thursday, October 29, 2020 Approved
Vim 8.2.1913 787 Wednesday, October 28, 2020 Approved
Vim 8.2.1910 1689 Tuesday, October 27, 2020 Approved
Vim 8.2.1905 1631 Monday, October 26, 2020 Approved
Vim 8.2.1900 1499 Sunday, October 25, 2020 Approved
Vim 8.2.1895 1398 Saturday, October 24, 2020 Approved
Vim 8.2.1891 1670 Friday, October 23, 2020 Approved
Vim 8.2.1883 1452 Thursday, October 22, 2020 Approved
Vim 8.2.1873 1840 Wednesday, October 21, 2020 Approved

This package has no dependencies.

Discussion for the Vim Package

Ground Rules:

  • This discussion is only about Vim and the Vim 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 Vim, 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