-
Notifications
You must be signed in to change notification settings - Fork 520
Closed
Labels
Issue-BugA bug to squash.A bug to squash.Needs: Author FeedbackPlease give us the requested feedback!Please give us the requested feedback!
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all open and closed issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
- If this is a security issue, I have read the security issue reporting guidance.
Summary
When performing the following, not all packages are available:
Find-PackageProvider -Name *
Bellow when executed from Windows Terminal

Bellow when executed from VSCode PowerShell Extension

PowerShell Version
Name Value
---- -----
PSVersion 5.1.22621.3880
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.3880
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Name : ConsoleHost
Version : 5.1.22621.3880
InstanceId : 405721b7-b9c0-4b24-a29c-afe9d3af86fa
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-AU
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspaceVisual Studio Code Version
1.91.1
f1e16e1e6214d7c44d078b1f0607b2388f29d729
x64Extension Version
ms-vscode.powershell@2024.2.2Steps to Reproduce
Type the following in both console and vsextension
Find-Package -Name *
Visuals
No response
Logs
No response
Metadata
Metadata
Assignees
Labels
Issue-BugA bug to squash.A bug to squash.Needs: Author FeedbackPlease give us the requested feedback!Please give us the requested feedback!