latest issue

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

i am expericening the powershell issu

PowerShell Version

Name                           Value                                                                                   
----                           -----                                                                                   
PSVersion                      5.1.26100.8894                                                                          
PSEdition                      Desktop                                                                                 
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                 
BuildVersion                   10.0.26100.8894                                                                         
CLRVersion                     4.0.30319.42000                                                                         
WSManStackVersion              3.0                                                                                     
PSRemotingProtocolVersion      2.3                                                                                     
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.129.1
x64

Extension Version

ms-vscode.powershell@2025.4.0

Steps to Reproduce

start the application

Visuals

No response

Logs

No response

The report names no source file, failing test, specific symptom, or useful log. Start by reproducing the issue in Visual Studio Code 1.129.1 with PowerShell extension 2025.4.0 and PowerShell 5.1, then capture the exact behavior and logs; done requires a reproducible failure with clear expected and actual results.