Fixing Claude Cowork 'Failed to start workspace' errors on Windows 11 Home
The problem: Claude Cowork fails to start on Windows 11 Home
A user encountered multiple errors when trying to use Claude Cowork on Windows 11 Home with Claude Desktop latest version (Feb 2026). The system had virtualization enabled in BIOS, no VPN, no Hyper-V, and no WSL2 initially, with an active Wi-Fi connection.
Errors encountered
- "Failed to start Claude's workspace. Can't reach the Claude API from Claude's workspace."
- "VM service not running. The service failed to start."
- "HCS operation failed: failed to create compute system: HcsWaitForOperationResult failed with HRESULT 0x800707de"
- "API Error: Unable to connect to API (ECONNRESET)"
- "Cannot create system 'cowork-vm' since Hyper-V is not installed"
What didn't work
The user tried numerous troubleshooting steps that failed to resolve the issue:
- Clean uninstall and reinstall of Claude
- Deleting temp files
- Restarting CoworkVMService manually
- Fixing DNS on Wi-Fi adapter (changed from 172.20.10.1 to 1.1.1.1/8.8.8.8)
- Removing duplicate bad DNS entry from HNS endpoint
- Disabling IPv6 on Wi-Fi adapter
- Setting Wi-Fi interface metric to lowest priority (metric 10)
- Creating NAT manually with New-NetNat
- Assigning IP manually to cowork-vm-vnet adapter
- Disabling/enabling Windows Firewall rules
- Running Claude as Administrator
- Enabling Virtual Machine Platform and WSL features via DISM
- Trying to install WSL2 kernel update package (failed — wrong installer)
The actual fix: Install WSL2 from Microsoft Store
The solution required three steps:
- Open Microsoft Store and search "Windows Subsystem for Linux" or go to: https://www.microsoft.com/store/productId/9P9TQF7MRM4R. Click Install and wait for completion.
- Restart your computer completely.
- Open Claude and go to Cowork tab.
To verify WSL2 installed correctly, open PowerShell and run: wsl --version. You should see WSL version 2.x.x.x.
Why this works
Claude Cowork runs inside a lightweight VM on Windows. It uses WSL2 as its underlying technology, not full Hyper-V. If WSL2 is not installed, the VM can't start.
Bonus tip for persistent API connection issues
If after installing WSL2 you still get "Can't reach Claude API," run this in PowerShell as administrator to check routing priority:
Get-NetIPInterface | Sort-Object -Property InterfaceMetric | Format-Table
Find your active Wi-Fi interface index and set it to metric 10:
Set-NetIPInterface -InterfaceIndex X -InterfaceMetric 10
Replace X with your actual interface index number.
📖 Read the full source: r/ClaudeAI
👀 See Also
Google AI Pro Account Restored After OpenClaw OAuth Ban — Appeal Form Works
A user reports their Google AI Pro account was restored 3 months after being banned for linking to OpenClaw via Google OAuth. The official appeal form eventually worked.
Running Qwen3.6-35B-A3B with ~190k Context on 8GB VRAM + 32GB RAM – Setup & Benchmarks
A Reddit user shares a working llama.cpp configuration for Qwen3.6-35B-A3B GGUF models on an RTX 4060 (8GB VRAM) + 32GB DDR5, achieving 37-51 tok/s at 192k context using TurboQuant and specific flags.
OpenClaw Project Operating System: Multi-Project Management Framework
A framework that isolates projects with standardized directories, uses cron for automation instead of agents for predictable tasks, and implements mandatory backup protocols to reduce token usage and improve execution consistency.
Claude for Motion Graphics: Prompt Patterns That Produce Animated HTML Visuals You Can Capture as Video
A r/ClaudeAI user shares a reliable prompt structure for generating animated motion graphics and interactive charts as HTML widgets from Claude, then capturing them as MP4 with Playwright + ffmpeg.