Detailed Analysis
A user based in Seoul, South Korea, running Windows 11 Pro on Anthropic's Unlimited Pro Plan ($110/month), reports being unable to access the Claude Cowork feature despite having Hyper-V enabled and the latest version of the Claude Desktop application installed. The core symptom is that the application only presents Chat and Code tabs, with no Cowork tab visible — a sign that the underlying virtualization service either failed to start or was never properly initialized during installation. The user's frustration is evident, and the post reflects a broader pattern of similar complaints that have surfaced across forums and GitHub issue trackers since Claude Cowork's launch in February 2026.
Claude Cowork relies on a background Windows service — variously labeled CoworkVMService or CoworkVMServiceStore depending on installation method — that leverages Hyper-V and the Windows Host Compute Service (HCS) to run a local virtual machine environment. When this service fails to start, the Cowork tab simply does not appear, leaving users with no obvious indication of what went wrong. Known bugs in Claude Desktop versions such as 1.1.2685 include incorrect system classification that flags otherwise compatible machines as unsupported, missing or corrupted VM bundles, and service startup failures that can be triggered by storage path misconfiguration (e.g., the application being installed on a non-C:\ drive). Checking logs at `%APPDATA%\Claude\logs\cowork_vm_node.log` for strings like "yukonSilver not supported" is a key diagnostic step that many affected users overlook.
The recommended remediation path follows a logical escalation: first, fully terminating all Claude Desktop processes via Task Manager (since closing the window does not kill background services), then manually starting CoworkVMService through services.msc or an elevated PowerShell command (`sc start CoworkVMService`), and finally performing a clean reinstall with storage explicitly set to C:\ before downloading the MSIX package from claude.ai/download. If sideloading restrictions block the MSIX installation, a reversible registry modification can temporarily unlock trusted app sideloading. Importantly, users should allow 30–60 seconds after switching to the Cowork tab for the VM to fully boot before assuming failure.
This issue matters beyond one user's frustration because it exposes a significant gap in the onboarding experience for a premium product tier. At $110 per month, subscribers reasonably expect a friction-free setup, yet the Cowork feature — which is likely a key differentiator for that plan — requires manual service management, log inspection, and registry edits to function reliably. The fact that this has persisted since the February 2026 launch and continues to affect Windows 11 Pro users (not just Home, where Hyper-V limitations are more expected) suggests that Anthropic has not yet deployed a robust automated recovery or diagnostic mechanism within the installer or the application itself.
In the broader context of AI assistant development, the Claude Cowork feature represents Anthropic's push into persistent, locally-grounded AI workflows — an area where competitors are also investing heavily. The technical complexity of embedding a hypervisor-backed VM into a consumer desktop application is substantial, and Windows' layered virtualization stack (Hyper-V, HCS, WSL2) introduces compounding failure modes that are difficult to anticipate across diverse hardware configurations. Anthropic's reliance on GitHub issue trackers and community forums for user-generated troubleshooting, rather than in-app diagnostics or proactive support outreach for Pro subscribers, highlights a maturity gap that will likely need to be addressed as the feature scales to a broader user base.
Read original article →