[BUG] Cowork fails with "Claude Code process exited with code 1" — persists through reboot and clean reinstall (Windows 10, v1.3036.0)

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?

Every attempt to start a Cowork session crashes immediately with the error: Claude Code process exited with code 1. The crash persists through a full system reboot and a complete uninstall/reinstall of Claude Desktop.
Environment

OS: Windows 10
Claude Desktop version:
Feature affected: Cowork

Troubleshooting attempted (all unsuccessful)

Confirmed no ANTHROPIC_API_KEY environment variable set at User or Machine scope
Full Windows restart
Uninstall of Claude Desktop via Windows Settings → Apps
Deleted leftover %LOCALAPPDATA%\Claude folder
Fresh download and install from claude.com/download
Signed in on fresh install, retried Cowork — same crash

What Should Happen?

Function without errors

Error Messages/Logs

Claude Code process exited with code 1.

Steps to Reproduce

Reproduction

Open Claude Desktop
Start a new Cowork session
Crash occurs immediately with Claude Code process exited with code 1

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.3036.0 (cf521c)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Additional observations

The %LOCALAPPDATA%\Claude\Logs directory contains only chrome-native-host.log. No main.log, renderer.log, or Cowork/VM-related log files exist, so no detailed crash information is available on the client side.
The chrome-native-host.log shows healthy start/stop cycles with no errors, indicating the Claude-in-Chrome bridge is working normally — this is specific to Cowork.
An earlier attempt to rename %LOCALAPPDATA%\Claude returned "Access denied" even with no Claude processes running (per Get-Process laude), suggesting a file lock from something other than the visible Claude processes at that time. This was before the reinstall; post-reinstall the folder is accessible.

Impact
Cowork is completely unusable on this machine. Other Claude surfaces (claude.ai in browser, Claude CLI in terminal) work normally.
Request
Guidance on where Cowork's main/VM logs should be written on Windows 10, or a fix for whatever is preventing the Cowork process from starting.