Introduction

VS Code stuck on activating extensions usually means one extension never finishes activation, the extension host is overloaded, or the current workspace triggers expensive startup logic.

Symptoms

  • The status bar shows activating extensions for a long time
  • Features such as IntelliSense or debug never become ready
  • The issue is worse in remote SSH, containers, or large monorepos

Common Causes

  • One extension crashes or loops during activation
  • Cached extension data became stale after an update
  • The workspace triggers too much file scanning on startup

Step-by-Step Fix

  1. 1.Start VS Code with extensions disabled to confirm the extension host is the problem.
  2. 2.Re-enable extensions in small batches to find the slow activator.
  3. 3.Clear extension caches and restart VS Code.
  4. 4.Reduce workspace scanning for node_modules, build output, and generated files.

Prevention

  • Keep heavyweight extensions to the workspaces that actually need them
  • Exclude generated folders from file watching and search
  • Review extension startup behavior after major VS Code updates