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

Microsoft Teams Failing to install #2051

Closed
Raffaello opened this issue Mar 30, 2022 · 3 comments
Closed

Microsoft Teams Failing to install #2051

Raffaello opened this issue Mar 30, 2022 · 3 comments
Labels
Resolution-Duplicate Issue is a duplicate
Milestone

Comments

@Raffaello
Copy link

Brief description of your issue

An Update of Microsoft Teams is reported to be available through WinGet CLI.

When doing the upgrade the MS Teams has errors:

(1/2) Found Microsoft Teams [Microsoft.Teams] Version 1.5.00.5967
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\raffa\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-Microsoft.Teams.1.5.00.5967-2022-03-30-09-14-37.697.log
Another version of this application is already installed.

As the error is Another version of this application is already installed,

Winget shouldn't propose it at all as an upgrade, maybe?.

Also it will be always displaying as an available upgrade when isn't possible to install it.

Steps to reproduce

install in your system MS Teams version 1.4.0.19572 then try to upgrade to 1.5.00.5967.

Basically, having this winget upgrade row displaying:

Microsoft Teams         Microsoft.Teams                1.4.0.19572    1.5.00.5967    winget

Expected behavior

the package should be upgraded to the version reported by winget.

specific behavior:

  1. It should uninstall old version and install the new version if can't upgrade directly(?).
  2. In this case is MS Teams that has a "challenging" installation so the responsibility will go on MS Teams, but in this case winget shouldn't display the upgrade available, or at least with some extra disclaimer information ....
  3. (optional) Ability to ignore a specific upgrade (this could be a feature of winget)

Actual behavior

It is failing to install due to MS Teams that can't be installed over another MS Teams version.

Here the install log's file:

MSI (s) (F4:98) [09:14:40:935]: Product: Teams Machine-Wide Installer -- Configuration failed.

MSI (s) (F4:98) [09:14:40:936]: Windows Installer reconfigured the product. Product Name: Teams Machine-Wide Installer. Product Version: 1.5.0.5967. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1638.

Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
{731F6BAA-A986-45A4-8936-7C3AAAAA760B}

Environment

Windows Package Manager (Preview) v1.3.692-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1586
Package: Microsoft.DesktopAppInstaller v1.18.692.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

As MS Teams is part of MS Office, it could be also because of this reason that it has a "challenging" upgrade.
my MS Office version is:

Version : 18.2110.13110.0
@ghost ghost added the Needs-Triage Issue need to be triaged label Mar 30, 2022
@Trenly
Copy link
Contributor

Trenly commented Mar 30, 2022

@denelon
Copy link
Contributor

denelon commented Mar 30, 2022

Duplicate of #752

@denelon denelon marked this as a duplicate of #752 Mar 30, 2022
@ghost
Copy link

ghost commented Mar 30, 2022

@Raffaello we've identified this Issue as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the referenced Issue. Thanks for your report! Be sure to add your 👍 to the other issue to help raise the priority.

@ghost ghost closed this as completed Mar 30, 2022
@ghost ghost added Resolution-Duplicate Issue is a duplicate and removed Needs-Triage Issue need to be triaged labels Mar 30, 2022
@denelon denelon added this to the v1.3-Client milestone Jun 21, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

3 participants