Downloads of v 0.4.3:


Last Update:

18 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Neovim contributors


vi vim gvim neovim text editor sublime atom emacs notepad


This is not the latest version of Neovim available.

0.4.3 | Updated: 18 Nov 2019



Downloads of v 0.4.3:


Software Author(s):

  • Neovim contributors

Neovim 0.4.3

This is not the latest version of Neovim available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Validation Testing Passed

Verification Testing Failed


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


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


To uninstall Neovim, 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

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade neovim -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 neovim -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure neovim installed
    name: neovim
    state: present
    version: 0.4.3
    source: STEP 3 URL

See docs at

chocolatey_package 'neovim' do
  action    :install
  version  '0.4.3'
  source   'STEP 3 URL'

See docs at

    Name: neovim,
    Version: 0.4.3,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller neovim
   Name     = 'neovim'
   Ensure   = 'Present'
   Version  = '0.4.3'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'neovim':
  provider => 'chocolatey',
  ensure   => '0.4.3',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install neovim version="0.4.3" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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


More powerful plugins

  • The msgpack API enables structured communication to and from any programming language.
  • Remote plugins run as co-processes that communicate with Neovim safely and asynchronously.

Better out-of-the-box

  • Strong defaults
  • Modern terminal features such as truecolor and bracketed paste
  • Built-in terminal emulator
  • First-class embedding
  • GUIs (or TUIs—such as readline) can nvim --embed or communicate via TCP socket using the discoverable msgpack API.

Drop-in replacement for Vim

  • Neovim is an extension of Vim: feature-parity and backwards compatibility are high priorities.
  • If you are already familiar with Vim, see :help nvim-from-vim to learn about the differences.

Following HEAD

  • If you want to stay up to date with the latest development you can install neovim using the --pre option.
  • For example: choco install neovim --pre.
  • Which will get you the latest nightly builds for windows.

Package Parametes

  • /NoNeovimOnPath: Neovim binary folder will not be added to the path.
    • Optional parameter.
    • Default behavior is that Neovim binary will be added to the path.
    • Example: choco install neovim --params "/NoNeovimOnPath"

Note: To force the installation of x32 version, use the --x86 argument with choco install.

# File:           chocolateybeforemodify.ps1
# Description:    Updating neovim
# Author:		    Reinaldo Molina
# Email:          rmolin88 at gmail dot com
# Revision:	    0.0.0
# Last Modified:  Fri Apr 20 2018 22:49
$packageName = "neovim"
$destDir = Join-Path $(Get-ToolsLocation) $packageName
Remove-Item $destDir -Force -Recurse

# Exit with the result of the last command
exit $?
# File:           chocolateyinstall.ps1
# Description:    Installation of Neovim
# Author:		    Reinaldo Molina
# Email:          rmolin88 at gmail dot com
# Revision:	    0.0.0
# Last Modified:  Fri Apr 20 2018 23:04

$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName= 'neovim' # arbitrary name for the package, used in messages
$destDir = Join-Path $(Get-ToolsLocation) $packageName
$url        = '' # download url, HTTPS preferred
$url64      = '' # 64bit URL here (HTTPS preferred) or remove - if installer contains both (very rare), use $url
$bin         = $destDir + '\Neovim\bin'

# Get user provided paramaters
# Help here:
$pp = Get-PackageParameters

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $destDir
  url           = $url
  url64bit      = $url64

  softwareName  = 'neovim*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique

	checksum      = '4f63f55697afaf4d9f82204768fd7ad3e98cc554f2745afd4a160d50a63d1025'
  checksumType  = 'sha256' #default is md5, can also be sha1, sha256 or sha512
	checksum64    = '549fd985e3e6207dc3d52d17fb2bc7957adc264f20b525fc7e62f8dc8c597931'
  checksumType64= 'sha256' #default is checksumType

  validExitCodes= @(0) #please insert other valid exit codes here

Install-ChocolateyZipPackage @packageArgs

# Adds neovim to the path if not present already
# Define option here and check at the same time
if (!$pp['NoNeovimOnPath']) {
	Install-ChocolateyPath -PathToInstall $bin
        Write-Output "Added Neovim binary folder to the user's PATH variable"

} else {
        Write-Output "Please note that Neovim binary folder will NOT be added to the path"

Write-Output "Please Consider donating"
Write-Output "Issues? Please visit"
# File:           chocolateyuninstall.ps1
# Description:    Uninstallation of neovim
# Author:		    Reinaldo Molina
# Email:          rmolin88 at gmail dot com
# Revision:	    0.0.0
# Last Modified:  Fri Apr 20 2018 22:50
$packageName= 'neovim' # arbitrary name for the package, used in messages
$destDir = Join-Path $(Get-ToolsLocation) $packageName
$bin         = $destDir + '\Neovim\bin'

Write-Output "Please manually remove `"$($bin)`" from the User PATH environment variable if not installing neovim again."

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
Neovim 0.5.0-beta 9794 Friday, April 3, 2020 Approved
Neovim 12 Monday, January 18, 2021 Approved
Neovim 0.4.5-beta 42 Thursday, August 13, 2020 Exempted
Neovim 0.4.4 20042 Wednesday, September 9, 2020 Approved
Neovim 0.4.3 26351 Monday, November 18, 2019 Approved
Neovim 0.4.2 5262 Monday, September 16, 2019 Approved
Neovim 0.3.8 5416 Friday, July 5, 2019 Approved
Neovim 0.3.7 2081 Friday, June 14, 2019 Approved

Release notes here.

Discussion for the Neovim Package

Ground Rules:

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