VSCodium/vscodium
1
0
Fork 0
mirror of https://github.com/VSCodium/vscodium.git synced 2026-02-04 03:51:16 -06:00
Code Issues 135 Packages Projects Releases 10 Wiki Activity

VScodium cannot properly transfer settings in zip version new installtion #672

New Issue
Closed
opened 2025-09-10 23:46:42 -05:00 by giteasync · 3 comments
giteasync commented 2025-09-10 23:46:42 -05:00
Owner
Copy Link

Originally created by @dpapis on GitHub.

Type: Bug

Greetings all
i am using VSCode teaching Python in school.
I am using the vscode zip version as it offers me great portability of code.
in a recent update version,specifically from 17.4.0 to 17.4.1 (17.4.1 is the current version i am using right now) i noticed the following issue:
First ,
i copied the data folder from the old installation folder (17.4.0) to the new installation folder (17.4.1)) than holds the new extracted version of newest vs code version
Second,
if i remove to recycle bin the old zip folder than contains the 17.4.0 version,the 17.4.1 version does not transfer the settings and extensions to new installation(notice that the old copied data folder exists in the new installation already).
if i keep the old intallation folder the vscode exe files loads correct all the installed extensions correctly-no new installation and configuration required...
Any suggestions how to resolve this?
as i mentiond before the above procedure that i have desribed is the propper procedure to transfer an old installation of vs code zip version to a new one, is the official that i use a long time now from the vs code site:
https://code.visualstudio.com/docs/setup/windows

win x64 windows 10 Pro and x64 zip of VS Code all used version utlil now.
Thansk in advaced

VSCodium version: VSCodium 1.74.0 (cb188d662af4ff5d43505b572b49905a1f0153ad, 2022-12-08T20:06:19.200Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info
Item Value
CPUs Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz (8 x 3600)
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
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 7.87GB (1.91GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (14)
Extension Author (truncated) Version
vscode-sqlite ale 0.14.1
prettier-vscode esb 9.10.3
code-runner for 0.11.8
vscode-language-babel mgm 0.0.35
git-graph mhu 1.30.0
python ms- 2022.20.1
jupyter ms- 2022.10.110
jupyter-keymap ms- 1.0.0
jupyter-renderers ms- 1.0.12
sqltools mtx 0.26.0
vscode-graphql Pri 0.3.7
vscode-thunder-client ran 2.2.0
open-in-browser tec 2.0.0
five-server yan 0.1.11
Originally created by @dpapis on GitHub. Type: <b>Bug</b> Greetings all i am using VSCode teaching Python in school. I am using the vscode zip version as it offers me great portability of code. in a recent update version,specifically from 17.4.0 to 17.4.1 (17.4.1 is the current version i am using right now) i noticed the following issue: First , i copied the data folder from the old installation folder (17.4.0) to the new installation folder (17.4.1)) than holds the new extracted version of newest vs code version Second, if i remove to recycle bin the old zip folder than contains the 17.4.0 version,the 17.4.1 version does not transfer the settings and extensions to new installation(notice that the old copied data folder exists in the new installation already). if i keep the old intallation folder the vscode exe files loads correct all the installed extensions correctly-no new installation and configuration required... Any suggestions how to resolve this? as i mentiond before the above procedure that i have desribed is the propper procedure to transfer an old installation of vs code zip version to a new one, is the official that i use a long time now from the vs code site: https://code.visualstudio.com/docs/setup/windows win x64 windows 10 Pro and x64 zip of VS Code all used version utlil now. Thansk in advaced VSCodium version: VSCodium 1.74.0 (cb188d662af4ff5d43505b572b49905a1f0153ad, 2022-12-08T20:06:19.200Z) OS version: Windows_NT x64 10.0.19045 Modes: Sandboxed: No <details> <summary>System Info</summary> |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz (8 x 3600)| |GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off| |Load (avg)|undefined| |Memory (System)|7.87GB (1.91GB free)| |Process Argv|| |Screen Reader|no| |VM|0%| </details><details><summary>Extensions (14)</summary> Extension|Author (truncated)|Version ---|---|--- vscode-sqlite|ale|0.14.1 prettier-vscode|esb|9.10.3 code-runner|for|0.11.8 vscode-language-babel|mgm|0.0.35 git-graph|mhu|1.30.0 python|ms-|2022.20.1 jupyter|ms-|2022.10.110 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.12 sqltools|mtx|0.26.0 vscode-graphql|Pri|0.3.7 vscode-thunder-client|ran|2.2.0 open-in-browser|tec|2.0.0 five-server|yan|0.1.11 </details> <!-- generated by issue reporter -->
giteasync added the
stale
 label 2025-09-10 23:46:42 -05:00
giteasync commented 2025-09-10 23:46:43 -05:00
Author
Owner
Copy Link

@Crystal-RainSlide commented on GitHub:

I got the same bug, but:

Update: It's fixed in 1.75.0.

@Crystal-RainSlide commented on GitHub: I got the same bug, but: - Same report at VSCode's repo: https://github.com/microsoft/vscode/issues/169462 - Seems to be fixed at: https://github.com/microsoft/vscode/issues/169006#issuecomment-1362892184 - Let's wait for VSCode 1.75.0 and see. Update: It's fixed in 1.75.0.
giteasync commented 2025-09-10 23:46:43 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub:

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.

@github-actions[bot] commented on GitHub: This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.
giteasync commented 2025-09-10 23:46:43 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub:

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

@github-actions[bot] commented on GitHub: This issue has been automatically marked as stale. **If this issue is still affecting you, please leave any comment**, and we'll keep it open. If you have any new additional information, please include it with your comment!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
discussion
documentation
downstream
duplicate
enhancement
extension
good first issue
help wanted
invalid
never-stale
pull-request
Mirrored from GitHub Pull Request
question
stale
telemetry
upstream
wontfix
No Label
stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium#672
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?