Downloads of v 7.4.1089:


Last Update:

21 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Build: veegee developer: vim team


vim-x64 vim editor admin

Vim x64

This is not the latest version of Vim x64 available.

  • 1
  • 2
  • 3

7.4.1089 | Updated: 21 Jan 2016



Downloads of v 7.4.1089:



Software Author(s):

  • Build: veegee developer: vim team

  • 1
  • 2
  • 3
Vim x64 7.4.1089

This is not the latest version of Vim x64 available.

  • 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


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


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


To uninstall Vim x64, 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 vim-x64 -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 vim-x64 -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 vim-x64 installed
    name: vim-x64
    state: present
    version: 7.4.1089
    source: STEP 3 URL

See docs at

chocolatey_package 'vim-x64' do
  action    :install
  version  '7.4.1089'
  source   'STEP 3 URL'

See docs at

    Name: vim-x64,
    Version: 7.4.1089,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vim-x64
   Name     = 'vim-x64'
   Ensure   = 'Present'
   Version  = '7.4.1089'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'vim-x64':
  provider => 'chocolatey',
  ensure   => '7.4.1089',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vim-x64 version="7.4.1089" source="STEP 3 URL"

See docs at

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 21 Jan 2016.


64-bit Vim for 64-bit Windows, with 64-bit Python 2.7 and 3.4 support, 64-bit Lua 5.2 support, and 64-bit Ruby 2.0.0 support (via RubyInstaller). Compiled with HUGE feature set and full optimizations for speed.

$packageName = 'vim-x64'
$installerType = 'exe'
$silentArgs = '/S'
$version = '7.4.1089'
$url = "${version}_x64.exe"
$checksum = '7c8af950581c63d6523e6f2a8cde0f4f20a743bd'
$checksumType = 'SHA1'

if ( Test-Path -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim 7.4" ) {
# An uninstaller that doesn't accept arguments (nor does it even work) will run if this key exists
Remove-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim 7.4' -ErrorAction SilentlyContinue
# Manually uninstall, it must have tried to run an uninstaller for a reason
Write-Output "Rebooting explorer to release a handle"
Get-Process | Where { $ -eq 'explorer'      } | Stop-Process -Force
Get-Process | Where { $ -eq 'FreeCommander' } | Stop-Process -Force
Remove-Item -Path "$ENV:ProgramFiles\Vim" -Force -Recurse

Install-ChocolateyPackage $packageName $installerType $silentArgs $url -checksum $checksum -checksumType $checksumType

# This is a key presumably created for uninstalling context menu and other integrations
# UninstallString is invalid, other uninstaller handles that stuff just fine.
# This entry is just garbage/clutter and upsets chocolateyuninstall.ps1
Remove-Item -Path "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Vim_x64" -ErrorAction SilentlyContinue
$packageName = 'vim-x64'
$softwareName = 'Vim*'
$installerType = 'EXE' 
$silentArgs = '/S' # NSIS
$validExitCodes = @(0)
$uninstalled = $false
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

[array]$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"
    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
  # Since the uninstaller doesn't actually work... we have to manually remove vim-x64
  Write-Output "Rebooting explorer to release a handle"
  Get-Process | Where { $ -eq 'explorer'      } | Stop-Process -Force
  Get-Process | Where { $ -eq 'FreeCommander' } | Stop-Process -Force
  Remove-Item -Path "$ENV:ProgramFiles\Vim" -Force -Recurse -ErrorAction Stop
  Remove-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim 7.4'

} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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 x64 7.4.1817 246 Thursday, May 5, 2016 Approved
Vim x64 7.4.1796 411 Friday, April 29, 2016 Approved
Vim x64 7.4.1759 353 Thursday, April 21, 2016 Approved
Vim x64 7.4.1739 371 Friday, April 15, 2016 Approved
Vim x64 7.4.1713 440 Thursday, April 7, 2016 Approved
Vim x64 7.4.1709 367 Tuesday, April 5, 2016 Approved
Vim x64 7.4.1689 355 Thursday, March 31, 2016 Approved
Vim x64 7.4.1646 368 Friday, March 25, 2016 Approved
Vim x64 7.4.1641 345 Thursday, March 24, 2016 Approved

This package has no dependencies.

Discussion for the Vim x64 Package

Ground Rules:

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