VSCodium
Overview
Version & Lifecycle
Community Notes
VSCodium close-before-update note
For managed VSCodium deployments, use the official Windows installers from the VSCodium GitHub releases or the project install page, and close VSCodium before updates. VSCodium EXE x64, MSI x64, and User x64 packages can return Exit Code 1 when the editor is open during an update, so Intune, ConfigMgr, RMM, or PSADT deployments should include VSCodium-specific conflicting-process handling before retrying.
For unattended setup with the Windows EXE installer, use Inno Setup-style silent options such as VSCodiumSetup-x64-x.y.z.exe /VERYSILENT /NORESTART /LOG="%WINDIR%\Temp\VSCodium-Install.log". If you customize tasks or install location, validate those switches against the exact VSCodium installer build you are packaging.
For managed VSCodium Windows updates, close VSCodium before launching the installer. The EXE x64 package is a close-before-update case; use a pre-close or user-deferral step, then verify the installed version after setup completes. Source: official VSCodium source.
Close VSCodium before running managed MSI or user-scope updates. If VSCodium.exe is open, updates can return Exit Code 1; add VSCodium to the deployment’s conflicting-process list so the next detection pass sees the updated files.
Source: VSCodium official source.
Release Notes & Updates
Help us match vulnerabilities
No vulnerability match yet. Pick the right product:
Don’t see it? Paste a CPE
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
Packaging Notes
Community-driven build scripts available; builds binaries from Microsoft vscode source with telemetry disabled
