PowerShell / PowerShell/vscode-powershell
Version 7.5 causes terminal window crash
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Type: Performance Issue
When I start VC, with PowerShell 7.5 installed, I get error messages about the terminal window and files not found. Consequently, powershell would not run.
I had to uninstall 7.5 and reinstall 7.4; now it works fine.
Extension version: 2025.0.0
VS Code version: Code 1.97.2 (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | 12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 31.68GB (11.89GB free) |
| Process Argv | --crash-reporter-id 089029d2-1858-4dbd-8427-39f020d3cff9 |
| Screen Reader | no |
| VM | 0% |
Process Info
CPU % Mem MB PID Process
0 140 13404 code main
0 119 7412 ptyHost
0 321 3192 "C:\Program Files\PowerShell\7\pwsh.exe" -NoProfile -ExecutionPolicy Bypass -Command "Import-Module 'c:\Users\ISRC1\.vscode\extensions\ms-vscode.powershell-2025.0.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2025.0.0' -BundledModulesPath 'c:\Users\ISRC1\.vscode\extensions\ms-vscode.powershell-2025.0.0\modules' -EnableConsoleRepl -StartupBanner \"PowerShell Extension v2025.0.0
Copyright (c) Microsoft Corporation.
https://aka.ms/vscode-powershell
Type 'help' to get help.
\" -LogLevel 'Warning' -LogPath 'c:\Users\ISRC1\AppData\Roaming\Code\logs\20250214T093146\window1\exthost\ms-vscode.powershell' -SessionDetailsPath 'c:\Users\ISRC1\AppData\Roaming\Code\User\globalStorage\ms-vscode.powershell\sessions\PSES-VSCode-13404-932210.json' -FeatureFlags @() "
1 392 1708 "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -Version 5.1 -s -NoLogo -NoProfile
0 15 12104 C:\WINDOWS\system32\conhost.exe 0x4
0 14 8036 conpty-agent
0 110 19476 "C:\Program Files\PowerShell\7\pwsh.exe" -noexit -command "try { . \"c:\Users\ISRC1\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1\" } catch {}"
0 14 26664 conpty-agent
0 56 17648 utility-network-service
0 182 18452 extensionHost [1]
0 106 15112 "C:\Users\ISRC1\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\ISRC1\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=18452
0 130 18624 shared-process
0 41 21928 crashpad-handler
0 259 22844 window [1] (Add to Sharepoint-group.ps1 - Visual Studio Code)
0 101 23960 fileWatcher [1]
0 216 26920 gpu-process
Workspace Info
;
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
py29gd2263:31024239
14376t-chatv2:31237133
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputscf:31238124
5a9hg449:31230677
9064b325:31222308
copilot_t_ci:31222730
cp15172_c:31236637
jda6j935:31233686
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
Reproduce the failure with PowerShell 7.5 and extension version 2025.0.0, comparing it with PowerShell 7.4. Start from the terminal and PowerShell Editor Services startup processes shown in the report, and use the reported terminal errors and missing files to determine the affected component; done means the terminal and PowerShell run normally on 7.5.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100