Update via winget cause Windows Integration to not be reapplied

[theclickman]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

git version 2.50.0.windows.1
cpu: x86_64
built from commit: 311e67dc2479debe725dfb9a3f974bdce04644ea
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.14.1
OpenSSL: OpenSSL 3.2.4 11 Feb 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK

Windows version

Windows 11

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Microsoft Windows [Version 10.0.26100.4061]

Options set during installation

Editor Option: Notepad++
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable FSMonitor: Disabled

Other interesting things

I was having Git version 2.49.0 installed. Windows Explorer Integration was active and working.
I did a check on winget to see update to install and did see the update to 2.50.0.
I did apply the update via winget.
After update, Windows Integration was gone.
To fix it, I did download the update manually and reapplied it, uncheck "only show new options" to be able to elect the Windows Integration again.

The option should be stored and preserved after the update from the initial installation user selection.

Terminal/shell

bash

Commands that trigger the issue

winget upgrade Git.Git

Expected behaviour

As Windows Explorer Integration was selected on initial installation, windows integration should be still functionning after the upgrade

Actual behaviour

Windows Explorer integration was no longer visible in the "old" Windows context menu.

Repository

No response

[dscho]

winget isn't one of the upgrade paths that is supported by the Git for Windows project, and I am too unfamiliar to say whether there is any way to configure it to your liking (Windows Explorer integration being one of the configurable things). So I am afraid that we cannot help with this ask here.

[theclickman]

winget is only running the standard installer with an automated flow based on default value. nothing fancy here. It is likely to exclude it as Windows Explorer integration is not check by default.
But from the output of option stored in the /etc/install-options.txt file, seems the fact the integration was selected or not is not stored in the file to be reused by the update flow.

[dscho]

winget is only running the standard installer with an automated flow based on default value. nothing fancy here. It is likely to exclude it as Windows Explorer integration is not check by default.

I guess that's as good a reason as any to let winget remain an release vehicle that is not officially supported by Git for Windows.

[vitaminj]

From the looks of things, winget runs the git installer with /SP- /VERYSILENT /SUPPRESSMSGBOXES /NORESTART which previously has maintained all the settings, but with 2.50.0 this for me didn't upgrade correctly either. Sorry, I've manually fixed it now, so can't report what it did wrong, but it stopped using my windows OpenSSH keys.

This issue IMO warrants further investigation @dscho if anything has changed in your installer such that unattended mode behaves differently? I imagine enterprise users will use this option as well as winget users

[dscho]

This issue IMO warrants further investigation

@vitaminj if you truly think so, I invite you to contribute. There is code in Git for Windows' installer to simply use the settings chosen last time during upgrades. This option could be surfaced via a new command-line option that could then be added to the winget installer.