DIAGNOSTIC

Open
#5,596 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
powershell, typescript, vscode
Domain
devtools

Research direction

Start with docs/troubleshooting.md, then clarify the missing symptom, expected and actual behavior, reproduction steps, and extension-terminal output. This is ready for work only when a specific failure is identified and reproducible evidence, including logs if relevant, defines what done means.

Written by the indexing model from the issue text.

Description

Issue-Bug Needs: Triage
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

$PSversionTable: $Host Please include $Host so we know this version is from the Extension Terminal!

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.6.6
PSEdition                      Core
GitCommitId                    7.6.6
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0.}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Visual Studio Code Version
1.137.0
x64
Extension Version
ms-vscode.powershell@2025.4.0
Steps to Reproduce

ms-vscode.powershell@2025.4.0

Visuals

No response

Logs

No response

Dominant language
TypeScript
Stars
1.9k
Forks
548
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/vscode-powershell

All issues in PowerShell/vscode-powershell

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.