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

12GB VRAM Benchmarks: Running Qwen 3.6 and Gemma 4 Models on a RTX 4070 Super
A Reddit user shares detailed speed benchmarks for Qwen3.6-35B-A3B, Qwen3.6-27B, Gemma 4 26B, and Gemma 4 31B on a 12GB RTX 4070 Super using llama.cpp with optimized settings.

Optimizing Qwen 3.6 27B/35B on RTX 3090: Flags, Quantization, and Auto-Routing
A user shares his llama-server flags for Qwen 3.6 27B and 35B GGUF models on an RTX 3090 (24GB), reporting slow speeds for the 35B and unreliable code output from the 27B. The post asks for better quant, flag tuning, and auto model switching.

How OpenCLAW Memory Actually Works: Fixing Agent 'Forgetting'
OpenCLAW agents don't have persistent memory between conversations - they reconstruct context from files like SOUL.md, USER.md, and MEMORY.md each time. Common 'forgetting' issues stem from old sessions, unstructured memory files, and storing important info in chat history instead of permanent files.

Access GPT-5.4 via Codex subscription in OpenClaw
A Reddit post details how to configure OpenClaw to use GPT-5.4 through an OpenAI Codex subscription by modifying the openclaw.json configuration file and restarting the gateway.