Upgrade with exact and id gives two results

[KalleDK]

Brief description of your issue

If I try to upgrade Microsoft Teams with exact id, I still get show two packages

Steps to reproduce

Both of these fails

winget upgrade --id Microsoft.Teams -e
winget upgrade --id Microsoft.Teams -e -s winget

Expected behavior

That the first entry is selected, as that is the one with the exact id

Actual behavior

winget upgrade --id Microsoft.Teams -e
Der blev fundet flere pakker, som matcher inputkriterierne. Du bedes finindstille input.
Navn            Id
-------------------------------
Microsoft Teams Microsoft.Teams
Microsoft Teams Teams

winget upgrade --id Microsoft.Teams -e -s winget
Der blev fundet flere pakker, som matcher inputkriterierne. Du bedes finindstille input.
Navn            Id
-------------------------------
Microsoft Teams Microsoft.Teams
Microsoft Teams Teams

Environment

[winget --info]
Windows Package Manager v1.0.11451
Copyright (c) Microsoft Corporation. Alle rettigheder forbeholdes.

Windows: Windows.Desktop v10.0.18362.1256
Pakke: Microsoft.DesktopAppInstaller v1.11.11451.0

Logfiler: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------------------
Erklæring om beskyttelse af personlige oplysninger https://aka.ms/winget-privacy
Licensaftale                                       https://aka.ms/winget-license
Meddelelser fra tredjepart                         https://aka.ms/winget-3rdPartyNotice
Startside                                          https://aka.ms/winget

Any other software?

[KalleDK]

It seems that a Machine Wide Teams was installed and a User version was installed. But still no way to disambiguate them afaik.

Which is apparently how Teams works... The machine wide installer, installs the user version on launch....

[OfficialEsco]

microsoft/winget-pkgs#14115

[jedieaston]

This looks to be another scenario in which a fix to #840 would be nice.

[denelon]

This should be resolved with the work in #1243 for #1073 when the last bit of work mentioned at #1073 (comment) is complete.

[denelon]

Is this still happening with Windows Package Manager 1.3 Release Candidate?

[ghost]

@KalleDK this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

[KalleDK]

@denelon - seems like it works now! Thank you