VSCode seems it does not respect my profiles when starting some extensions

Open
#320,389 0 comments 0 reactions 1 assignee View on GitHub

@sandy081 is already working on this.

Since Jun 8, 2026.

Assessment

This issue has not been assessed yet.

Description

bug user-profiles

Type: Bug

Hello there,

I recently posted a similar issue for new Agents window. In that task I explained that I disabled many features in the "Default" profile, including all AI, and the profile I am starting agent window is fully decorated for AI works. Yet, agents window tries to use "Default" profile to connect agents, and fails miserably to do so becuause of changes I made to "Default" profile.

The same is now happenning with Remote Explorer.

I also removed Remote Explorer from "Default" profile. And now I am not able to connect WSL containers, and vscode complains saying "Extension 'WSL' is required. And it says this after I started this connection from within Remote Explorer, just from another profile set for this purpose.

How can you recreate the issue? follow these steps:
1- Open "Default" profile and remove WSL, and maybe Remote Explorer(?!)
2- Create a new profile, from scratch or using default
3- switch to new profile, find and install WSL
4- open Remote explorer window and try to connect a WSL container (current or new windows, wont matter)
5- Now witness: VSCode switches to "Default" profile immediately before trying to connect, and it fails because there is no WSL in "Default" profile.
6- Bonus: open File menu, and then "Close Remote Connection". The profile stays in "Default".

One exception I saw so far is this:
If I enable WSL in "Default" profile, open a remote folder, and switch to another profile that has WSL enabled within that folder, then next time I try to connect from non-Default profile, it reopens the folder in that profile without a problem.

Everything I use in VSCode should be contained within the profile I am working in. The exception clearly shows that my profiles are respected in the workspace level, but not in global level.

I hope you fix this issue and bring balance and peace to the use of profiles.

VS Code version: Code 1.123.0 (6a44c352bd24569c417e530095901b649960f9f8, 2026-06-03T11:29:03+02:00)
OS version: Windows_NT x64 10.0.26100
Modes:
Connection to 'WSL: AgenticTraining' could not be established No remote extension installed to resolve wsl.

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2195)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x8086, DEVICE=0x0d26 [Intel(R) Iris(TM) Pro Graphics 5200], DRIVER_VENDOR=Intel, DRIVER_VERSION=20.19.15.4531 ACTIVE
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.8521
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
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.91GB (2.07GB free)
Process Argv --crash-reporter-id 1e1cd08e-d950-4c1a-a30a-00ed7b58646a
Screen Reader no
VM 0%

Connection to 'WSL: AgenticTraining' could not be established No remote extension installed to resolve wsl.

Extensions (1)
Name Identifier Author Version
Extensions not loaded extensions-load-error N/A
A/B Experiments 
vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
b6b4d950:31327385
6abeh943:31336334
envsdeactivate2:31505458
cloudbuttont:31379625
3efgi100_wstrepl:31403338
839jf696:31457053
ec5jj548:31422691
cp_cls_t_966_ss:31526232
inlinechat_v2_hd992725:31505030
4je02754:31466945
c3h7c220:31478652
38bie571_auto:31426784
cp_cls_t_1081:31454832
conptydll_true:31498968
e9c30283:31461165
test_treatment2:31471001
46204921:31447328
idci7584:31464702
e3e4d672:31494082
ei9d7968:31496641
chat:31457767
7e187181:31503455
ghj88844:31499326
ec1eg703:31520046
ddid_c:31478207
hmra_i5g22:31518061
getcmakediagnosticsoff:31489825
7df3h592:31512476
cp_cls_t_1082:31516087
logging_enabled_new:31498466
j0d79568:31499440
jb_cp_cls_c_632:31524806
748c7209:31512887
32d76977:31512328
ha629193:31508444
cdk-lw-on:31524445
31fi7170_t:31522396
jh5f2457_c:31515489
61138546:31518536
gf14b233:31526830
Dominant language
TypeScript
Stars
193k
Forks
42.9k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.