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)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- powershell, vscode
- Área
- networking
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- 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. - Log in with an account in the local Administrators group, using key auth.
- From another Windows 10 machine, connect using VS Code (Insiders) Remote-SSH.
- 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
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 8.3k
- Forks
- 821
- Merge medio
- 12 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de PowerShell/Win32-OpenSSH
-
Area-ssh-agent Issue-Upstream Parity
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
PowerShell/Win32-OpenSSH#2458 · 1 reacción ·
-
0 - Backlog Area-sshd Area-Terminal Investigate Issue-Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
PowerShell/Win32-OpenSSH#2468 · 4 comentarios · 1 reacción ·
-
Area-Authentication Area-Logging/Diagnostics Area-sshd Investigate Issue-Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
PowerShell/Win32-OpenSSH#2466 · 1 comentario · 1 reacción ·
-
Area-ssh-agent Issue-Enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
PowerShell/Win32-OpenSSH#2462 · 1 comentario · 1 reacción ·
-
Area-ssh-agent Investigate
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
PowerShell/Win32-OpenSSH#2460 · 1 reacción ·
Todos los issues de PowerShell/Win32-OpenSSH
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
amnezia-vpn/amnezia-client#3297 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
`dns_resp_find` never checks the answer CLASS, so a non-IN record is returned as if it were INAbiertobug lompi sev-3
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Feature Feature Parity
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
valkey-io/valkey-glide-ruby#369 ·
Los mantenedores suelen responder en 2 días