The Error
You open VS Code and a yellow warning bar appears at the top:
Your Code installation appears to be corrupt. Please reinstall.
VS Code still works, but the warning sticks around on every launch. On some versions it blocks features outright, or keeps nagging you at startup until you deal with it.
Root Cause
VS Code has a built-in integrity checker. At startup, it computes checksums of its core files and compares them against a product.json manifest. One byte off anywhere โ and the warning fires.
The most common triggers:
- Extensions that patch VS Code internals โ notably custom title bar or theme extensions that inject CSS into VS Code's own HTML/JS files.
- Manual edits to VS Code's application files (e.g., editing
workbench.htmlto remove the "unsupported" warning โ a common workaround that itself causes this warning). - Antivirus or security software that modifies or quarantines files inside the VS Code installation directory.
- Incomplete update โ an auto-update that was interrupted mid-write.
- File system corruption โ rare, but possible on unstable systems.
Fix 1: Disable the Integrity Check (Quickest Fix)
Caused by an extension or an intentional edit? You can silence the warning without reinstalling.
Install the Fix VSCode Checksums extension:
- Open the Extensions panel (
Ctrl+Shift+X/Cmd+Shift+X). - Search for Fix VSCode Checksums (by lehni).
- Install it, then open the Command Palette (
Ctrl+Shift+P) and run:Fix Checksums: Apply - Restart VS Code when prompted.
The extension recomputes checksums from your current files and patches the manifest. VS Code's checker runs again, finds a match, and the warning disappears.
Fix 2: Reinstall VS Code (Clean, Recommended)
Fix 1 didn't help, or you're dealing with a botched update? A clean reinstall is the reliable path. Good news: settings, extensions, and keybindings live in a separate folder โ they survive a reinstall untouched.
Windows
- Uninstall VS Code via Settings โ Apps.
- Delete leftover directories if they exist:
%LOCALAPPDATA%\Programs\Microsoft VS Code %APPDATA%\Code โ DO NOT delete this โ contains your settings
- Download the latest installer from [code.visualstudio.com](https://code.visualstudio.com) and install.
### macOS
- Drag VS Code from `/Applications` to Trash.
- Download the `.zip` from the VS Code site, extract it, and drop it back into `/Applications`.
- Your settings in `~/Library/Application Support/Code` stay untouched.
### Linux (apt)
sudo apt remove code sudo apt install code
Or for Snap:
sudo snap remove code sudo snap install code --classic
## Fix 3: Repair Without Reinstalling (Windows Only)
Windows users have a shortcut. VS Code's installer includes a repair mode that re-copies modified or missing files without wiping everything:
- Go to **Settings โ Apps โ Visual Studio Code โ Modify**.
- Select **Repair** in the installer wizard.
- Done โ no full reinstall needed.
## Fix 4: Check for Antivirus Interference
The error comes back after a fresh install? Your AV is almost certainly the culprit. Add VS Code's installation directory to its exclusion list:
- **Windows**: `%LOCALAPPDATA%\Programs\Microsoft VS Code`
- **macOS**: `/Applications/Visual Studio Code.app`
- **Linux**: `/usr/share/code` or wherever your distro installs it
## Verify the Fix
Restart VS Code fully โ close all windows, not just the current one. If the yellow bar is gone at next launch, you're done.
Want to be thorough? Check the startup log:
Help โ Toggle Developer Tools โ Console
Search for `checksum` or `corrupt`. A clean installation logs nothing about either.
## Prevention
Three habits that keep this warning from coming back:
- **Be careful with extensions that write to VS Code internals.** Extensions like Custom CSS and JS Loader inject directly into VS Code's app files โ they will always trigger the integrity check. Worth it for some setups, but know the trade-off going in.
- **Let updates finish.** Don't force-quit VS Code while it's updating in the background. An interrupted write is a reliable way to land in corrupt-install territory.
- **Verify your installer before running it.** Slow or flaky connection? A partial download can produce a quietly broken install. Compare the SHA-256 hash of your `.exe` or `.dmg` against the hash on the VS Code releases page. The [Hash Generator at ToolCraft](https://toolcraft.app/en/tools/developer/hash-generator) does this in-browser โ paste the file, pick SHA-256, and compare. Nothing leaves your machine.

