Repository navigation
. #5560
Copy link
Copy link
Closed as not planned
Labels
Issue-BugA bug to squash.A bug to squash.Needs: TriageMaintainer attention needed!Maintainer attention needed!
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
TOPICS
PowerShell Version
Name Value
---- -----
PSVersion 5.1.26100.8875
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.26100.8875
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1Visual Studio Code Version
1.130.0
x64Extension Version
ms-vscode.powershell@2025.4.0Steps to Reproduce
TOPICS
Visuals
No response
Logs
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Issue-BugA bug to squash.A bug to squash.Needs: TriageMaintainer attention needed!Maintainer attention needed!
Activity
github-actions commentedon Jul 28, 2026
This issue does not contain a real report — the title is
.and both the summary and reproduction steps contain only the placeholder text "TOPICS". There is no described problem, reproduction steps, or expected vs. actual behavior.If you encountered a genuine issue with the PowerShell extension, please open a new issue with a descriptive title, a clear summary of the problem, and steps to reproduce it. We'd be happy to help!