PowerShell Extension Issue

[navina19300]

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

Couldn't able to integrate PowerShell with VS Code, for Shell Code Prompt.

PowerShell Version

Host name: DESKTOP-KI2D5UJ

Visual Studio Code Version

Version: 1.96.2 (user setup)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.17763

Extension Version

Identifier
ms-vscode.powershell
Version
2024.4.0
Last Updated
2025-01-13, 16:13:19
Size
303.1 MB
Cache
3.2 KB

Steps to Reproduce

1. Installed PowerShell Extension in VS Code
2. Ctrl + Shift + P Command is not working
3. In Command Palette the prompt Terminal : Select Default Shell is not listed for the further progress.

Visuals

1. Installed PowerShell Extension in VS Code
2. Ctrl + Shift + P Command is not working
3. In Command Palette the prompt Terminal : Select Default Shell is not listed for the further progress.

Logs

1. Installed PowerShell Extension in VS Code
2. Ctrl + Shift + P Command is not working
3. In Command Palette the prompt Terminal : Select Default Shell is not listed for the further progress.

[andyleejordan]

Hi, this sounds like you're having trouble using VS Code, as the commands you're running are VS Code commands (not our extension's) and the error message is about your VS Code settings. Can you seek support from VS Code? Thanks!

[github-actions]

This issue has been labeled as resolved, please verify the provided fix (or other reason).

[github-actions]

This issue has been labeled as resolved, please verify the provided fix (or other reason).