Windows Cowork VM Service Error: Path Issue and Fix
Windows Cowork VM Service Failure
Windows users of Claude's Cowork feature are experiencing a recurring error where the service fails every 10-20 minutes with the message "VM service not running. The service failed to start." The root cause is related to the vm_bundles folder, but the commonly cited path (%APPDATA%\Claude\vm_bundles) doesn't exist for MSIX installations.
The Actual Problem
The issue stems from Cowork looking for the vm_bundles folder in the wrong location on Windows systems with MSIX installations. The standard path that most documentation references doesn't apply to these installations, leading to the service repeatedly failing to start.
Documented Solution
A user has documented the complete fix, which includes:
- Identifying the correct path for the vm_bundles folder on MSIX installations
- A repair script to address the issue
- A filed bug report with Anthropic (GitHub issue #170)
- An assessment of Cowork's current stability status on Windows
Available Resources
The full technical write-up with detailed steps is available at the author's website, and the GitHub issue (#170) has been created in the anthropics/knowledge-work-plugins repository to track this problem officially.
📖 Read the full source: r/ClaudeAI
👀 See Also
Practical Prompt Structure for Claude AI Execution Agents
A developer shares prompt engineering techniques that reduced hallucinations in Claude AI agents performing API calls, data extraction, and multi-step workflows. Key strategies include writing prompts as contracts, dedicating 40% of tokens to error handling, and separating 'wait' from 'stop' conditions.
Contract Testing for AI-Driven Development with OpenClaw
Contract testing can replace integration/E2E tests when using AI agents like OpenClaw, focusing on interfaces and invariants between components. The AI generates code to satisfy deterministic contracts, creating a tight feedback loop for faster iteration.
Using Claude to analyze writing patterns for better custom instructions
A Reddit user describes a method for creating more effective custom instructions by having Claude analyze 10 writing samples to identify concrete patterns like punctuation avoidance and analogy sources, rather than relying on subjective tone descriptions.
Claude Code LSP Setup Guide: Structural Code Understanding
A Reddit post details how to configure Claude Code to use Language Server Protocol for structural code understanding instead of text matching, reducing query times from 30-60 seconds to ~50ms with go-to-definition, find-references, and call hierarchy features.