"winget install [package id]" should almost never be ambiguous

[DHowett]

Brief description of your issue

I've tried to install a package using its ID and been told that it is ambiguous.

% winget search signal
Name                                                   Id                             Version       Match       Source
-----------------------------------------------------------------------------------------------------------------------
...
Signal                                                 OpenWhisperSystems.Signal      5.19.0                    winget
...

% winget install OpenWhisperSystems.Signal
Multiple packages found matching input criteria. Please refine the input.
Name               Id                        Source
----------------------------------------------------
Time Speaker Clock 9WZDNCRDHNXW              msstore
Signal             OpenWhisperSystems.Signal winget

"Time Speaker Clock" didn't even come up for search, which was using an even less restrictive keyword than "OpenWhisperSystems.Signal".

I am aware of --id, but I do not think that the user should need to memorize arcane incantations for simple tasks. 😄

Expected behavior

It installs the one, the only, package identified by the ID OpenWhisperSystems.Signal.

Environment

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

Windows: Windows.Desktop v10.0.22474.1000
Package: Microsoft.DesktopAppInstaller v1.16.12702.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

[Jaifroid]

And I would add that monikers should be unique. This was raised in #1568 , but that issue was closed in favour of #1523, the title of which doesn't really reflect the problem of multiple packages being found despite an ID or moniker being specified.

[denelon]

We're still making improvements to the "msstore" source. I've commented on several issues, and provide guidance in the recent blog post. I expect we will have substantial improvements in this area in the coming days.

[denelon]

Duplicate of #1524

Dustin L. Howett (@DHowett) 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.

[DHowett]

For what it’s worth: as a naive user, I could not have known that this is a bug with the *msstore* source specifically. Perhaps some user education on how that source is bad would go a long way? The blog post doesn’t mention anything about this case.