Find-WinGetPackage fails with "Windows Package Manager Group Policy Settings" error in VSCode PowerShell Extension Terminal #5266
Replies: 3 comments
-
I have exactly the same problem. |
Beta Was this translation helpful? Give feedback.
-
My TEMPORARY workaround looks like this: |
Beta Was this translation helpful? Give feedback.
-
the same thing. if I select |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When running a .ps1 script in the PowerShell Extension Debug Terminal in VSCode, executing the Find-WinGetPackage command results in the following error:
However, when I execute the same command in the default PowerShell Terminal within VSCode, it works as expected without any errors.
I am unsure if this issue is related to the VSCode PowerShell extension, WinGet itself, or a misconfiguration on my end. For now, I am opening this discussion here to determine if it is a known issue with Windows Package Manager.
Steps to Reproduce
Find-WinGetPackage -Name terminal
Beta Was this translation helpful? Give feedback.
All reactions