microsoft / microsoft/winget-cli
`winget upgrade oh-my-posh --version 27.1.2` installs a second copy of the app instead of upgrading it
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
winget upgrade
Brief description of your issue
Context:
JanDeDobbeleer.OhMyPosh version 26.23.8 was installed machine-wide using an MSI, and my machines are configured to install machine-wide by default:
"installBehavior": {
"preferences": {
"scope": "machine",
"architectures": ["x64"]
}
}
Version 27.1.2's manifest specifies that MSIX installation is preferred, and this only supports per-user installation.
The problem:
Running winget upgrade oh-my-posh --version 27.1.2 on a machine with 26.23.8 installed machine-wide doesn't upgrade the existing app, but instead installs a second copy.
The result is:
PS❯ winget list JanDeDobbeleer.OhMyPosh
Name Id Version Source
--------------------------------------------------
Oh My Posh JanDeDobbeleer.OhMyPosh 27.1.2 winget
Oh My Posh JanDeDobbeleer.OhMyPosh 26.23.8 winget
PS❯ gcm oh-my-posh -all
CommandType Name Version Source
----------- ---- ------- ------
Application oh-my-posh.exe 26.23.8.0 C:\Program Files (x86)\oh-my-posh\bin\oh-my-posh.exe
Application oh-my-posh.exe 27.1.2.0 C:\Users\<REDACTED>\AppData\Local\Programs\oh-my-posh\bin\oh-my-posh.exe
Steps to reproduce
- Install
JanDeDobbeleer.OhMyPoshversion 26.23.8 machine-wide - Run
winget upgrade oh-my-posh --version 27.1.2
Expected behavior
Version 27.1.2 should replace version 26.23.8
Actual behavior
Version 27.1.2 is installed per-user next to version 26.23.8. And the latter is first on the PATH, so the new version isn't used.
Environment
Windows Package Manager v1.11.430
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.6396
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.430.0
Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
Configuration Modules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Admin Setting State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
DefaultProxy Disabled
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the machine-wide MSI and per-user MSIX upgrade scenario with the listed winget commands, then trace the upgrade path that selects installer scope. Done means upgrading the existing machine-wide installation without leaving a second per-user copy, with regression coverage for this scope mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100