[BUG] Claude Code VS Code extension 2.1.x crashes on Windows Server 2016 (build 14393) – works in 2.0.x

Resolved 💬 3 comments Opened Jan 12, 2026 by arthurgailes Closed Feb 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description
After updating Claude Code VS Code extension from 2.0.x to 2.1.x, the extension fails to start on Windows Server 2016 (build 14393). The bundled native binary resources/native-binary/claude.exe exits immediately with Windows error code 3221225785 (0xC0000139).

Rolling back to the latest 2.0.x version restores full functionality.

Environment

  • OS: Windows Server 2016 (10.0.14393)
  • VS Code: 1.104.3
  • Claude Code extension: 2.1.5 (broken), 2.0.x (works)
  • Node/npm Claude CLI: works normally on the same machine

Logs

Error from Claude (on channel …): Error: Claude Code process exited with code 3221225785

Running the bundled binary directly:

claude.exe --version
# exits immediately with no output

Notes
This looks like a Windows API / runtime baseline change in the bundled native binary between 2.0.x and 2.1.x (possibly Bun-related). If Windows Server 2016 / Win10 1607 is no longer supported, it would be helpful to document this or fail with a clearer error.

What Should Happen?

It should work

Error Messages/Logs

Steps to Reproduce

Start the VSCode extension

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.75

Claude Code Version

2.0.75

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗