Downloads of v 7.4.1824:


Last Update:

10 May 2016

Package Maintainer(s):

Software Author(s):

  • Build:
  • Developer: vim team


vim-x64 vim editor tux admin

[Deprecated] Vim x64

  • 1
  • 2
  • 3

7.4.1824 | Updated: 10 May 2016



Downloads of v 7.4.1824:



Software Author(s):

  • Build:
  • Developer: vim team

  • 1
  • 2
  • 3
[Deprecated] Vim x64 7.4.1824

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall [Deprecated] 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.1824
    source: STEP 3 URL

See docs at

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

See docs at

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

Requires Otter Chocolatey Extension. See docs at

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

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vim-x64 version="7.4.1824" 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 04 Jul 2020.


Deprecated package, install Vim-Tux instead.##

Used libraries: Perl 5.22.1, Python 2.7.11, Python 3.5.1, Racket, Ruby 2.2.3, Lua 5.3.2, Tcl 8.6.4, libXpm.
Build provided by - consider donating to help support their server costs.

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 255 Thursday, May 5, 2016 Approved
Vim x64 7.4.1796 415 Friday, April 29, 2016 Approved
Vim x64 7.4.1759 362 Thursday, April 21, 2016 Approved
Vim x64 7.4.1739 382 Friday, April 15, 2016 Approved
Vim x64 7.4.1713 446 Thursday, April 7, 2016 Approved
Vim x64 7.4.1709 373 Tuesday, April 5, 2016 Approved
Vim x64 7.4.1689 370 Thursday, March 31, 2016 Approved
Vim x64 7.4.1646 375 Friday, March 25, 2016 Approved
Vim x64 7.4.1641 349 Thursday, March 24, 2016 Approved

Veegee has become inactive, switching to builds provided by

Discussion for the [Deprecated] Vim x64 Package

Ground Rules:

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