Introduction

An extension can appear installed and enabled while its commands, language features, formatter, debugger, or status-bar items never load. The failure is often scoped to activation conditions: the extension is disabled for the current profile, workspace trust blocks it, a remote window installed it on the wrong side, or cached extension state references an older version. Treat the problem as an activation issue rather than a generic editor problem.

Symptoms

  • The extension is listed as installed, but its commands do not appear in the Command Palette
  • A formatter, debugger, language server, or sidebar view disappears after an extension update
  • The extension works in a local folder but not in WSL, SSH, Dev Containers, or Codespaces
  • Reload Window temporarily restores the extension before it fails again
  • Extension host logs show activation errors, missing dependencies, or rejected workspace trust

Common Causes

  • The extension is installed in the wrong profile or wrong remote authority
  • Workspace Trust prevents activation for a folder opened from an untrusted location
  • Extension global storage contains stale state from a previous version
  • A dependency binary bundled with the extension is blocked by policy or incompatible with the host platform
  • Workspace settings override the extension's language, formatter, or runtime configuration

Step-by-Step Fix

  1. 1.Confirm the extension location and profile
  2. 2.Check whether VS Code is running the extension locally, remotely, or in a different profile before reinstalling it.
powershell
code --list-extensions --show-versions
# In VS Code, open Extensions and check the Profile and Install in Local/Remote indicators
  1. 1.Read the extension activation log
  2. 2.The extension host log usually names the missing executable, rejected activation event, or setting that prevents startup.
powershell
# Command Palette
# Developer: Open Logs Folder
# Review exthost.log and window.log for the extension publisher/name
  1. 1.Test the extension in a clean trusted folder
  2. 2.A clean folder tells you whether the extension itself is broken or the current workspace is blocking activation.
powershell
New-Item -ItemType Directory -Force $env:TEMP\vscode-extension-test | Out-Null
code --profile ExtensionCleanProfile $env:TEMP\vscode-extension-test
# Trust the folder, install only the affected extension, and run its command
  1. 1.Reinstall only the affected extension state
  2. 2.After identifying the extension, remove its package and storage rather than deleting the full VS Code user data directory.
powershell
code --uninstall-extension publisher.extension
code --install-extension publisher.extension
Get-ChildItem $env:APPDATA\Code\User\globalStorage | Where-Object Name -match 'publisher.extension'

Verification

Verify the exact failure path that triggered the incident instead of relying on a single successful command. Repeat the user-facing action, collect the service or editor log again, and compare the timestamped result with the output captured before the fix. If the affected system has more than one node, profile, workspace, or site binding, test the same path on each one before closing the incident.

  • Confirm the original error text no longer appears in the relevant event log, application log, terminal, or status command.
  • Confirm the repair survives a restart of the affected service, editor session, worker process, or virtual machine when that restart is safe.
  • Watch for secondary failures such as permission errors, stale cache, certificate mismatch, port binding conflicts, or blocked outbound connections.
  • Save the final command output and configuration path in the runbook so the next responder can compare against a known-good state.

Prevention

  • Use VS Code profiles to separate stable team tooling from experimental extensions
  • Record which extensions must be installed locally versus inside WSL, SSH, or Dev Containers
  • Review extension release notes before enabling automatic rollout on shared workstations
  • Keep workspace settings focused on project needs instead of duplicating every user preference

Rollback and Escalation

Before applying the fix in production, keep a rollback path ready. Export the current configuration, snapshot the VM or service settings where practical, and write down the exact signal that will trigger rollback. If the change does not improve the original symptom within the expected window, restore the previous configuration and reopen diagnosis from the first failing layer.

Escalate when the failing path crosses an ownership boundary such as Active Directory, DNS, storage, hypervisor networking, corporate proxy, endpoint security, or a managed extension marketplace. Include the failing command, event ID, correlation ID, host name, user profile, and timestamp so the owning team can reproduce the same path without guessing. Keep temporary mitigation separate from permanent cleanup so the service can recover before longer-term refactoring begins.

Operational Notes

Treat this guide as an incident workflow, not a blind checklist. Change one variable at a time, record the before and after state, and avoid combining unrelated registry, policy, package, or configuration changes during the same maintenance window. That discipline makes it possible to prove which change fixed Fix VS Code Extension Installed but Not Working and prevents a later responder from repeating a risky workaround without context.

When the symptom is intermittent, repeat the diagnostic command from two contexts: the affected user or service account, and an administrator session on the same host. Differences between those two outputs usually reveal policy, profile, permission, proxy, or environment-variable drift. If the failure follows only one user profile or one workspace, repair that scope first instead of changing global server settings. If it follows every profile, continue with machine-wide services, firewall rules, installed updates, and shared configuration.

  • [VS Code Auto Save Not Working](fix-vscode-auto-save)
  • [VS Code Bracket Colorization Not Working](fix-vscode-bracket-colorization)
  • [Fix Fix Vscode Copilot Not Working Issue in VS Code](fix-vscode-copilot-not-working)
  • [VS Code Debugger Not Attaching - Complete Troubleshooting Guide](fix-vscode-debugger-not-attaching)
  • [Fix VS Code Debugging Not Stopping at Breakpoints: Breakpoints Ignored](fix-vscode-debugging-breakpoints-not-working)

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "TechArticle", "headline": "Fix VS Code Extension Installed but Not Working", "description": "Diagnose VS Code extension issues with activation events, extension host logs, clean profiles, workspace trust checks, and safe extension reinstalls.", "url": "https://www.fixwikihub.com/vscode-errors-fix-extension-issue", "publisher": { "@type": "Organization", "name": "FixWikiHub", "url": "https://www.fixwikihub.com" }, "author": { "@type": "Person", "name": "FixWikiHub Editorial Team" }, "datePublished": "2026-01-01T12:22:44.178Z", "dateModified": "2026-01-01T12:22:44.178Z" } </script>