[BUG] ENOSPC: no space left on device - Cowork workspace stuck at 75% on Windows 10

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?

Cowork workspace fails to start every time. Gets stuck at
around 75% and then shows ENOSPC: no space left on device error.

System info:

• Windows 10
• 8GB RAM
• 10GB free disk space on C: drive

Things I already tried:

• Reinstalling Claude Desktop
• Clearing disk space
• Enabling VirtualMachinePlatform via PowerShell
• Freeing up RAM to 62%
• Reinstall workspace button
• Restarting laptop multiple times

Nothing works. Please fix this bug.

What Should Happen?

The Cowork workspace should start up successfully and be ready to use.

Error Messages/Logs

ENOSPC: no space left on device, write

Restarting Claude or your computer sometimes resolves this. 
If it persists, you can reinstall the workspace or share 
your debug logs to help us improve.

Steps to Reproduce

1. Install Claude Desktop on Windows 10
2. Open Claude Desktop
3. Click on Cowork tab
4. Select a folder to give Cowork access to
5. Watch the workspace setup progress bar
6. It gets stuck at around 75% and shows ENOSPC error
7. Clicking "Reinstall the workspace" does not fix it
8. Restarting laptop does not fix it

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Desktop (not Claude Code CLI)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

System specs:

• Windows 10
• 8GB RAM
• 10GB free disk space on C: drive

Things I already tried:

• Reinstalling Claude Desktop multiple times
• Freeing up disk space to 10GB
• Freeing up RAM to 62%
• Enabling VirtualMachinePlatform via PowerShell
• Clicking "Reinstall the workspace" button
• Restarting laptop multiple times
• Running wsl --shutdown in PowerShell

Nothing has worked. The error appears every single time
at around 75% of workspace setup.