Better support for system context

[denelon]

Description of the new feature / enhancement

When customers are using WinGet via the system context, several challenges arise.

One of the challenges is installing, updating WinGet in the system context. The other class of problems is related to installers that require a logged in user (MSIX packages), or packages installed in user context (HKCU registry keys).

Proposed technical implementation details

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• System Context (#3049), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[mdanish-kh]

[Policy] Context-System

[denelon]

Try:

Install-WinGetPackage <package ID> -Scope System for MSIX based applications. This should set the package up to be registered for each user upon login.

[denelon]

In the system context, only packages supporting "machine" scope should be allowed by default.

If a user specifies "--force" this can be overridden, but the installer may not honor the user's intent.

There may be scenarios for some portable packages where it makes sense for the system context, but that will need to be investigated.