Installer failed while installing AnyDesk and Microsoft Teams

[sanamhub]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Installer failed while installing AnyDesk and Microsoft Teams

AnyDesk: AnyDeskSoftwareGmbH.AnyDesk

Microsoft Teams: Microsoft.Teams

Steps to reproduce

1. Open terminal
2. Type winget upgrade --all
3. Hit enter

Actual behavior

Errors while installing some packages (screenshot below)

Expected behavior

Install success

Environment

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

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

_No response_

[OfficialEsco]

AnyDesk requires Powershell to be run as Administrator, this is already implemented in the Manifest but winget-cli does not know what to do with it yet.

winget-pkgs/manifests/a/AnyDeskSoftwareGmbH/AnyDesk/ad 7.0.6/AnyDeskSoftwareGmbH.AnyDesk.installer.yaml

Line 38 in a133a9a

ElevationRequirement: elevationRequired

Microsoft Teams cooould still have the issues with the Machine-Wide and Per user Installation (the logs as requested would be helpful.)

[denelon]

Related to:

• Add messaging to support package specific elevation requirements winget-cli#1537

[Trenly]

Thank you for taking the time to report this issue. In the amount of time the issue has been open, there have been several updates to the WinGet CLI which may have helped mitigate some of these concerns. I encourage you to try out the latest version of the CLI and see if your problem still persists.

If additional problems persist, it would be extremely helpful if a new issue could be opened. Thanks!

Close with reason: Stale;