How to uninstall VSCodium on Windows

Removing VSCodium and resetting its data are separate decisions. Settings and extensions live outside the install folder, and neither goes away when you uninstall the app. Back them up first if you might reinstall. This guide covers VSCodium installed per-user from the VSCodium.VSCodium winget package, and keeps your project folders and their own .vscode configuration untouched.

Quit VSCodium first

Save your files and close every VSCodium window. Check Task Manager (Ctrl+Shift+Esc) for any VSCodium.exe still listed before you uninstall.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find VSCodium, and choose Uninstall, or run:

winget uninstall --id VSCodium.VSCodium

Back up before you remove data

Copy %APPDATA%\VSCodium to keep settings, keybindings and snippets, and %USERPROFILE%\.vscode-oss to keep extensions, before you clear either one.

Where the data lives

Location	What it holds	What to do
`%APPDATA%\VSCodium`	Settings, keybindings, snippets	Back this up; the uninstaller does not remove it
`%APPDATA%\VSCodium\Cache`, `Code Cache`, `GPUCache` and `logs`	Editor caches and logs	Safe to remove after quitting
`%USERPROFILE%\.vscode-oss`	Extensions	Back up if you want to reinstall them the same way
`%USERPROFILE%\.vscode-oss-shared`	Shared user data	Same decision as `.vscode-oss`

VSCodium and VS Code do not share settings or extensions. %USERPROFILE%\.vscode and %APPDATA%\Code belong to Visual Studio Code, not this app, and are not part of this table.

Check the result

Run these read-only commands after the uninstall finishes:

Get-Process VSCodium -ErrorAction SilentlyContinue
winget list --id VSCodium.VSCodium
Test-Path "$env:LOCALAPPDATA\Programs\VSCodium"
Test-Path "$env:APPDATA\VSCodium"
Test-Path "$env:USERPROFILE\.vscode-oss"

No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means a window or helper is still open.
A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
The first Test-Path returning False means the program folder is gone; True means files remain there.
Test-Path "$env:APPDATA\VSCodium" returning True means your settings and caches are still there, which is expected unless you removed them yourself.
Test-Path "$env:USERPROFILE\.vscode-oss" returning True means your extensions folder is still there; remove it yourself once you have backed it up, if you want a clean start.

If you installed it with winget

winget uninstall runs the same uninstaller Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\VSCodium, .vscode-oss or .vscode-oss-shared on its own.

What Mole lists

For VSCodium installed per-user from winget:

The program folder and the Start Menu shortcut are selected by default.
%APPDATA%\VSCodium\Cache, Code Cache, GPUCache and logs are selected by default.
%APPDATA%\VSCodium itself is listed but not selected.
If a vscodium:// link registration still points at the removed program, Mole lists it and backs it up to a .reg file first.
Mole also lists a file-type association key for each extension VSCodium can open (.py, .js, .md, and similar); in this test almost none of them had actually been written to the registry, since VSCodium only registers a file type the first time you set it as the default opener for that extension.

Projects on disk and their own .vscode folders are not part of this list. The rule added on September 29 lists %USERPROFILE%\.vscode-oss and %USERPROFILE%\.vscode-oss-shared for review without selecting them. Their removal has not been retested on the VM; check the review in the version you use.

What this test covered

Tested with VSCodium 1.126.04524 installed through winget, per-user scope, on an ARM64 test VM. The test installed it from an elevated session, so its uninstaller asked for administrator access; a normal per-user install does not.