[vim/vim] Wrong DisplayVersion registry key written in Windows 11 (Issue #14629)

35 views
Skip to first unread message

jonathan-b-wiebe

unread,
Apr 24, 2024, 2:42:26 PM4/24/24
to vim/vim, Subscribed

Steps to reproduce

  1. Open a terminal and install vim using the command 'winget install vim.vim'. As of today Vim 9.1.0312_x64.exe is downloaded and installed.
  2. Type the command 'winget upgrade'. The results will show that version 9.1.0 is installed and 9.1.0312 is available.
  3. Open vim. This will show that installed version is indeed 9.1.0312.
  4. Open the registry editor and go to the key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim 9.1
  5. Note that the DisplayVersion is set t0 9.1.0. This is also the source of the version shown in Settings -> Apps -> Installed Apps.
  6. Manually installing the latest version from the vim-win32-installer site (9.1.0368) will update the registry key to 9.1.0000, which is still incorrect.

Expected behaviour

  1. Winget should show that version 9.1.0312 is installed and not show that an update is available.
  2. Settings -> Apps -> Installed Apps should show version 9.1.312 is installed.
  3. The registry key should be set to 9.1.0312.

Version of Vim

9.1.0312

Environment

Windows 11-23H2

Logs and stack traces

No response


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629@github.com>

Christian Brabandt

unread,
Apr 24, 2024, 3:03:54 PM4/24/24
to vim/vim, Subscribed

Isn't that a problem with winget then, if it works when manually installing?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075640475@github.com>

jonathan-b-wiebe

unread,
Apr 24, 2024, 3:21:04 PM4/24/24
to vim/vim, Subscribed

Manually installing the latest version from the vim-win32-installer site (9.1.0368) will update the registry key to 9.1.0000, which is still incorrect. The registry key should be set to 9.1.0312.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075670695@github.com>

Christian Brabandt

unread,
Apr 24, 2024, 3:37:54 PM4/24/24
to vim/vim, Subscribed

I don't think this is true, here on my current system (Win10), it shows the correct version:
grafik.png (view on web)
grafik.png (view on web)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075701905@github.com>

jonathan-b-wiebe

unread,
Apr 24, 2024, 3:52:10 PM4/24/24
to vim/vim, Subscribed

I have re-installed using the same version you are running (9.1.0136) and it indeed works correctly.
I will uninstall and reinstall with newer versions to determine when this behavour started.
Thanks for your help!


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075726059@github.com>

jonathan-b-wiebe

unread,
Apr 24, 2024, 4:10:31 PM4/24/24
to vim/vim, Subscribed

I can now confirm that this behaviour started somewhere between version 9.1.0282 and 9.1.0296. I cannot get move exact then this because these are two consecutive released on the vim-win32-installer site and I am not set up to compile vim in order to test the intermediate versions between these.
Installing version 9.1.0282 shows the following in the registry:
image.png (view on web)
Installing version 9.1.0296 shows the following:
image.png (view on web)
Re-installing version 9.1.0282 returns the key to the correct value.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075754492@github.com>

Restorer

unread,
Apr 24, 2024, 4:21:30 PM4/24/24
to vim/vim, Subscribed

@jonathan-b-wiebe
And can you please install the latest version with “vim-win32-install” and see what you get in your registry?
https://github.com/vim/vim-win32-installer/releases/tag/v9.1.0368


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075773757@github.com>

Christian Brabandt

unread,
Apr 24, 2024, 4:25:06 PM4/24/24
to vim/vim, Subscribed

Hm, I don't see any potential changes between v9.1.282 and v9.1.296 that could cause this.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075780272@github.com>

Christian Brabandt

unread,
Apr 24, 2024, 4:27:09 PM4/24/24
to vim/vim, Subscribed

I guess this one here: vim/vim-win32-installer@672d8c5 ?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075783482@github.com>

jonathan-b-wiebe

unread,
Apr 24, 2024, 4:28:03 PM4/24/24
to vim/vim, Subscribed

Installing gvim_9.1.0368_x64.exe results in the following registry key:
image.png (view on web)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075784803@github.com>

Restorer

unread,
Apr 24, 2024, 4:29:04 PM4/24/24
to vim/vim, Subscribed

I'm afraid it has to do with this pull request #338 and #14471


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075786178@github.com>

Restorer

unread,
Apr 24, 2024, 4:29:49 PM4/24/24
to vim/vim, Subscribed

Installing gvim_9.1.0368_x64.exe results in the following registry key:

Thank you. I'll check it out now.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075787518@github.com>

Restorer

unread,
Apr 24, 2024, 6:08:48 PM4/24/24
to vim/vim, Subscribed

That's probably it.
https://github.com/vim/vim/blob/a4c085a3e607bd01d34e1db600b6460fc35fb0a3/src/dosinst.c#L1657

It's possible that this should fix it.

diff --git a/src/Make_mvc.mak b/src/Make_mvc.mak
index aec9efaf9..4d03a722b 100644
--- a/src/Make_mvc.mak
+++ b/src/Make_mvc.mak
@@ -1321,6 +1321,10 @@ $(OUTDIR):
 
 CFLAGS_INST = /nologo /O2 -DNDEBUG -DWIN32 -DWINVER=$(WINVER) -D_WIN32_WINNT=$(WINVER) $(CFLAGS_DEPR)
 
+!IFDEF PATCHLEVEL
+CFLAGS_INST=	$(CFLAGS_INST) -DVIM_VERSION_PATCHLEVEL=$(PATCHLEVEL)
+!ENDIF
+
 install.exe: dosinst.c dosinst.h version.h
 	$(CC) $(CFLAGS_INST) dosinst.c kernel32.lib shell32.lib \
 		user32.lib ole32.lib advapi32.lib uuid.lib \

I'll have to check it again.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2075934551@github.com>

Restorer

unread,
Apr 25, 2024, 6:43:48 AM4/25/24
to vim/vim, Subscribed

Yeah, everything seems to be working as it should.
prg-vim-inst-ptchlvl.png (view on web)
reg-vim-inst-ptchlvl.png (view on web)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/14629/2076887976@github.com>

Christian Brabandt

unread,
Apr 25, 2024, 3:29:18 PM4/25/24
to vim/vim, Subscribed

Closed #14629 as completed via ec67ee0.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/14629/issue_event/12614395976@github.com>

Reply all
Reply to author
Forward
0 new messages