microsoft / microsoft/winget-cli
Can't uninstall package when both x86 and x64 versions are installed
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)
No response
Brief description of your issue
On my machine I had following packages installed
- Microsoft.DotNet.DesktopRuntime.6 x64
- Microsoft.DotNet.DesktopRuntime.6 x86
Both were on the version 6.0.36
I wanted to uninstall x86 version but leave x64 installed
Winget didn't allow for that , either it suggested uninstalling all of them or supplying --version
Multiple versions of this package are installed. Either refine the search, pass the `--version` argument to select one, or pass the `--all-versions` flag to uninstall all of them.
I tried to check if uninstall has --architecture parameter, but unfortunately it's missing
When I supplied --version it uninstalled x64 version not x86
Steps to reproduce
- Install packages
winget install --id Microsoft.DotNet.DesktopRuntime.6 --architecture x64 --version 6.0.36 --scope machine
winget install --id Microsoft.DotNet.DesktopRuntime.6 --architecture x86 --version 6.0.36 --scope machine
- Try to uninstall package and see the issue
winget uninstall --id Microsoft.DotNet.DesktopRuntime.6
- Uninstall with supplying version parameter
winget uninstall --id Microsoft.DotNet.DesktopRuntime.6 --version 6.0.36
- uninstalled wrong package
Expected behavior
Winget should allow for uninstall correct architecture package
If install command has this option then by analogy it should be available for uninstall too.
Actual behavior
Currently winget doesn't uninstall package that I want and I need to fix machine after incorrect uninstall
Environment
Windows Package Manager v1.11.430
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22631.5909
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.430.0
Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
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 with the WinGet CLI uninstall command and compare its supported options with the install command's --architecture option. Reproduce the two x86/x64 installations using the commands in the issue, then verify that uninstall can select the requested architecture without removing the other package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100