Run as SYSTEM user

[STG-Tanner]

Brief description of your issue

Winget fails to run under the SYSTEM account. #548 appears to have been addressed in the 1.3 milestone, yet there is no change in behavior.

Steps to reproduce

Attempt to execute 'winget' under the SYSTEM user

Expected behavior

Winget should run normally under SYSTEM

Actual behavior

Executing 'winget' returns the following:
'winget' is not recognized as an internal or external command, operable program or batch file.

Environment

Windows Package Manager v1.3.2091
Windows: Windows.Desktop v10.0.22000.795
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.0

[denelon]

The mechanism for running as system is being implemented as a part of the work we're doing for:

• Develop Intune integration #215

We're publishing a NuGet package that exposes an "in proc" COM API. The winget CLI is not directly available in the system context as it is delivered via MSIX in the "App Installer" package.

COM API Specification: - winget-cli/#888 - Com Api.md at master · microsoft/winget-cli (github.com)

idl: winget-cli/PackageManager.idl at master · microsoft/winget-cli (github.com)

Duplicate of #215

[ghost]

@STG-Tanner 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.