PowerShell / PowerShell/vscode-powershell
powershell didnt start
Open
Nobody has claimed this yet.
Issue-Bug
Needs: Triage
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
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
omniroute complained after just installing the powershell it now did not start when needed
PowerShell Version
newest win 10 vs code omniroute
Visual Studio Code Version
1.136.0
x64
Extension Version
ms-vscode.powershell@2025.4.0
Steps to Reproduce
vscode omniroute work on telegram bot
Visuals
No response
Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/troubleshooting.md and compare the reported setup: Windows 10, VS Code 1.136.0, and PowerShell extension 2025.4.0. Reproduce the failure using the described VS Code and Telegram bot workflow, then collect the missing logs and a precise error message. Done means the startup failure has an actionable reproduction or is shown not to be caused by the extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100