Claude Desktop v1.1.4173 crashes on startup: @formatjs/intl unhandled rejection
Resolved 💬 3 comments Opened Feb 25, 2026 by patocarranza Closed Feb 28, 2026
Description
Claude Desktop v1.1.4173 fails to display its window on startup. The process appears in Task Manager but no UI is rendered. Rolling back to v1.1.4010 resolves the issue.
Steps to Reproduce
- Let Claude Desktop auto-update to v1.1.4173
- Launch the app
- Process starts (visible in Task Manager with 4 child processes) but no window appears
Error Output
Launching app-1.1.4173\claude.exe from PowerShell reveals two unhandled promise rejections:
This error originated either by throwing inside of an async function without a catch block,
or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: [@formatjs/intl] An `id` must be provided to format a message. You can either:
1. Configure your build toolchain with [babel-plugin-formatjs]
or [@formatjs/ts-transformer] OR
2. Configure your `eslint` config to include [eslint-plugin-formatjs]
to autofix this issue
at nZe (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:83:2748)
at Sae (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:83:4203)
at WOt (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:705:12468)
at RDe (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:705:14365)
at Hd (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:705:15535)
at EventEmitter.<anonymous> (...\app-1.1.4173\resources\app.asar\.vite\build\index.js:1234:79020)
The error appears twice from two different call sites. These unhandled rejections crash the Electron renderer, preventing the window from appearing.
Additional Observations from main.log
Claude Code process exited with code 1073807364(0x40010004 = STATUS_LOCAL_DISCONNECT)[warn] Cannot save session: storage path not available(sessions lost across restarts)- MCP servers fail with
MCP error -32000: Connection closed(PDF Tools, Desktop Commander) desktop_mcp_unexpected_closeevents for AWS API MCP Server, Windows-MCP, Filesystem, Desktop Commander
Workaround
Launch v1.1.4010 directly, or rename the broken version folder:
Rename-Item "$env:LOCALAPPDATA\AnthropicClaude\app-1.1.4173" "$env:LOCALAPPDATA\AnthropicClaude\app-1.1.4173.broken"
Environment
- Working version: 1.1.4010
- Broken version: 1.1.4173
- OS: Windows 11 Home 10.0.26200
- CPU: Intel Core i7-9750H @ 2.60GHz
- RAM: 24 GB
- Arch: x64
- Node (from logs): v24.13.0
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗