microsoft
"A setting has changed that requires a restart to take effect." needs more info
Type: Bug
There are no steps to reproduce. I'm facing an issue when I get dialog on image below everytime I open vscode, the message lacks reasoning, trace logs show nothing, there is no possible way of getting rid of it unless I know why it's happening.
Quick googling shows that there are others who are pulling out their hair because of no info provided.
VS Code version: Code 1.90.1 (611f9bfce64f25108829dd295f54a6894e87339d, 2024-06-11T21:01:24.262Z) OS version: Windows_NT x64 10.0.22631 Modes: Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 9 7900X 12-Core Processor (24 x 4691) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 63.22GB (49.53GB free) |
| Process Argv | --crash-reporter-id e4aa2530-b0be-4069-8355-e5851d07ffa0 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Debian |
| OS | Linux x64 5.15.133.1-microsoft-standard-WSL2 |
| CPUs | AMD Ryzen 9 7900X 12-Core Processor (24 x 0) |
| Memory (System) | 30.96GB (28.68GB free) |
| VM | 0% |
Extensions (15)
| Extension | Author (truncated) | Version |
|---|---|---|
| java | red | 1.31.0 |
| selectline-statusbar | tom | 0.0.2 |
| intellicode-api-usage-examples | Vis | 0.2.8 |
| vscodeintellicode | Vis | 1.3.1 |
| vscode-java-debug | vsc | 0.57.0 |
| vscode-java-dependency | vsc | 0.23.6 |
| vscode-java-pack | vsc | 0.27.0 |
| vscode-java-test | vsc | 0.41.1 |
| vscode-maven | vsc | 0.44.0 |
| workspace-storage-cleanup | meh | 1.1.5 |
| remote-ssh | ms- | 0.112.0 |
| remote-ssh-edit | ms- | 0.86.0 |
| remote-wsl | ms- | 0.88.2 |
| remote-explorer | ms- | 0.4.3 |
| tom | 1.2.2 |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelt:31048053
dsvsc021:30996838
945dj816:31013170
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
pythonprt:31056678
dwnewjupyter:31046869
newcmakeconfigv2:31071590
I was just experiencing this issue and isolated my problem to the WSL extension in VSCode. I was able to resolve my issue by running wsl --shutdown from powershell.
This would have been 1000x easier to debug if this error message included some helpful information about which extension is causing the issue and/or which setting was being changed.
