microsoft / microsoft/winget-pkgs
[Package Issue]: Microsoft.PowerShell
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Other
Brief description of your issue
After updating Microsoft.PowerShell to the latest version (v7.3.3), winget still shows that an update is available for the app (even after Terminal relaunch).
Steps to reproduce
- Install
Microsoft.PowerShell 7.3.2.0. - Run
winget upgrade Microsoft.PowerShell. - The app will be updated.
- Close the Terminal app.
- Run
winget list Microsoft.PowerShell. - See that the version remains
7.3.2.0.
Actual behavior
Do not try to update Microsoft.PowerShell after updating it.
Expected behavior
The app gets updated but the version number will be the old one within winget package manager.
Environment
> winget --info
Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.2728
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
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
Screenshots and Logs

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 listed winget upgrade Microsoft.PowerShell and winget list Microsoft.PowerShell commands, then inspect the Microsoft.PowerShell package manifest in this repository. Confirm whether the manifest or installed-package detection reports 7.3.2.0 after installing 7.3.3; done means winget reports the installed version correctly and no longer offers the same upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100