microsoft / microsoft/winget-pkgs
[Package Issue]: Microsoft.Teams detecting installer as the program itself
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
Multiple installed packages found.
Brief description of your issue
Winget seems to view the Teams Machine-Wide Installer as an instance of Teams itself. Could possibly explain https://github.com/microsoft/winget-pkgs/issues/61420
Steps to reproduce
winget upgrade
Actual behavior
Name Id Version Available Source
------------------------------------------------------------------------------------------------
Microsoft Edge WebView2 Runtime Microsoft.EdgeWebView2Runtime 102.0.1245.30 102.0.1245.33 winget
Windows Terminal Microsoft.WindowsTerminal 1.12.10982.0 1.13.11431.0 winget
Microsoft Teams Microsoft.Teams 1.5.00.11163 1.5.00.12969 winget
WinDirStat WinDirStat.WinDirStat Unknown 1.1.2 winget
Microsoft Teams Microsoft.Teams 1.4.0.7174 1.5.00.12969 winget
5 upgrades available.
Expected behavior
just one instance of Teams in the list
Environment
Windows Package Manager v1.2.10941
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19044.1706
Package: Microsoft.DesktopAppInstaller v1.17.10941.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
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 duplicate Microsoft Teams entries with winget upgrade in the reported Windows Package Manager environment. Trace how the Teams Machine-Wide Installer is detected and identified, and consider the work complete when the upgrade list shows only one Teams instance without incorrectly treating the installer as Teams.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100