[DOCS] Cowork requirements should clearly state Windows Pro/Enterprise is required (Home edition not supported)

Resolved 💬 5 comments Opened Feb 23, 2026 by nelly-mfp Closed Feb 26, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://support.claude.com/en/articles/13345190-getting-started-with-cowork

Section/Topic

Cowork - System Requirements / Windows compatibility

Current Documentation

The Cowork "Getting started" documentation states:

  • Windows (arm64) is not currently supported.
  • Open to all paid users.

It does NOT mention that Windows Home edition is incompatible due to missing full Hyper-V support (specifically the vmms service).

The problem

Cowork requires full Hyper-V (the vmms - Virtual Machine Management service), which is only available on Windows Pro/Enterprise/Education. Windows Home only includes "Virtual Machine Platform" + "Windows Hypervisor Platform", which is insufficient for Cowork's VM-based sandbox.

Error on Windows 11 Home:

RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address

Diagnostic findings:

  • OS: Windows 11 Home 24H2 (Build 26100), x64
  • vmcompute service: Running (used by Docker)
  • vmms service: MISSING - not available on Home edition
  • OneDrive: Running (not the cause)
  • Windows Search Indexer: Running (not the cause)

Related issues confirming this affects many users:

  • #24918 - Cannot connect to Claude API from workspace (Win 11 Home)
  • #24962 - VM fails: wrong DNS, missing sessiondata.vhdx, no NAT (Win 11 Home)
  • #25241 - Windows 11 Home issue
  • #25663 - Cowork workspace bricked (Win 11 Home)
  • #26090 - Cowork tab not showing (Win 10 Home)
  • #26873 - Plan9 mount failed (Win 11 Home)
  • #27384 - "Virtualization is not enabled" error despite hypervisor active (Win 11 Home)

Suggested documentation change

Please add to the Cowork requirements page:

Windows edition: Requires Windows 11 Pro, Enterprise, or Education. Windows Home is not supported due to missing Hyper-V Virtual Machine Management (vmms) service.

This affects a large portion of Windows users, as most consumer PCs ship with Windows Home edition. Clear documentation would save users significant time troubleshooting an issue that has no workaround on Home edition.

What's Wrong or Missing?

The Cowork documentation is missing critical Windows edition requirements:

  1. No mention that Windows Home is not supported - The docs only mention ARM64 is unsupported, but don't mention that Home edition lacks the required Hyper-V vmms service
  2. No clear system requirements - Users on Windows Home waste significant time troubleshooting an issue that has no workaround
  3. Multiple GitHub issues from Home users - At least 7 separate issues (#24918, #24962, #25241, #25663, #26090, #26873, #27384) report the same root cause
  4. Misleading "available to all paid users" claim - Paid users on Windows Home cannot use Cowork at all

The documentation should clearly state: "Requires Windows 11 Pro, Enterprise, or Education. Windows Home is not supported."

Suggested Improvement

Add the following to the Cowork "Getting Started" page under system requirements:

System Requirements - Windows

| Requirement | Details |
|---|---|
| Windows Edition | Pro, Enterprise, or Education (Home is not supported) |
| Architecture | x64 (ARM64 not supported) |
| Hyper-V | Must be enabled (requires vmms and vmcompute services) |

Note: Windows Home edition does not include the full Hyper-V stack required by Cowork. If you see the error "Plan9 mount failed: bad address", check your Windows edition. You can verify by running Get-Service vmms in PowerShell — if the service is not found, your Windows edition does not support Cowork.

Impact

High - Prevents users from using a feature

Additional Context

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗