Support for filtering packages on installer method

[denelon]

trafficstars

Several packages do not support or provide a silent install experience.

Assuming package manifests identify support for interactive installers, the client should be able to filter these packages so they aren't inadvertently executed for certain scenarios. The client should be able to support a preference for silent install experiences if specified. Additionally the client should be able to filter search results so that packages requiring interactive install can be omitted.

This could be implemented in settings, as well as via command-line arguments.

[denelon]

This feature is required prior to accepting "interactive only" installers into the community repository. Many users are looking for headless/unattended import capabilities.

[Trenly]

[Policy] Area-Settings

[upintheairsheep]

The fact dependency support was added before this simple issue is kinda weird.

[luzpaz]

Any traction here ? (asking due to #107357 being closed)

[SkylerWallace]

Would love to see this get looked at again. Requiring silent installation is a blocker for many programs. Notable ones include HP Support Assistant and Samsung Magician.

Add a boolean indicator in the manifest like InteractiveInstallOnly. Add a search filter to winget search that only lists installers that support silent install like --supports-silent.

[Dragon1573]

Currently we have InstallModesproperty in both schema v1.6.0 and v1.7.0. Changing this to a required property would help. Filter those who only contains interactive.