vim/vim-win32-installer

Vim Win32 Installer

Vim Installer and Archives (Win32 and Win64)

This is a project for building Nightly and Stable Vim Windows build snapshots automatically (more information).

Download and execute the most recent gvim_x.y.pppp_x86.exe file to install Vim (where x.y is the release version and pppp is the patch number). The exe files contain the (32bit) installer while the .zip files contain an archive of the 32bit (_x86) or 64bit versions (_x64). To install it, extract the archive and update your PATH variable. The installer will do that automatically and provide some additional extensions (e.g. Edit with Vim menu). The gvim...pdb.zip file only contains the corresponding pdb files for debugging the binaries.

If you need a dynamic interface to Perl, Python2, Python3, Ruby, TCL, Lua or Racket/MzScheme, make sure you also install the following. Vim will work without it, but some Plugin might need this additional dependency. (e.g. Gundo needs a working Python2 installation, Command-T needs a working Ruby installation and Neocomplete needs a working Lua installation). This means, those interpreters have to be installed in addition to Vim. Without it Vim won't be able to use that feature! You can find those interperters here:

• Strawberry Perl 5.32
• ActiveTcl 8.6.6 (currently disabled)
• LuaBinaries 5.4
• Python 2.7
• Python 3 3.8 or later
• Racket 8.7 (BC)
• RubyInstaller 3.2

Make sure that you install the same architecture (32bit/64bit) for those libraries that matches your Vim installation.

For Python 3, Vim is compiled against Python 3.12 using Stable ABI, and this allows you to use Python 3.8 or any later version. See also :help python3-stable-abi.

Additionally the binaries include the new terminal feature for Vim and therefore contain the winpty.dll (32bit or 64bit) and the winpty-agent.exe from the winpty repository. This feature is currently considered experimental. Read the help at :h terminal.txt for more information.

For supporting better encryption, it comes with the libsodium.dll from the libsodium repository See the help at :h 'cryptmethod' for more details.

Note: The zip archive might be considered unsecure in Windows, causing Windows to display a dialog box "These files might be harmful to your computer...". If you want to disable this warning, you need to "unblock" the zip file. Do that in the properties dialog of the zip file, first tab General and look for the security section and click on "Unblock". However using a signed release might prevent that behaviour in Windows eventually (see also next paragraph).

See: Vim Repository for the Vim source.

Custom Patches

Note: If you want to test some patches, place them in the patch directory with the extension .patch. They will be applied before building Vim and the binary will then be tested against the test suite.

Signed Builds

Creating a signed binary and installer still requires manual effort, therefore not every release will be signed. They will be provided on a best effort basis occasionaly. If there haven't been any signed releases for a long time, feel free to request a new one by creating an issue here.

Thanks to SignPath.io for providing a free code signing service and to the SignPath Foundation for a free code signing certificate to sign the builds.

Winget

The nightly builds will be automatically uploaded and submitted to the winget repository. So you can use the winget command line tool to update your vim installation and do not have to download and install new releases manually.

This is only done for the unsigned builds, because the signed builds currently still require some manual steps to complete.

There will be 2 different types of Releases submitted to the winget Repository:

1) vim.vim.nightly Releases

Every build will be uploaded to the winget package repository as vim.vim.nightly (nightly) build. You need to search for vim.vim.nightly.

2) vim.vim (stable) Releases

In addition, approximately every 100 releases, a new stable release will be uploaded to the winget repository using the 'vim.vim' identifier. This should happen approximately every month.

License & Copyright

Most work was done by Ken Takata (@k-takata) and Christian Brabandt (@chrisbra).

The Vim license applies (see :h license) to all the build scripts in this repository. Note, that Vim is included as a submodule and comes with its own license (although is also released under the Vim license).

vim-win32-installer's Issues

Python 3 - upgrade to 3.6.x

Hello,

Would it be possible to bump up the version of python supported in vim for windows?
-DDYNAMIC_PYTHON3_DLL=\"python35.dll\"

The latest python is 3.6.3:
https://www.python.org/downloads/release/python-363/

Python 3.5.4 is the last "bugfix" release of 3.5. The Python 3.5 branch has now entered "security fixes only" mode; going forward, the only improvements made in the 3.5 branch will be security fixes.

https://www.python.org/downloads/release/python-354/

Feature request: VisVim for Visual Studio and "OfficeVim" for Office

Hi,

I'm after an equivalent VisVim for Office application. There is Viemu but it doesn't work with my Office 2016 and cost ~100USD.

Can I request for a function to integrate VisVim with MS Office? I'm not programming in C/C++ so it is definitely hard for me, provided that Visvim can add function for Word.

Any suggestion?

Thanks!

Source code (v8.0.nnnn.zip and v8.0.nnnn.tar.gz) does not contain the Vim source code.

The Vim directory after archive extraction is empty.

Windows Defender: Trojan:Win32/Fuerboos.A!cl found in gvim_8.0.1216_x86.exe

When downloading the executable of gvim 8.0, Windows Defender finds a trojan: Trojan:Win32/Fuerboos.A!cl

The file is: gvim_8.0.1216_x86.exe

Enable terminal feature?

Need to escape `\` in titles

https://github.com/vim/vim-win32-installer/releases/tag/v8.1.0325

• 8.1.0321: 'incsearch' regression: /� highlights everything

\v is wrongly converted to � (U+FFFD). It seems that we need to escape \.

Virus Alert

This file gvim_8.1.0022_x86.exe contains a virus in the file uninstall-gui.exe according to McAfee.

Remove The Capation In Windows

I Want To Remove The Capation,I Try Many Times To modify The Source Code and Rebuild It,But Failed.Can You Help Me? Could You Consider Add A Option To Gvim Like Scroll Bar? Like This: set go-=C (Remove The Capation)

Python 3.6 support

I have installed python 3.6 on my computer, but
:python3 print("Hello world")
returns

E370: Could not load library python35.dll
E263: Sorry, this command is disabled, the Python library could not be loaded.

Do I need to downgrade Python to version 3.5?

Tcl DLL name is wrong

Since ActiveTcl 8.6.6, the DLL name had been changed from tcl86.dll to tcl86t.dll.
Vim 8.0.0989 supports the TCL_DLL compile option to set the DLL name.
See also: https://groups.google.com/d/msg/vim_dev/-66BRdu3Yx0/xbxozWVZAgAJ

However I'm not using the option now. When I tried to set it, if_tcl couldn't find the DLL on my AppVeyor account.
https://ci.appveyor.com/project/k-takata/vim-win32-installer/build/93/job/mw6tg69qf8lxvs6w#L966
This is really strange, because tcl86t.dll does exist in the $PATH:
https://ci.appveyor.com/project/k-takata/vim-win32-installer/build/93/job/mw6tg69qf8lxvs6w#L831

Possible options might be:

1. Find the cause and fix it. Use TCL_DLL=tcl86t.dll setting.
   Seems difficult.
2. Use TCL_DLL=tcl86t.dll setting. Skip tests for if_tcl.
   Users can use a DLL from ActiveTcl 8.6.6, but it is not tested.
3. Keep current setting (TCL_DLL=tcl86.dll). Don't skip tests for if_tcl.
   Users should use a DLL from ActiveTcl 8.6.4 or earlier, or one from MinGW.

Optional vim path in the PATH environment variable

Feature request

To make it possible to use vim from the cmd and powershell prompts.

Maybe the installer could have an option to add the path C:\Program Files\Vim\vim81 (to gvim.exe) to the PATH environment variable.

YouCompleteMe unavailable: requires Vim compiled with Python (2.7.1+ or 3.4+) support.

Python Version: 3.7.0
Problem: Imcompatible with YouCompleteMe (https://github.com/Valloric/YouCompleteMe).

Windows cannot find 'vim80\uninstall-gui.exe' and that file is absent from in recent packages

When uninstalling an older version of vim8, the vim8.1 installer complains:

Windows cannot find 'c:\apps\vim80\uninstall-gui.exe'.

Looking at the latest release, gvim_8.1.0229_x64.zip does not contain uninstall-gui.exe. It does contain uninstall.exe. Same for gvim_8.1.0229_x86.zip.

Did a rename occur? (I'm not sure if it ever existed. It's absent from my old 8.0.596 install too.)

Latest releases is deemed unsafe

The latest release when downloaded chrome browser reports to be unsafe and windows prevents installer from running

McAfee Virus Alert with gvim_8.1.0126_x86.exe

At work today (6/29/18), McAfee Enterprise 8.8 (last updated on 6/28/18) detected a virus when I ran the gvim_8.1.0126_x86.exe installer. To be specific, it quarantined the uninstall-gui.exe claiming it was RDN/Ransom.

I use Windows Defender at home and it did not detect any such issues with the same vim installer.

uninstall-gui.exe virustotal detection

The uninstall-gui.exe file is being matched on VirusTotal by a non-trivial number of AVs. See https://www.virustotal.com/en/file/6ccd82e1afb291fe95f8b2747d44359093163f5c18f22bd1135eec4b62b5990b/analysis/1533744730/ for more information.

Ruby support

Hello,
When I tried to use a plugin where ruby is needed, the launch fail.
Moreovor when I run :echo has('ruby') the answer is 0.
Is ruby supported whith this release?

Thanks a lot

Seeing a Command Prompt box flash quickly on Windows 10？

os：win10 64-bit
vim version：gvim_8.1.0053_x64.zip

my English is not good,I hope I can describe the problem clearly
ok，in my gvim, when I run :term, or run PlugInstall with vim-plug or other commands, I always see the Command Prompt box flash quickly, I have added the vim_installed_path to PATH,and I try to installed with the Self-installing executable,but the problem still exists
Does anyone have the same problem？or is somethings wrong in my settings
(my gvim works well but this problem confused me)

Mal/Generic-S detected by anti-virus software Sophos

I installed v8.0.1617 on my win7 and Sophos reported Mal/Generic-S' detected.

Please DO NOT delete $VIM/_vimrc by default

Hello! Can you set up to re-install GVim without deleting the $VIM/_vimrc file by
default? It is very inconvenient.

As l known, the gvim81.exe download from
https://www.vim.org/download.php#pc does not delete $VIM/_vimrc by default.

Thanks very much!

Cannot Set Font Properly in mui2.exe

Hello, I'm not trying to complain anything but to mention it if it is not a known issue. That is, it seems that I could not set guifont properly if there is a whitespace in between of the font name, like set guifont=foo\ bar:h10. But setting like set guifont=Consolas:h10 works fine. Also, using set guifont=* that invokes a font selector makes the font works properly. But then :set guifont echos something like guifont=foo_bar:h10:... which even I set the font by following the same full string it didn't work. Thanks.

Silent install of vim not so silent

Hello,

While writing some automation around installing vim on a couple hundred machines I noted that the /S argument is not that silent. I have also tried /VERYSILENT.

Specifically, how can I prevent this dialog box from popping up?

While this box is open the installer does not finish.

Respectfully,
Robert J.

“LANG” “language messages”parameter does not work

gvim8 Windows10_64 chinese
in _vimrc,

let $LANG = 'en_US.UTF-8'

or

language messages en

message is still chinese

System error on starting gvim

I installed a 32-bit signed installer of 8.1.1568 on Win7 x64 and when I start the gvim, the following pops up.

When I click OK, the program starts, but I have noticed, for example, that it's not possible to change the messages language. English is shown regardless of the value of $LANG, or after a command like ":lang mes de" for example.

Before I had the version 1324 installed, and that one was starting and working normally.

E370: Could not load library python36.dll

Hello,
I am using the lasversion of vim with dynamic support of python 3.
When I run :version, Vim is looking for Python36.DLL.
Python3 is installed in C:\Program Files (x86)\Python36-32, the DLL is in this folder and this folder is in the PATH. But when I run :python3 print("Hello world"), it returns
E370: Could not load library python36.dll
E263: Sorry this command is disabled, the Python library could not be loaded.
Thank you.

x86 binaries are not provided from v8.1.1045

Binaries for x86 are not provided from v8.1.1045

https://github.com/vim/vim-win32-installer/releases/tag/v8.1.1045
https://github.com/vim/vim-win32-installer/releases/tag/v8.1.1048

I'm not sure but auto build may be broken.

Add a 64-bit installer (gvim_8*_x64.exe)

I'm using 64-bit vim and would like to use the installer features (context menus, ...).

Any reason why there is no installer for 64-bit? Looks like the build script supports it but it's skipped at the end.

The latest installer contains the trojan Win32/Fuerboos.C!cl

Seems kinda bad:

x64 bit exe support?

Hello,

Thanks for publishing the windows builds of vim so frequently. Having gvim/vim on windows is a nice treat.

is it possible to provide x64 bit exe files for the nightly builds? It looks like the x86 exe builds are provided:
https://github.com/vim/vim-win32-installer/releases/tag/v8.0.1322

Thanks for the consideration!

j.b.

Build vim with Python 3.6 support

Hi

Python 3.6 has been around for a while. is it possible to build vim with python 3.6 please?

just a suggestion.

Thanks

Uninstall-gui - "Blocked threat" Win32:malware-gen.

After instalation on Windows 10 x64 - Avast Anivirus show popup "Win32:malware-gen"
and bloked file Uninstall-gui.exe

vim version: 8.1.77

Windows x86 build is broken

Can't use the latest version on win32

ActivePerl issues

The latest build failed because ActivePerl 5.24.1 is not available anymore:
https://ci.appveyor.com/project/chrisbra/vim-win32-installer/build/job/ak3qaap7yoqldbo5

The latest versions of ActivePerl are 5.26.1 and 5.24.3, but both provides only 64-bit builds.
32-bit versions of 5.26.0 and 5.24.0 are still available, but it might become unavailable in a few months.

We need to decide how to do with this. E.g.:

• Download 32-bit ActivePerl (5.26.0 or 5.24.0) and copy it into our repository.
• Request the AppVeyor support team to install the latest version of 32-bit ActivePerl.
• Stop enabling if_perl.
• Switch our installer to 64-bit version, because users may not get 32-bit ActivePerl near future.

Upgrade to Python 3.7

no x86 builds of nightly?

Hi @chrisbra,

Thanks for making the nightly builds of vim - really great for you to do so.

Since version https://github.com/vim/vim-win32-installer/releases/tag/v8.1.0127 there haven't been nightly builds of x86.

Is that deliberate - you're tired of the false positives from virus scanners, or an oversight?

Umlaut (ÖÄÜ) can`t be displayed...

Hello,

if I launch the german version of vim for windows I can`t see umlauts in the editor:

In the middle of the screen, you see 'für' wrong displayed.

Installed Vim does not add to runtimepath .vim/pack/*/start and opt directories

Hello,

After installing Vim using latest 64 bit installer, Vim runtimepath (:set) does not include, nor does loads plugins from .vim\pack\bundle\start or .vim\pack\bundle\opt directories.

Is it intentional? Of course, Vim under linux includes those directories. Also, Vim distributed by Git for Windows does include those directories.

Am I doing something wrong installing on Windows?

echo has("python3") returns 0

Hi

I am trying to find a Vim compiled with Python37, you claim it is compiled with python3, but the flag tells me the opposite. Am I missing something here? I tried both the x64 and x86 versions

Fail to load a proper Ruby DLL

The :ruby 2 command fails with E370 and E266 in my setup.

• My ruby DLL is present in $PATH and its name matches &rubydll.
• set rubydll=C:\Ruby24-x64\bin\x64-msvcrt-ruby240.dll still fails.

I am confused what goes wrong.

Fatal Python error

Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00003440 (most recent call first):

Question about License

I'm not too familiar with software licenses, but should there be a License file in this repository?

Standard user installation fails

Description

When trying to install gvim_8.1.0885_x64.exe as a standard (non-administrator) user.

Observed

An error dialog appeared, saying:

Error opening file for writing:
C:\Program Files\Vim\vim81\gvim.exe

Expected

When a non-administrator user starts the installer, then the User Account Control window asks for the administrator password.

What works

Right clicking on the installer and choosing Run as administrator, completes the installation without any issues.

Quickfix used too many buffer number

1, I usually go to buffers with number+tab (mapped to number+<C-^>), it's convinent when buffer numbers are small;
2, But, I found that everytime quickfix window opens, the used buffer number is increased. And I often toggle the quickfix window.
3, How can I keep the buffer number of quickfix fixed ? Thanks!

Gvim crash when executing ":py3 print(sys.version)"

If I execute other python-support plugin Ex command in Gvim, like :Leaderf, it crashed too.
Please check the screenshot below.

Gvim version:

Update diff.exe?

The diff.exe in the top-level directory in this repository says it's version 2.7:

>.\diff.exe --version
diff - GNU diffutils version 2.7

According to http://git.savannah.gnu.org/cgit/diffutils.git/tag/?h=v2.7 that version was released in 1994. Would it be possible to upgrade to a more recent version? I ran into this when trying to run a script that depends on --strip-trailing-cr on a system that had Vim's diff first in its path.

Alternatively you might consider placing utility programs in a separate, out-of-%PATH% directory similar to what Git for Windows does.

Remove experimental/recommended label

Can we remove the experimental/recommended labels from the releases page for the MUI installer? I think it is safe to assume now, that the 64bit installer works okay and there haven't been any changes for a while.

ping @k-takata

Virus detected?

Symantec on my machine quarantined the install -- the gvim_8.0.1417.exe executable -- because of the SONAR.PSDownloader!g1 in it.

Broken link to 64 bit build

The link to the 64 bit release for Windows at the vim website's download page is broken. (I am not sure if this is the right place to report this; probably it is!?)

Windows binary version not provided for download as usual

Hi,

I often check for the recent version of vim released here. However, in a week, only source zips were provided.

Was there any big issue with the site?

Thanks

TN

blank menubar

Hi, no menubar shown in gvim, just blank white rectangle.
i tried almost every vim installer from vim.org, they are all same blank.
my pc environment is win7 64bit.