[Package Issue]: Microsoft.Teams detecting installer as the program itself

cobalt2727 commented 2 years ago

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] 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

alanlivio commented 1 year ago

I get same error. Also, the upgrade is not able to be done.

C:\Users\alan>winget upgrade --all
Name                         Id                      Version    Available    Source
-----------------------------------------------------------------------------------
Teams Machine-Wide Installer Microsoft.Teams         1.5.0.8070 1.5.00.21668 winget
1 upgrade available.

(1/1) Found Microsoft Teams [Microsoft.Teams] Version 1.5.00.21668
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
Installer failed with exit code: 1638
Installer log is available at: C:\Users\alan\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-Microsoft.Teams.1.5.00.21668-2022-10-05-11-01-51.799.log
Another version of this application is already installed.

C:\Users\alan>winget --info
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22622.601
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.2161.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

kkbruce commented 1 year ago

always update error.

cobalt2727 commented 1 year ago

I'm encountering this as well

NJT145 commented 1 year ago

on me, this happens when I use --scope=machine option. For example: I use winget install -e -i --id=Microsoft.Teams --source=winget --scope=machine to install it. However, this installs installer to "C:\Program Files (x86)\Teams Installer" but not the app. This is the problem. The machine install manifest should be removed...

stevehipwell commented 1 year ago

Is this really that hard to fix?

C8H17OH commented 11 months ago

Even worse now, since there are Microsoft Teams classic, the new Teams (aka Teams 2.0) and "Teams Machine-Wide Installer." Lucky that the personal version of Teams does not join in such confusion.

marktab commented 1 week ago

I work for Microsoft as a Cloud Solution Architect: my use case are some older Windows 10 personal home machines which both show this message. I was noticing that the winget downloads code (presumably the update) but that the update does not install. Hopefully there will be a resolution, perhaps to not signal that an update should be applied.

microsoft / winget-pkgs