TechFixSignal
VS Code

VS Code Extension Host Terminated Unexpectedly 3 Times

When VS Code shows Extension host terminated unexpectedly 3 times within the last 5 minutes, set Http Proxy Support to off, then consider rolling back to 1.129.

Reviewed by TechFixSignal EditorialSee how this guide is verified

Last checked
Sep 9, 2026
Applies to
Windows, Mac, Desktop
Fix status
Community Confirmed
Fastest useful check

Quick answer

Match the toast Extension host terminated unexpectedly 3 times within the last 5 minutes. First open Settings, search Http: Proxy Support, set it to off, then fully quit and relaunch VS Code. If Ext Host logs still show createProxyAuthorizationLookup or @vscode/proxy-agent failing, and you are on 1.130 or newer, roll back to VS Code 1.129 only after backing up settings — that path is more disruptive than the Proxy Support leftover. Reload Window alone is not enough for this fingerprint.

On this page

What we're seeing

  • The exact toast is Extension host terminated unexpectedly 3 times within the last 5 minutes.
  • Independent September 2025–August 2026 first-hand GitHub issues quote that toast, including cases with no third-party extensions enabled.
  • One first-hand cluster ties the crash loop to Http: Proxy Support and clears after setting Proxy Support to off.
  • Another first-hand cluster from 1.130 onward shows Ext Host SyntaxError around createProxyAuthorizationLookup in @vscode/proxy-agent and reports a stable leftover on 1.129.
  • A one-off exit-code-5 self-resolve is not the leftover for this guide.

Start here

Try these first

Fix 1

Confirm the extension host toast

Community Confirmed

Match the three-times toast before changing proxy settings or rolling back a build.

  1. Read the notification. This guide is for Extension host terminated unexpectedly 3 times within the last 5 minutes.
  2. Open Help → Toggle Developer Tools or the Ext Host log and note whether createProxyAuthorizationLookup or @vscode/proxy-agent appears.
  3. Note your VS Code version under Help → About.
  4. Do not stop at Developer: Reload Window alone for this fingerprint.

Applies to Windows, Mac, Desktop

Fix 2

Set Http: Proxy Support to off

Community Confirmed

A first-hand September 2025 report with the exact toast and no extensions confirmed Http: Proxy Support = off as a working leftover. Try this before any version rollback.

  1. Open Settings and search for Http: Proxy Support.
  2. Set Http: Proxy Support to off.
  3. Fully quit VS Code and relaunch it. Do not rely on Reload Window alone.
  4. Confirm the toast stays gone while you open folders and use extensions again.

Applies to Windows, Mac, Desktop

Fix 3

Roll back to VS Code 1.129 if still crashing

Community Confirmed

August 2026 first-hand reports show the createProxyAuthorizationLookup Ext Host failure on 1.130 and later, with a stable leftover after returning to 1.129. This is more disruptive than Proxy Support off — back up settings first.

  1. Confirm Ext Host logs still mention createProxyAuthorizationLookup or @vscode/proxy-agent after Proxy Support is off.
  2. Confirm Help → About shows 1.130 or newer.
  3. Export or copy your settings and keybindings so you can restore them after a downgrade.
  4. Install VS Code 1.129 from the official previous-versions archive for your OS, then relaunch.
  5. If the toast is gone on 1.129, stay on that build until a newer release no longer reproduces the Ext Host crash.

Applies to Windows, Mac, Desktop

Fix 4

Isolate a bad extension or profile

Community Confirmed

Some same-toast reports clear after a clean profile even when Proxy Support is already off. Use this only after the proxy leftover.

  1. Start VS Code with extensions disabled once as a test, or open a fresh profile.
  2. If the toast disappears, re-enable extensions in small groups to find a conflict.
  3. If it still crashes with extensions disabled and Proxy Support off, prefer the 1.129 rollback leftover above.

Applies to Windows, Mac, Desktop

Device notes

Windows
Http: Proxy Support lives in Settings. Prefer off before any installer downgrade.
Mac
Same Proxy Support leftover. Fully quit from the menu bar after changing it.
Desktop
Ext Host logs that name @vscode/proxy-agent point to the 1.129 rollback branch when Proxy Support off is not enough.

Official information

Checked on 9 September 2026, microsoft/vscode GitHub issues that quote Extension host terminated unexpectedly 3 times within the last 5 minutes document first-hand leftovers for Http: Proxy Support = off and for staying on 1.129 when @vscode/proxy-agent fails on 1.130+. There is no separate VS Code Docs page that names only this exact three-times toast as a known issue with those leftovers.

Sources

Keep troubleshooting

Related problems