Downloads of v 8.2.0303:


Last Update:

23 Feb 2020

Package Maintainer(s):

Software Author(s):

  • Bram Moolenaar
  • Vim Community


vim editor vi gvim cli admin cross-platform foss vim-win32-installer


This is not the latest version of Vim available.

  • 1
  • 2
  • 3

8.2.0303 | Updated: 23 Feb 2020



Downloads of v 8.2.0303:



Software Author(s):

  • Bram Moolenaar
  • Vim Community

  • 1
  • 2
  • 3
Vim 8.2.0303

This is not the latest version of Vim available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vim, run the following command from the command line or from PowerShell:


To upgrade Vim, run the following command from the command line or from PowerShell:


To uninstall Vim, 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 vim -y --source="'INTERNAL REPO URL'" --version="'8.2.0303'" [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 vim -y --source="'INTERNAL REPO URL'" --version="'8.2.0303'" 

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

Exit $exitCode

- name: Install vim
    name: vim
    version: '8.2.0303'
    state: present

See docs at

chocolatey_package 'vim' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '8.2.0303'

See docs at

cChocoPackageInstaller vim
    Name     = "vim"
    Version  = "8.2.0303"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'vim':
  ensure   => '8.2.0303',
  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.

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

This package was approved as a trusted package on 23 Feb 2020.


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: E9EDA7E18866CC5D9F507CED7D3D89EB4CEDC8B7C8B4CD74E92E922D1F56FDBE
  checksum64: EA25A5E3C137D2D6B82E3B625B41C6B6AE7516C213835C3FF44FDAE4A54677E2
$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: 111F126F6AF2D9DFCBE62CCCE77EC80A | sha1: AE6E76B2EF66323AACEB6A3F06D5871501279440 | sha256: EA25A5E3C137D2D6B82E3B625B41C6B6AE7516C213835C3FF44FDAE4A54677E2 | sha512: A25FC23E035BF3F0D82CCE0E6403BB39F871F416FAB1BC783A284EF6B3CA97A1797A3F79E9ACDACE51F7ADD4EC4A609DAC461920BC991A81BF549CE34FED1535
md5: 40DA1B99C22A3F171E6DB025ED62DC32 | sha1: 0554A8F9AF5C99657B9FD48FA7921AF962729CEF | sha256: E9EDA7E18866CC5D9F507CED7D3D89EB4CEDC8B7C8B4CD74E92E922D1F56FDBE | sha512: 8DE3A7FC6F71F448DAEECEA6D037C2EBEC67707C188D62794DC9CE2E841FC8B915371B79EAC51471D5B6A3AE909D2D7B59D867CF75B96CC8C5D0A5A60D710F5D
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.

Add to Builder Version Downloads Last Updated Status
Vim 9.0.0669 1537 Thursday, October 6, 2022 Approved
Vim 9.0.0662 932 Wednesday, October 5, 2022 Approved
Vim 9.0.0654 1768 Tuesday, October 4, 2022 Approved
Vim 9.0.0643 1557 Monday, October 3, 2022 Approved
Vim 9.0.0636 953 Sunday, October 2, 2022 Approved
Vim 9.0.0631 976 Saturday, October 1, 2022 Approved
Vim 9.0.0626 1479 Friday, September 30, 2022 Approved
Vim 9.0.0619 1110 Thursday, September 29, 2022 Approved
Vim 9.0.0612 7 Wednesday, September 28, 2022
Waiting for Maintainer

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