Fix for Claude Desktop Workspace VM Service Issue on Windows 11 Home
Workspace Feature Broken on Windows 11 Home
The workspace/Cowork feature in Claude Desktop has been failing on Windows 11 Home installations for months, displaying the error: "Failed to start Claude's workspace — VM service not running."
Root Cause
The CoworkVMService cannot verify its own executable path within the locked WindowsApps directory. Signature verification fails before the VM even starts.
Manual Fix via PowerShell
Run these commands in an Admin PowerShell session:
Stop-Service CoworkVMService -Force -ErrorAction SilentlyContinue
Copy-Item "C:\Program Files\WindowsApps\Claude_*_x64__*\app\resources\cowork-svc.exe" "$env:USERPROFILE\cowork-svc.exe"
& "$env:USERPROFILE\cowork-svc.exe"Keep the PowerShell window open, then launch Claude Desktop. The workspace should load successfully.
Automated Solution
A GitHub tool automates this process with auto-start at logon and auto-sync when Claude updates: https://github.com/tiranmoskovitch-dev/claude-vm-fix
This solution works on Windows Home edition without requiring an upgrade to Windows Pro.
📖 Read the full source: r/ClaudeAI
👀 See Also
Practical Review: 3 Essential Clawhub Skills and 3 to Avoid
A developer tested Clawhub skills for weeks and found three worth installing: web-search (Brave), daily-brief, and memory-search. Three others—food-order, multi-agent orchestrators, and humanizer—waste tokens and add unnecessary complexity.
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.
Splitting Agent Context into Three Layers to Solve the 700-Line Monolith Problem
A team building a 6-agent autonomous system solved context file bloat by separating agent context into three layers based on concern type and change frequency: CLAUDE.md for identity, BRIEFING.md for mission, and PLAYBOOK.md for operations. This approach prevents silent failures from argument limits and makes editing predictable.
Qwen3.5-397B MoE Runs on 14GB RAM via Paged Expert Loading on M1 Ultra
Paged MoE engine keeps only 20 experts resident and lazy-loads the rest from SSD, running a 209GB 397B model on a 64GB Mac Studio with 1.59 tok/s and 14GB peak RAM. Includes smaller model benchmarks.