Open pamanes opened 3 months ago
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!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Does it do the same thing with winget list -e --id 'Microsoft.PowerShell'
?
I wasn't able to reproduce this behavior on my system:
PS C:\ManVal> winget list powershell
Name Id Version Source
---------------------------------------------------------------
PowerShell 7-x64 Microsoft.PowerShell 7.4.4.0 winget
Windows Terminal Microsoft.WindowsTerminal 1.20.11781.0 winget
PS C:\ManVal> winget list --id "Microsoft.PowerShell"
Name Id Version Source
-----------------------------------------------------
PowerShell 7-x64 Microsoft.PowerShell 7.4.4.0 winget
I think winget applies a regex type pattern. That's why there is the --exact
parameter.
PS C:\> winget list --id "Microsoft.PowerShell"
Name Id Version Source
---------------------------------------------------------------------
PowerShell 7-x64 Microsoft.PowerShell 7.4.4.0 winget
PowerShell 7-preview-x64 Microsoft.PowerShell.Preview 7.5.0.3 winget
PS C:\> winget list --id "Microsoft.PowerShell" --exact
Name Id Version Source
-----------------------------------------------------
PowerShell 7-x64 Microsoft.PowerShell 7.4.4.0 winget
Brief description of your issue
Listing installed packages by Id for Microsoft.PowerShell returns: No installed package found matching input criteria.
I know it is installed because this returns correctly:
Steps to reproduce
Install package Microsoft.PowerShell then run:
winget list --id "Microsoft.PowerShell"
Expected behavior
Should return the installed package.
Actual behavior
Environment