`connect ENOENT \\.\pipe\PSES_fskvz4fs.gy4` appears, until VSC has been reinvoked, when a `.PS1` file is invoked in VSC, after cancelling a shutdown that was caused by a PS1 file, which was invoked by VSC.

Open

#5,307 opened on Nov 2, 2025 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: powershell, typescript, vscode
Domain: desktop, devtools

Research direction

Start by reproducing the Windows VS Code sequence in the issue: invoke the .PS1 file, cancel the shutdown, reinvoke it, close VS Code with WM_CLOSE, and reopen it. Inspect the extension's available logs and process or pipe handling around the failure; done means the file can be reinvoked after cancelling shutdown without the connect ENOENT error.

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

As was originally reported at microsoft/vscode/issues/244192:

connect ENOENT \\.\pipe\PSES_fskvz4fs.gy4 appears when a .PS1 file is invoked in VSC, after cancelling a shutdown that was caused by a PS1 file, which was invoked by VSC. The error ceases to appear after VSC has been (closed, then) reinvoked.

PowerShell Version

I did not collect this at the time. However, if relevant to issues/4332, it may contain them.

Extension Version

〃

Logs

〃

Visual Studio Code Version

Version: 1.98.2 (user setup)
Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.26120

Steps to Reproduce

Invoke a .PS1 file containing shutdown /r /fw via VSC's GUI: ^1

#!/usr/bin/env pwsh
#Requires -PSEdition 'Core'
#Requires -Version 7.5.0
If ([OperatingSystem]::IsWindows() -Eq $True) {
	sudo shutdown /r /fw /t 0
}

Cancel when it prompts the user to, because of unkillable processes.
Reinvoke the file. It causes the undermentioned:
WM_CLOSE code. ^3
Invoke code.
Invoke the file again. It'll function.

Dominant language: TypeScript
Stars: 1.9k
Forks: 548
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.

Similar issues

ls -i / --inode not supported ("invalid option -- i"), breaks autoconf's `ls -di .` working-directory check Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

vercel-labs/just-bash#464 · Opened Sep 24, 2026
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

garrytan/gbrain#5421 · Opened Sep 24, 2026
Passer le formulaire de publication en BAL 1.5 par défaut Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

BaseAdresseNationale/adresse.data.gouv.fr#2583 · Opened Sep 24, 2026
🎙️ task - fix(tests-node): the shipped catch ships cause error where error is unknown Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

ehmpathy/declapract-typescript-ehmpathy#632 · Opened Sep 24, 2026
Search modal renders beneath the open AI dock (shared --z-overlay) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

TanStack/tanstack.com#1293 · Opened Sep 24, 2026

More TypeScript issues