The Cowork tab is missing, the VM won't start, and Anthropic's docs don't mention half of it. Here's every Windows bug we've tracked and what actually fixes them.
"The Claude API cannot be reached from Claude's workspace."
That was the first thing I saw after installing Claude Cowork on Windows. February 10, 2026. Day one of the Windows launch. I had Hyper-V enabled. My internet was working. Claude Chat loaded fine on the same machine.
But Cowork? It just stared at me and refused to connect.
I spent the next two hours reading GitHub issues, and I realized I wasn't alone. Not even close. The Claude Code GitHub repo has been flooded with Windows-specific Cowork bugs since launch day. Cryptic "yukonSilver not supported" errors. Missing Cowork tabs on fully capable machines. A VM service that installs itself and then refuses to be removed, even by administrators.
If Claude Cowork is not working on your Windows machine right now, this article will save you hours. We've tracked every major bug, mapped them to their actual causes, and listed what fixes them. No fluff. Just the bugs, the fixes, and an honest take on whether Cowork on Windows is ready for real work.
The Five Ways Cowork Breaks on Windows
Here's what nobody tells you about Cowork's Windows launch. The problems aren't random. They fall into five distinct patterns, and knowing which one you're hitting is half the battle.
1. The Missing Tab. You install Claude Desktop, open it, and the Cowork tab simply isn't there. Only "Chat" shows up. This is the "yukonSilver not supported" bug, tracked in GitHub issues #25136, #32004, and #32837. Claude's internal platform detection incorrectly marks your system as incompatible, even when all virtualization features are enabled.
2. The Infinite Setup Spinner. The Cowork tab appears, but clicking it shows "Setting up Claude's workspace" with a loading bar stuck at 80 to 90%. It never completes. Users have reported leaving it running for 12+ hours with no progress. No error message. Just spinning.
3. The API Connection Failure. The workspace starts but can't reach Claude's API. You get "Cannot connect to Claude API from workspace" or its Japanese equivalent. This was a day-one launch bug on Windows 11 Home and has resurfaced multiple times since.
4. The Network Conflict. Cowork uses a hardcoded network range (172.16.0.0/24) for its internal NAT. If your home network, corporate VPN, or another VM tool uses the same range, Cowork's VM can't reach the internet. Worse, it can break your WSL2 and Docker networking in the process.
5. The Update Regression. Cowork was working fine. Then Claude auto-updated to version 1.1.5749 on March 9, 2026, and it broke. Users report that the update introduced a regression that they can't fix without waiting for another patch from Anthropic.
The Windows Home Problem That Anthropic Still Hasn't Documented
This is where it gets messy.
Claude Cowork runs inside a lightweight Hyper-V virtual machine on your Windows machine. That's how it creates its sandboxed environment for file access and code execution. The problem? Windows 11 Home doesn't include the full Hyper-V stack.
Home edition has Virtual Machine Platform and Windows Hypervisor Platform. But it's missing the vmms (Virtual Machine Management) service that Cowork's VM requires. Without it, the VM either fails silently or throws a cryptic "Plan9 mount failed: bad address" error.
At least seven separate GitHub issues have been filed by Windows Home users who spent hours troubleshooting before discovering that their Windows edition simply can't run Cowork. One user explicitly noted they "subscribed to Max specifically to use this feature" and only discovered the incompatibility after paying.
As of March 2026, Anthropic's official Cowork documentation does not clearly state that Windows Home edition is incompatible. The docs mention that ARM64 isn't supported, but say nothing about the Home edition limitation.
A documentation request (GitHub issue #27906) was filed in February asking Anthropic to add this information. The gap remains.
If you're on Windows Home, the quickest check is to open PowerShell and run Get-Service vmms. If the service isn't found, Cowork won't work on your machine. Period.
The "yukonSilver" Bug and Why Your Pro Machine Still Fails
Stay with me here, because this one is especially frustrating.
Even if you're running Windows 11 Pro with every virtualization feature enabled (Hyper-V, VMP, WHP, WSL2), you might still see the Cowork tab missing entirely. The logs will show "yukonSilver not supported (status=unsupported)" followed by the VM bundle cleanup routine running instead of the actual VM boot.
"yukonSilver" is Claude's internal codename for its VM configuration on Windows. The bug is in the platform detection logic: it incorrectly classifies fully capable x64 Windows 11 Pro systems as unsupported.
But that's not even the real problem. The installer also creates a Windows service called CoworkVMService, and this service sometimes becomes impossible to remove. Running sc.exe delete CoworkVMService as Administrator returns "Access denied." The service blocks clean reinstalls and creates a circular failure where you can't fix the problem and you can't start fresh.
The documented workaround from community debugging: manually run Add-AppxPackage as the target user to install the MSIX package correctly for your account. It's a PowerShell command that most of Cowork's target audience (non-developers) would never discover on their own.
As one developer debugging the issue put it perfectly: "Cowork is marketed at the people least equipped to debug it when it breaks."
If you've been running into similar infrastructure headaches with AI agents and want something that works out of the box, our comparison of self-hosted vs managed OpenClaw deployments covers why some teams are moving away from local setups entirely.
The Network Bug That Breaks Docker Too
Here's what nobody tells you about Cowork's networking on Windows.
Cowork creates its own Hyper-V virtual switch and NAT network. It's separate from WSL2's networking and separate from Docker Desktop's networking. Three different tenants sharing the same hypervisor, each with their own plumbing.
The specific failure: Cowork creates an HNS (Host Network Service) network called "cowork-vm-nat" but sometimes fails to create the corresponding WinNAT rule. The HNS network exists, but there's no NAT translation. The VM boots, but it has no internet access.
And in a particularly fun bug, Cowork's virtual network has been reported to permanently break WSL2's internet connectivity until you manually find and delete the offending network configuration using PowerShell HNS diagnostic tools.
The fix, discovered by community members, involves stopping all Claude processes, killing the Cowork VM via hcsdiag, removing the broken HNS network, and recreating it on a non-conflicting subnet like 172.24.0.0/24 or 10.200.0.0/24.
This is three PowerShell commands for someone who knows what they're doing. For someone who just wanted to organize their Downloads folder with AI, it's a wall.
What Actually Fixes Each Bug (Quick Reference)
Let's cut to the practical fixes for each failure mode.
Missing Cowork Tab (yukonSilver bug): First, make sure you're not on Windows Home. If you're on Pro or Enterprise and still don't see the tab, uninstall Claude Desktop completely. Remove the CoworkVMService manually if possible (sc.exe stop CoworkVMService then sc.exe delete CoworkVMService from an elevated prompt). Clear residual files from %APPDATA%\Claude and %LOCALAPPDATA%\Packages\Claude_*. Reinstall fresh from claude.ai/download.
Infinite Setup Spinner: Check if your VM bundle downloaded correctly. Look in %APPDATA%\Claude\vm_bundles\ for the VM files. If the directory is empty or incomplete, your download was interrupted. A clean reinstall usually resolves this. If it persists on Windows Home, it's the Hyper-V incompatibility and there's no fix short of upgrading your Windows edition.
API Connection Failure: Disable your VPN temporarily. Check if your network uses the 172.16.0.0/24 range. If Chat mode works but Cowork doesn't, the issue is the VM's network stack, not your internet connection. Update to the latest Claude Desktop version (v1.1.4328 or higher specifically addressed early API connection bugs).
Network Conflict: Run Get-NetNat in PowerShell. If it returns empty but Get-HnsNetwork | Where-Object {$_.Name -eq "cowork-vm-nat"} returns a result, you're in the "missing NAT rule" failure mode. Remove the broken network and recreate it on a different subnet. Detailed steps in the blog post by Jonas Kamsker at kamsker.at.
Update Regression (v1.1.5749): If Cowork broke after the March 9 update, there's no user-side fix. You're waiting for Anthropic to ship a patch. Check the Claude Desktop release notes for the latest version.
If all of this sounds like a lot of infrastructure debugging for a tool that's supposed to "just work," that's because it is. This is exactly the kind of operational friction we built Better Claw to eliminate. Your OpenClaw agent runs on our managed infrastructure, no local VMs, no Hyper-V dependencies, no NAT conflicts. $29/month, bring your own API keys, and your first deploy takes about 60 seconds.
Why This Matters Beyond Just Bugs
Here's the honest take.
Cowork is a genuinely impressive product when it works. The sub-agent coordination, the sandboxed file access, the ability to produce polished documents from natural language prompts. Anthropic built something real here.
But the Windows launch has been rough. And the core tension is architectural: Cowork runs a full Hyper-V VM on your local machine, which means every Windows configuration quirk, every network conflict, every edition limitation becomes a potential failure point.
There are over 60 open GitHub issues tagged platform:windows on the Claude Code repo right now. New ones are still being filed daily, including as recently as March 24, 2026.
For quick desktop tasks where you're sitting at your machine and can babysit the process, Cowork is worth the troubleshooting. But if you need an AI agent that runs reliably regardless of what's happening on your local machine, the architecture needs to be different.
That's where managed OpenClaw hosting comes in. Your agent runs on cloud infrastructure. It connects to Slack, Discord, WhatsApp, and 15+ other channels. It doesn't care whether your laptop is running Windows Home or Pro, whether Hyper-V is enabled, or whether your VPN conflicts with a hardcoded subnet.
The AI agent works. Your laptop stays out of it.
The Real Question You Should Be Asking
The bugs will get fixed. Anthropic is actively patching, and the March updates have already resolved some early issues. In six months, Cowork on Windows will probably work well for most configurations.
But the question isn't whether Cowork will eventually work. The question is what you need an AI agent to do.
If you need a desktop co-pilot for occasional file organization and document creation, Cowork is the right architecture. Be patient with the bugs. Keep your Windows updated. Check GitHub before assuming the issue is on your end.
If you need an always-on agent that handles tasks across messaging platforms, runs while your computer sleeps, and doesn't depend on your local VM stack, you need something different entirely. Our guide on how OpenClaw works explains the architectural difference in detail.
Don't let the tool you chose dictate what you can build. Choose the tool that matches what you're building.
If you want an OpenClaw agent running in 60 seconds without debugging PowerShell on a Tuesday night, give BetterClaw a try. It's $29/month per agent, BYOK, and we handle the infrastructure. You handle the interesting part.
Frequently Asked Questions
Why is Claude Cowork not working on my Windows machine?
The most common causes are: running Windows Home edition (which lacks the full Hyper-V stack Cowork requires), the "yukonSilver" platform detection bug that incorrectly marks capable systems as unsupported, network conflicts with VPNs or other VM tools using the 172.16.0.0/24 range, or a corrupted CoworkVMService that blocks clean installations. Check your Windows edition first, then your virtualization settings, then the Claude Code GitHub issues for your specific error.
Does Claude Cowork work on Windows 11 Home?
Officially, Anthropic has not clarified whether Windows Home is supported. In practice, Windows 11 Home lacks the vmms service (full Hyper-V) that Cowork's VM requires, and at least seven GitHub issues document Home users unable to run Cowork. Run Get-Service vmms in PowerShell. If the service isn't found, Cowork won't work on your edition without upgrading to Windows Pro or Enterprise.
How do I fix the "yukonSilver not supported" error in Claude Cowork?
This is a platform detection bug on Claude's side, not a configuration problem on yours. The workaround involves a complete uninstall of Claude Desktop, manual removal of the CoworkVMService via elevated PowerShell, clearing residual files from %APPDATA%\Claude, and a fresh reinstall. If the CoworkVMService returns "Access denied" when you try to delete it, you may need to use the registry editor or boot into Safe Mode to remove it.
Is Claude Cowork worth $100 to $200 per month if I'm on Windows?
If you're on Windows Pro or Enterprise with a stable network configuration, Cowork delivers real value for desktop productivity tasks. But on Windows Home, it simply won't work. And even on Pro, the current bug situation means you should expect some troubleshooting time. If you need reliable AI agent infrastructure without local dependencies, a managed OpenClaw setup at $29/month with BYOK API keys may be a better fit until the Windows experience matures.
Is Claude Cowork on Windows stable enough for daily use in 2026?
As of late March 2026, Cowork on Windows is still labeled a "research preview" by Anthropic. Over 60 open GitHub issues are tagged for Windows, new bugs are being reported daily, and an auto-update in March 2026 introduced a regression that broke working installations. It's usable for non-critical desktop tasks if your system configuration is compatible, but it's not yet reliable enough for production workflows where downtime means lost work.
