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
Claude Code Skills vs. Custom Agents: A Mental Model Based on Task Consistency
A Reddit user clarifies the distinction between Claude Code skills and custom agents: skills execute the same steps every time, while custom agents require reasoning and adaptation. The post also covers parallel subagents, delegation, hooks, and building blocks.
Components of a Coding Agent: How Tools, Memory, and Context Extend LLMs
Sebastian Raschka breaks down the six building blocks of coding agents like Claude Code and Codex CLI, explaining how agent harnesses combine models with tools, memory, and repository context to make LLMs more effective for software work.
OpenClaw Memory Plugin Analysis: Lossless Claw + LanceDB Recommended
A developer tested OpenClaw memory plugins and found that the default setup causes token bloat, while Lossless Claw paired with LanceDB provides optimal performance for maintaining agent context without high costs.
Agent-Oriented API Design Patterns: Insights from Moltbook
Moltbook's API design supports proactive AI agent interactions by integrating direct instruction, state transitions, cognitive challenges, and educational rate-limiting.