[BUG] App Don't work in ARM Microsfot Surface, the window nevers appear

Resolved 💬 3 comments Opened Feb 25, 2026 by danielcomin-bit Closed Feb 28, 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?

Claude Desktop 1.1.4173 starts (4 processes visible in Task Manager, ~150MB total memory) but no window ever renders. No crash, no system tray icon. The app was working on 1.1.4088 (Feb 24) and broke after auto-update to 1.1.4173 (Feb 25).
Console output shows unhandled promise rejection from @formatjs/intl ("An id must be provided to format a message") at index.js:83:2748. All MainWindowHandle values are 0 — the BrowserWindow is never created.
Tested: --disable-gpu, --disable-gpu-compositing, --use-angle=swiftshader, --force-device-scale-factor=1, --lang=en-US, --no-sandbox, full cache wipe (%APPDATA%\Claude + %LOCALAPPDATA%\AnthropicClaude), clean reinstall. None resolved the issue.
Downgrading to 1.1.4088 (x64 via Uptodown) immediately fixes the problem.
Environment: Windows 11 25H2 (Build 26200), Snapdragon X 12-core X1E80100 @ 3.40 GHz, 32GB RAM, Surface device.

What Should Happen?

Claude Desktop should render its main window on launch, as it did on version 1.1.4088 and all prior versions.

Error Messages/Logs

Steps to Reproduce

Install Claude Desktop 1.1.4173 (ARM64 or x64) on Windows ARM64 (Snapdragon X Elite)
Launch Claude Desktop
App appears in Task Manager with 4 processes but no window renders
Get-Process Claude | Select MainWindowHandle returns 0 for all processes
Downgrade to 1.1.4088 → window appears normally

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1.4173

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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