VS Code Not Opening or Keeps Crashing: How to Fix It

If VS Code is not opening, shows a blank window, or crashes at launch, test GPU rendering, extensions, and user data separately. These checks isolate the failure without deleting your settings.

This guide proceeds from the simplest and safest fixes to more involved ones. Test after each step.

The blank-window and unsupported-installation checks are documented in the official VS Code FAQ.

Fix a blank or white window

A blank window can be caused by GPU hardware acceleration in the Chromium engine that VS Code uses for its UI.

Save work in any responsive VS Code window first. Then quit VS Code normally; if it is stuck, use the operating system's process manager to end only processes identified as VS Code.

Then start VS Code with GPU acceleration disabled:

bash

code --disable-gpu

If VS Code opens normally with this flag, update the graphics driver through the operating system or hardware vendor and test normal startup again. Keep the flag as a diagnostic until you reproduce the difference.

Test with a fresh GPU cache

A damaged GPU cache after an update can cause launch crashes and blank windows. Close VS Code and rename the GPUCache folder to GPUCache.backup:

• Windows: %APPDATA%\Code\GPUCache
• macOS: ~/Library/Application Support/Code/GPUCache
• Linux: ~/.config/Code/GPUCache

Restart VS Code normally. It creates a fresh cache; if the symptom remains, close VS Code and restore the backup.

Start without extensions

A crashing extension can prevent VS Code from launching. Start VS Code with extensions disabled by passing the --disable-extensions flag:

bash

code --disable-extensions

If VS Code launches successfully, an extension is causing the crash. To find it, run Help: Start Extension Bisect from the Command Palette after VS Code opens. See manage extensions for more details. The bisect tool disables extensions in groups and asks if the crash still occurs on reload, narrowing down to the single responsible extension.

Once found, uninstall or disable the extension. Check its Marketplace page for an update or report the issue to the extension author.

Check for anti-virus interference on Windows

On Windows, anti-virus software sometimes quarantines or blocks VS Code components. If you see [Unsupported] in the title bar after VS Code manages to open, or if a native crash occurs on launch, anti-virus software has likely modified VS Code files.

Check antivirus quarantine or history for VS Code files that were removed or blocked. Restore the file only when you recognize the official installation, then reinstall VS Code to repair missing application files. Avoid excluding the entire installation folder unless the antivirus vendor specifically confirms a false positive.

Also check that compatibility mode is not enabled. Right-click the VS Code executable or shortcut, choose Properties, open the Compatibility tab, and make sure Run this program in compatibility mode for is unchecked.

Fix corrupted settings

A malformed settings file can crash VS Code on startup. To test this, temporarily move your settings file to a backup location. The settings file is at:

• Windows: %APPDATA%\Code\User\settings.json
• macOS: ~/Library/Application Support/Code/User/settings.json
• Linux: ~/.config/Code/User/settings.json

Rename it to add a .backup extension, then start VS Code. If it opens, your settings file had a syntax error or a problematic value. You can restore your settings from the backup file, checking the JSON structure carefully, or start fresh and re-add your preferences.

Run VS Code in verbose mode

For more diagnostic information, start VS Code in verbose mode:

bash

code --verbose

This prints detailed startup information to the terminal. Look for error messages, missing files, or processes that fail to start. You can also open Help > Toggle Developer Tools after VS Code opens, then check the Console tab for JavaScript errors.

Test separate user data

Use a separate user-data directory with an empty temporary folder and disable extensions. VS Code creates an isolated environment and does not modify your normal settings or extensions.

• Windows PowerShell: code --user-data-dir "$env:TEMP\vscode-clean-test" --disable-extensions
• macOS or Linux: code --user-data-dir /tmp/vscode-clean-test --disable-extensions

If the isolated window opens, the normal user data or an extension is involved. If it still crashes, the installation, GPU, or operating system remains in scope. Close the test window when finished; the temporary folder can be removed later after confirming it contains no data you need.

Reinstall VS Code

Reinstalling VS Code normally does not delete settings, keybindings, snippets, or extensions because they live outside the application installation. Back up important settings or export your profile first in case you later decide to perform a clean uninstall.

Download the latest version from the VS Code download page. On macOS, drag the old application to the Trash first, then install the new one. On Windows, the installer replaces the existing installation automatically. On Linux, use your package manager to reinstall.

For the normal platform-specific update path before reinstalling, see /vscode/how-to-update-vs-code-on-windows-macos-and-linux.

If you still experience crashes after reinstalling, the problem may be at the operating system level. Check for pending OS updates, disk errors, or memory problems using your system's built-in diagnostic tools.