Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Visible elevated cmd.exe window appears on server desktop when connecting via VS Code Remote-SSH (v9.5.0.0p1-Beta and v10.0.0.0p2-Preview; not in v7.9.0.0p1-Beta)

Aperta
  • Qualcosa non va?
#2,465 1 commento 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
powershell, vscode
Ambito
networking

Direzione di ricerca

Reproduce the issue with the listed VS Code Remote-SSH steps, comparing affected and unaffected sshd versions and the plain ssh user@host case. Review install-sshd.ps1 and the displayed code-server-insiders.cmd launch command while checking how the server process is presented. Done means VS Code stays connected without a visible server-side cmd.exe window.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Area-sshd Area-Terminal Investigate Issue-Regression
Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce
Steps to reproduce
  1. Install Win32-OpenSSH v10.0.0.0p2-Preview (or v9.5.0.0p1-Beta) on a Windows 10 server via the release zip and install-sshd.ps1.
  2. Log in with an account in the local Administrators group, using key auth.
  3. From another Windows 10 machine, connect using VS Code (Insiders) Remote-SSH.
  4. Look at the server's desktop.
Expected behavior

No console window appears on the server's desktop.

Actual behavior

A window titled "Administrator: c:\windows\system32\cmd.exe" appears, empty except for a cursor. If I close it, VS Code loses its connection, so the window is hosting the VS Code server (code-server-insiders.cmd).

Connecting with plain ssh user@host from a terminal does not cause this; it only happens with VS Code Remote-SSH.

Versions tested (same client, same server, same config)
sshd version Window appears
v10.0.0.0p2-Preview Yes
v9.5.0.0p1-Beta Yes
v7.9.0.0p1-Beta No

Another Windows server running an older sshd, connected from the same client, also shows no window.

Environment
  • Server: Windows 10 22H2, build 19045.6456
  • Client: Windows 10 22H2, build 19045.3803, OpenSSH_for_Windows_8.1p1
  • VS Code: Insiders <1.140.0-insider (system setup)> Commit: 4a6a3612a562c50f54c2bd5211f0ea42915b974e
  • Remote - SSH extension
Expected behavior
No console window appears on the server's desktop when a client connects with VS Code Remote-SSH (this is what happens with v7.9.0.0p1-Beta).
Actual behavior
With v10.0.0.0p2-Preview and v9.5.0.0p1-Beta, a window titled "Administrator: c:\windows\system32\cmd.exe" appears on the server's desktop each time VS Code connects. It is empty except for a cursor. Closing it kills the VS Code server and the client reports it cannot connect, so the window is hosting code-server-insiders.cmd.

Plain `ssh user@host` from a terminal does not trigger the window. Only VS Code Remote-SSH does.

Tested with the same client, same server, same config:
- v10.0.0.0p2-Preview: window appears
- v9.5.0.0p1-Beta: window appears
- v7.9.0.0p1-Beta: no window

Another Windows server running an older sshd shows no window with the same client.
Error details
No error message. The behavior is the unexpected visible window. Process seen while connected:

cmd /Q /C C:\Users\<user>\.vscode-server-insiders\cli\servers\Insiders-<hash>\server\bin\code-server-insiders.cmd --connection-token=remotessh --start-server --enable-remote-auto-shutdown ...
Environment data
Server: Windows 10 22H2, build 19045.6456
Client: Windows 10 22H2, build 19045.3803
Client ssh: OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
Server sshd (affected): v10.0.0.0p2-Preview, v9.5.0.0p1-Beta
Server sshd (not affected): v7.9.0.0p1-Beta
Install method: release zip + install-sshd.ps1
Login account: member of local Administrators group, key auth
VS Code: Insiders <1.140.0-insider (system setup)>  Commit: 4a6a3612a562c50f54c2bd5211f0ea42915b974e
Remote - SSH extension <Insiders-4a6a3612a562c50f54c2bd5211f0ea42915b974e>
Version

v7.9.0.0

Visuals

No response

Lingua principale
Nessun dato sulla lingua
Stelle
8.3k
Fork
820
Merge medio
12m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PowerShell/Win32-OpenSSH

Tutte le issue di PowerShell/Win32-OpenSSH

Issue simili

Altre issue su Networking

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.