vscode: language pack extension doesn't work after restart
Type: Bug
I’ve been using the Chinese language pack before, but lately it’s not working. When I open a new window, the interface language remains the default English. After I reinstalled and restarted, the interface language changed to Chinese. But after restarting again, it changed back to the original and vscode prompts me to install the language pack again. Throughout the process, it never appeared in the installed extension list. I tried other language packs that were not previously installed and this problem does not occur. The attempt in vscode insider version is also fine.
VS Code version: Code 1.81.0 (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:37:13.485Z) OS version: Windows_NT x64 10.0.22621 Modes:
System Info
Item | Value |
---|---|
CPUs | AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx (8 x 2296) |
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
Load (avg) | undefined |
Memory (System) | 6.94GB (2.07GB free) |
Process Argv | –crash-reporter-id b3cb70f6-3f3a-48e6-9db0-d5bb41631a5b |
Screen Reader | no |
VM | 0% |
Extensions (16)
Extension | Author (truncated) | Version |
---|---|---|
codesnap | adp | 1.3.4 |
vscode-clangd | llv | 0.1.24 |
python | ms- | 2023.14.0 |
vscode-pylance | ms- | 2023.8.10 |
jupyter | ms- | 2023.7.1002162226 |
jupyter-keymap | ms- | 1.1.2 |
jupyter-renderers | ms- | 1.0.17 |
remote-wsl | ms- | 0.81.0 |
cmake-tools | ms- | 1.14.34 |
cpptools | ms- | 1.16.3 |
hexeditor | ms- | 1.9.12 |
material-icon-theme | PKi | 4.29.0 |
sqlite-viewer | qwt | 0.3.13 |
xmake-vscode | tbo | 2.1.5 |
cmake | twx | 0.0.17 |
cloudmusic | YXL | 9.19.1 |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30792226
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
2e4cg342:30602488
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
03d35959:30757346
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
e537b577:30795824
dsvsc013:30795093
dsvsc014:30804076
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 13
- Comments: 20 (6 by maintainers)
using vscode edit ~/.vscode/extensions/extensions.json just delete the language pack element and restart your vscode, then restart with new language pack. At least it works on my mac. as .vscode as a hidden path, you can just cd to the path in terminal and type " code extensions.json" in shell
It seems to be caused by some config files from old versions.
I have a machine installed 1.80 at first and updated to 1.81 does not have this issue. Another machine, which has this issue, is fixed by deleting
%AppData%/Code
and%HOME%/.vscode
and resyncing all settings and extensions.I had two profiles (without(default)/with copilot) and was having this issue. I tried it on the latest Insider build and couldn’t reproduce it. thank you.