Cowork issues on Windows

Issues the maintainers labelled both platform:windows and area:cowork.

1,074 issues · 263 open · 811 resolved (76%) · first seen Feb 12, 2026

Is this getting better or worse?

This class of problem is holding steady. 328 new reports in the last 90 days vs 426 in the 90 before — -23%. The open backlog peaked at 263 in 2026-10 and sits at 263 today.

0 66 132 197 263 2026-022026-052026-082026-10
2026-02 — First reports2026-04 — Most new reports (246)2026-10 — Peak backlog (263 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

280 of these reports name the Claude Code build they were running, spanning 115 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 38 days across 811 closures. Of the 811 closures with a recorded reason, 14% were closed as completed and 696 as not-planned or duplicate. The most recent completed fix landed in 2026-10.

Workarounds reported by the community

348 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] Cowork: Cannot use folders outside home directory on Windows (secondary drive)
…rs within your home directory can be used." A symbolic link workaround was also tested: creating a symlink inside the home directory pointing to the target folder on the secondary drive. Cowork resolves the symlink to it…
Found in the description of #29583 · resolved
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixes it
…ndbox could break again, with no obvious reason why. - This workaround has a real cost. KB5124008 is the September Patch Tuesday update and patches two actively exploited elevation-of-privilege vulnerabilities. Staying o…
Found in the thread of #92984 · still open
[BUG] Claude Desktop fails to launch on Windows — orphaned Silo / Job Object after app crash, only logoff or reboot recovers (HRESULT 0x80070020 in AppModel-Runtime EventID 215/208)
…doesn't propagate cleanup back through the Silo Only known workaround Logoff + Login (or full reboot). This clears the orphaned handle in the user-session. Service restarts and AppX package resets do not clean it up. Th…
Found in the description of #53247 · still open
Claude Desktop (Windows): provide a way to disable the bundled Cowork background service (CoworkVMService) for users who don't use Cowork
…esktop is not an option for me — I use it daily. - The only workarounds are user-hostile : take ownership of and force , or schedule a task at logon. Both may break on package updates and feel wrong on a system level. Se…
Found in the description of #57371 · still open
[FEATURE] Allow configuring VM bundle (vhdx) storage location
…ve. NTFS junctions ( ) fail. There is no reliable user-side workaround. For me, it's quite unconvenient. I have to move other files to D: to continue use Cowork. - OS: Windows 11 - Latest Claude Desktop Proposed Solution…
Found in the description of #56089 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–100

Ranked by community engagement (reactions weighted over comments). Listing the top 300 of 1,074 matches; the statistics above cover all 1,074.

Related aggregations

  1. Cowork issues on macOS

    819 issues
  2. Cowork issues on the web app

    75 issues
  3. Cowork issues on Linux

    71 issues
  4. The desktop app issues on Windows

    2,281 issues
  5. Terminal UI issues on Windows

    1,764 issues
  6. Core CLI issues on Windows

    1,414 issues
  7. Model behaviour issues on Windows

    1,314 issues
  8. Tool calls issues on Windows

    983 issues