Fix for 'VM Service Not Running' error in Cowork on Windows 11
Diagnosing and fixing the virtualization error
A user on r/ClaudeAI reported encountering a 'VM Service Not Running' error in Cowork on Windows 11 Home, particularly when tinkering with MCPs. The error appeared and disappeared randomly. After checking that Hyper-V was installed and running, they discovered the root cause: the hypervisor wasn't set to launch at boot.
Diagnostic command
To check if this is the issue, run this PowerShell command:
bcdedit /enum | findstr -i hypervisor
If the output shows hypervisorlaunchtype Off, that's the problem. The hypervisor needs to be active at the boot level, not just running as a service after Windows loads.
Fix command
To resolve this, run:
bcdedit /set hypervisorlaunchtype auto
After running this command, perform a full restart of your system and try Cowork again. The user confirmed this fixed their issue after multiple troubleshooting attempts.
📖 Read the full source: r/ClaudeAI
👀 See Also
OpenClaw's Gateway and Skills: Moving Beyond Chat to Automated Execution
OpenClaw's Gateway connects channels like Telegram and WhatsApp to skills that execute real-world actions such as running tests, calling APIs, and managing files, with cron jobs enabling scheduled background automation.
Developer shares 25 tested Claude prompts for SaaS development workflows
A developer has shared 25 specific prompts they use daily for SaaS development, covering backend architecture, API design, frontend copy, product documentation, and go-to-market tasks. The prompts are designed to save time on repetitive tasks like code review, documentation generation, and edge case testing.
Building API endpoints with Claude: Practical prompt engineering lessons from a 70+ endpoint project
A developer built 70+ LinkedIn automation API endpoints with Claude writing 80% of the code, discovering that treating prompts like contracts with explicit constraints works better than natural language instructions for action-taking agents.
DeepSeek-V4-Flash W4A16+FP8 with MTP Self-Speculation: 85 tok/s on 2x RTX PRO 6000 Max-Q
DeepSeek-V4-Flash quantized to W4A16+FP8 achieves 85.52 tok/s at 524k context on 2× RTX PRO 6000 Max-Q using a patched vLLM with retrofitted MTP head, up from 52.85 tok/s baseline.