[BUG] VS Code Extension - Missing Windows ARM64 Support

[oddrationale]

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?

Same issue reported in the following: #11925, #11868, #8757, #8439, #8422, and #8410. All of these issues are closed but the issue still persists.

I am not able to use the Claude Code in the VS Code Extension. I get the following error message: Error: Claude Code requires Node.js version 18 or higher to be installed.

VS Code Version: 1.106.3 Claude Code Extension Version: 2.0.46 Claude Code (CLI) Version: 2.0.58 Node Version: 22.14.0 OS Version: Windows 11 26200.7171 (ARM64)

What Should Happen?

Should be able to use the Claude Code extension in VS Code.

Error Messages/Logs

Error: Claude Code requires Node.js version 18 or higher to be installed.

Steps to Reproduce

1. Install the Claude Code VS Code extension.
2. Restart VS Code.
3. Open Claude Code within VS Code.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.58

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[github-actions[bot]]

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/11868
2. https://github.com/anthropics/claude-code/issues/8757
3. https://github.com/anthropics/claude-code/issues/11925

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[blois]

I believe the issue here is missing Windows ARM64 support.

[oddrationale]

The Claude CLI works as expected on Windows on ARM. I installed it using the binary version. I'm not sure what the relationship is between the VS Code extension and the CLI, so I'm not sure if this info is helpful.

Let me know if there is any further troubleshooting or logs I can provide to help.

[teo-lapa]

+1 per questo problema.

Configurazione:

• VS Code: 1.106.3
• Claude Code Extension: 2.0.46 (ultima disponibile per Windows ARM64)
• OS: Windows 11 ARM64 (Build 26200.7171)
• Hardware: PC Windows ARM64 moderno

Problema: L'estensione VS Code è ferma alla versione 2.0.46 per Windows ARM64, mentre sono disponibili versioni fino alla 2.0.60 per altre piattaforme (Windows x64, macOS, Linux).

Quando provo ad aggiornare tramite VS Code Marketplace, ottengo sempre la 2.0.46 perché le versioni successive (2.0.47-2.0.60) non sono compilate per win32-arm64.

Richiesta: Sarebbe possibile rilasciare anche le versioni più recenti dell'estensione VS Code compilate per la piattaforma Windows ARM64?

Grazie!

[teo-lapa]

Bumping this issue to prevent auto-closure.

The Windows ARM64 support gap is a significant blocker for users like myself on modern ARM-based Windows devices (Snapdragon laptops).

Current situation:

• ✅ Linux ARM64: supported (latest version available)
• ✅ macOS ARM64: supported (latest version available)
• ❌ Windows ARM64: stuck at v2.0.46 (latest is v2.0.61)

Since Windows on ARM devices can run x64 apps through emulation, a temporary workaround would be to install VSCode x64 instead of ARM64 native. However, native ARM64 support would be the proper solution.

@blois - Is there any timeline or technical blocker preventing Windows ARM64 builds from being published to the marketplace? The architecture is already supported for Linux and macOS ARM64, so it seems like it should be straightforward to add win32-arm64 to the build targets.

Thank you!

[oddrationale]

@blois: Hi, I noticed this issue was closed and wanted to clarify the reasoning.

Was it closed because the problem has been fixed in a recent release? If so, could you share which version includes the fix?

Or is this something that isn’t planned to be addressed going forward?

Thanks for the transparency!

[blois]

The issue should be fixed in the next release- the extension will attempt to use the x86 binary via emulation.