microsoft / winget-cli

WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
https://learn.microsoft.com/windows/package-manager/
MIT License
23.35k stars 1.45k forks source link

Cannot install Microsoft.Teams but could yesterday (0x80070002 : unknown error) #3818

Open robinmalik opened 1 year ago

robinmalik commented 1 year ago

Brief description of your issue

Hi,

Yesterday I was able to run winget install Microsoft.Teams from my laptop and it successfully installed the new v2 client (23257.2618.2432.4374, although the client itself then noted another update available).

Today I've tried to repeat this on my desktop (both W11, same winget version and desktop app installer version). I had to uninstall every instance of Microsoft Teams and reboot to stop winget from detecting version 1.6, and show the new version - this may be by design, and that's fine, but with the new version listed I'm unable to install it as it errors with Installer failed with exit code: 0x80070002 : unknown error

Log attached from winget install Microsoft.Teams --verbose-logs

WinGet-2023-10-27-08-26-01.961.log

Steps to reproduce

winget install Microsoft.Teams --verbose-logs

Expected behavior

Installs

Actual behavior

Does not install

Environment

Windows Package Manager v1.6.2771
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22635.2552
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2771.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
plyagent00 commented 1 year ago

Hi,

We face the same error as @robinmalik As a temporary workaround solution, we install the Classic version of Teams with --id "Microsoft.Teams.Classic", after the first run It asks the user whether He wants to switch to a new version or not, and after update, It works without issues.

Here's some output from log:

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... ????????????????????????????? 95% Installer failed with exit code: 0x80070002 : The system cannot find the file specified.

Zoriot commented 2 months ago

Same issue when trying to update Teams

Nicholas-SE commented 2 months ago

This is still happening, crazy I waited for New Teams to be THE Teams and MS still can't figure this out. The go to classic and upgrade option works but this seems like a major issue for anyone that wants to setup machines with Intune win32 apps calling winget. Does anyone know when this will be fixed?