[BUG] "Failed to load session" — Consistent crash on Windows ARM (Surface Laptop 7) during active Claude Code sessions
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?
`<html>
<body>
<!--StartFragment--><html><head></head><body><h1>[BUG] "Failed to load session" — Consistent crash on Windows ARM (Surface Laptop 7) during active Claude Code sessions</h1>
<h2>Preflight Checklist</h2>
<ul>
<li>[x] I have searched existing issues and this hasn't been reported yet</li>
<li>[x] This is a single bug report</li>
<li>[x] I am using the latest version of Claude Code</li>
</ul>
<h2>What's Wrong?</h2>
<p>Claude Code (via the "Code" tab in the Claude Desktop app) consistently crashes with <strong>"Failed to load session"</strong> during active sessions on a <strong>Windows ARM64</strong> machine.</p>
<h3>Reproduction steps:</h3>
<ol>
<li>Open Claude Desktop app on Windows ARM</li>
<li>Click the <strong>"Code"</strong> tab</li>
<li>Select a local project folder</li>
<li>Enter a prompt — Claude begins processing</li>
<li>After a few moments of work (generating/modifying code), the session crashes with <strong>"Failed to load session"</strong></li>
</ol>
<p>This happens <strong>every time</strong>, on every project. The session never survives long enough to complete meaningful work.</p>
<h3>What should happen:</h3>
<p>The session should remain stable throughout the coding workflow without crashing.</p>
<h2>Environment</h2>
Detail | Value
-- | --
Device | Microsoft Surface Laptop 7th Edition
Processor | Snapdragon X 12-core X1E80100 @ 3.40 GHz
Architecture | ARM64
OS | Windows 11 Home, Build 26200
RAM | 32 GB
Claude plan | Max (20x)
Claude Desktop | Latest version (as of Feb 2026)
<h2>Additional context</h2>
<ul>
<li><strong>ARM-specific issue</strong>: I also use Claude Code on a second machine (Windows 11 x86_64) for professional work, and the bug <strong>does NOT occur</strong> on that machine. Same account, same app version — only the ARM machine is affected.</li>
<li><strong>Use case</strong>: I'm a freelance developer using Claude Code daily across two machines — personal development projects on the ARM Surface Laptop, and professional file processing tasks on the x86 machine.</li>
<li><strong>Troubleshooting already attempted</strong>:
<ul>
<li>✅ Cleared all cache folders (<code>Cache</code>, <code>Code Cache</code>, <code>GPUCache</code>, <code>DawnGraphiteCache</code>, <code>DawnWebGPUCache</code>, <code>ChromeNativeHost</code>, <code>Crashpad</code>, <code>blob_storage</code>, <code>Network</code>) from <code>%APPDATA%\Claude\</code></li>
<li>✅ Restarted the app multiple times</li>
<li>❌ None of the above resolved the issue</li>
</ul>
</li>
<li><strong>Impact</strong>: The bug makes Claude Code <strong>completely unusable</strong> on Windows ARM. This is a blocker for my daily workflow.</li>
</ul>
<h2>Possibly related issues</h2>
<ul>
<li>#19336 (Failed loading session on Windows Desktop)</li>
<li>#15978 (Failed to load session)</li>
<li>#25724 (Failed to load session — session history loss)</li>
<li>#17657 (Failed to load session, frequent, requires re-login)</li>
</ul></body></html><!--EndFragment-->
</body>
</html>
``
What Should Happen?
The session should remain stable throughout the coding workflow without crashing.
Error Messages/Logs
"Failed to load session" displayed in red text on the Code tab, with a "Retour à la page d'accueil" button.Steps to Reproduce
- Open Claude Desktop app on Windows ARM
- Click the "Code" tab
- Select a local project folder
- Enter a prompt — Claude begins processing
- After a few moments, session crashes with "Failed to load session"
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.1.4088
Platform
Other
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗