Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug trying to update my microsoft teams application #3893

Open
SourcierDeVerite opened this issue Nov 15, 2023 · 4 comments
Open

Bug trying to update my microsoft teams application #3893

SourcierDeVerite opened this issue Nov 15, 2023 · 4 comments
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@SourcierDeVerite
Copy link

SourcierDeVerite commented Nov 15, 2023

Brief description of your issue

I use Microsoft Teams with my Office 365 School Account. When I try to update it with Winget, I see two packages with the same id and when I try specifying the id, I get the error message "No installed packages match the criteria entered." (My WInget is in French so I tried to translate the messages as best I could).

Steps to reproduce

# winget upgrade

The following packages have an upgrade available, but require explicit targeting for upgrade:
Nom                          ID              Version      Available           Source
-------------------------------------------------------------------------------------
Microsoft Teams classic      Microsoft.Teams 1.6.00.30666 23257.2618.2432.4374 winget
Teams Machine-Wide Installer Microsoft.Teams 1.5.0.8070   23257.2618.2432.4374 winget

# winget upgrade Microsoft.Teams
No installed package found matching input criteria.

Expected behavior

Upgrade one or all packages with the id Microsoft.Teams

Actual behavior

Error Message "No installed package found matching input criteria"

Environment

Copyright (c) Microsoft Corporation. All rights reserved.

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

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
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Nov 15, 2023
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. Area-Matching Issue related to correlation between installed package and manifest and removed Needs-Triage Issue need to be triaged labels Nov 15, 2023
@denelon
Copy link
Contributor

denelon commented Nov 15, 2023

The conflict is happening with the "Teams Machine Wide Installer". One of the work arounds is to pin that package to block WinGet from trying to update it.

@SourcierDeVerite
Copy link
Author

SourcierDeVerite commented Nov 16, 2023

It's look like I can't pin only "Teams Machine-Wide Installer" without pin also "Microsoft Teams":

# winget pin add "Teams Machine-Wide Installer"
Found Microsoft Teams [Microsoft.Teams]
Pin successfully added

# winget pin list
Name                   ID                        Source of pin
--------------------------------------------------------------------
Microsoft Teams        Microsoft.Teams           winget Pinning

Also, I cannot remove it from pin list:

# winget pin remove "Microsoft.Teams"
No installed package found matching input criteria.

# winget pin remove "Microsoft Teams"
No installed package found matching input criteria.

@denelon
Copy link
Contributor

denelon commented Nov 16, 2023

Could you try to uninstall Teams Machine Wide Installer via Settings and see if that helps?

I've seen several reports where the Machine Wide Installer is being recognized as the Teams application. The Machine Wide Installer is normally present on devices where Teams was installed for the user rather than the system.

@denelon denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Nov 16, 2023
@SourcierDeVerite
Copy link
Author

I uninstalled Teams Machine Wide Installer via settings, but it also uninstalled Teams, so I reinstalled it via Winget:

# winget install "Microsoft.Teams"
Found Microsoft Teams [Microsoft.Teams] Version 23257.2618.2432.4374
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://statics.teams.cdn.office.net/production-windows-x64/23257.2618.2432.4374/MSTeams-x64.msix
  ██████████████████████████████   120 MB /  120 MB
Successfully verified installer hash
Starting package install...
  ██████████████████████████████  100%
Successfully installed

# winget upgrade "Microsoft.Teams"
No available upgrade found.
No newer package versions are available from the configured sources.

This seems to have solved the problem, but like you said, there is a confusion between the installer and the application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

2 participants