Steps to reproduce
After installing Vim with any of the signed executable installer (x86, x64, arm64), the actual program executables in the installation folder are not signed (e.g. C:\Program Files\Vim\vim.exe).
Only the installer itself is signed.
Expected behaviour
I would expect the actual Vim application files to be signed too. As is the case with the zip archive.
A signed installer with an unsigned application is is only half a solution. The app is still treated as unsigned by Windows.
Specifically when running Vim on my company computer, the program is notably slower than a fully signed version.
Version of Vim
any
Environment
Windows 11 25H2 64-bit
I have tested the gvim_9.2.1061_x64_signed.exe, gvim_9.2.1031_x64_signed.exe, and gvim_9.2.0958_x64_signed.exe installers. All contain unsigned files. Whereas the application files in gvim_*_x64_signed.zip are signed.
Steps to reproduce
After installing Vim with any of the signed executable installer (x86, x64, arm64), the actual program executables in the installation folder are not signed (e.g. C:\Program Files\Vim\vim.exe).
Only the installer itself is signed.
Expected behaviour
I would expect the actual Vim application files to be signed too. As is the case with the zip archive.
A signed installer with an unsigned application is is only half a solution. The app is still treated as unsigned by Windows.
Specifically when running Vim on my company computer, the program is notably slower than a fully signed version.
Version of Vim
any
Environment
Windows 11 25H2 64-bit
I have tested the gvim_9.2.1061_x64_signed.exe, gvim_9.2.1031_x64_signed.exe, and gvim_9.2.0958_x64_signed.exe installers. All contain unsigned files. Whereas the application files in gvim_*_x64_signed.zip are signed.