microsoft / microsoft/vscode-remote-release
Not able to connect to atlvscode0003 using my NT password
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Bug
VS Code --> ctrl+shift+P --> remotte-ssh: connect to host... --> select Windows --> enter NT passord --> "Permission Denied"
Extension version: 0.122.0
VS Code version: Code 1.116.0 (560a9dba96f961efea7b1612916f89e5d5d4d679, 2026-04-15T00:28:13Z)
OS version: Windows_NT x64 10.0.26100
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics (16 x 3294) |
| GPU Status | 2d_canvas: enabled GPU0: VENDOR= 0x1002, DEVICE=0x1900 [AMD Radeon 780M Graphics], DRIVER_VENDOR=AMD, DRIVER_VERSION=32.0.13040.8004 ACTIVE GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.7309 Machine model name: Machine model version: 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 trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 30.67GB (18.81GB free) |
| Process Argv | --crash-reporter-id 387a5148-2405-45a1-9fd8-073a88e15ad9 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vswsl492cf:30256860
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
6abeh943:31336334
envsdeactivate2:31464701
cloudbuttont:31379625
42190218_ostrepl:31403339
use-responses-api:31390855
je187915:31401254
ec5jj548:31422691
cp_cls_t_966_ss:31454198
a9239246:31499107
4je02754:31466945
c3h7c220:31478652
38bie571_auto:31426784
cp_cls_t_1081:31454832
conptydll_true:31498968
ia-use-proxy-models-svc:31452481
e9c30283:31461165
test_treatment2:31471001
control_6dc23131:31497324
idci7584:31464702
e3e4d672:31494082
ei9d7968:31496641
534a6447:31496642
chat:31457767
8hig5102:31480529
jc933416:31497036
67jbj424:31495046
7e187181:31499614
cpptoolsoff-v2:31475362
i2gc6536:31499202
30450953:31499301
ghj88844:31499326
23c7c724:31491644
client_tst_t:31495907
ddid_c:31478207
getcmakediagnosticson:31489824
ja75b849:31495667
nes-perm-reb-0:31490411
cp_cls_c_1082:31491634
719di409_sum_t:31499345
logging_enabled_new:31498466
db5d2638:31499441
748c7209:31497895
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
Start by reproducing the Ctrl+Shift+P “Remote-SSH: Connect to Host” flow against the reported Windows host and collect the Remote-SSH output or logs around the permission denial. Compare the authentication details with the extension and VS Code versions listed; done means identifying a reproducible cause or documenting the missing diagnostic information needed to proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100