Does Claude Cowork work on Windows?
Yes. Anthropic shipped Cowork for Windows on February 10, 2026 with the same features as the Mac build, and it went generally available on both on April 9, on x64 and ARM64 alike.
That answer is correct and not much use if you’re here because Cowork just failed on your PC. The Windows complaints fall into two piles, the edition you’re running and an update from September 8, and they’re worth pulling apart because the workarounds differ.
Windows 11 Home, then KB5124008
Local Cowork runs inside a sandboxed virtual machine, and that VM wants Hyper-V-class virtualization. On Home, a lot of people report setup failing. Three GitHub issues on anthropics/claude-code (#27906, #31991, #43915) were closed as duplicates of each other, which at least tells you it isn’t only your machine, and a Microsoft Q&A thread from July 6 was left unresolved. I can’t tell you whether Home works today. Nothing we found confirms it either way.
The update is a separate mess. KB5124008 went out on September 8 and broke Cowork’s local command execution; Anthropic acknowledged it on the 10th, Microsoft put it on its known-issues list on the 11th, and KB5129195 on September 14 didn’t fix it. As of September 15 there was no confirmed fix.
What works on any edition is cloud Cowork (in beta since July 7), because it runs on Anthropic’s machines instead of yours. And if Cowork looks different lately, that’s because on September 16 Anthropic merged it into regular Claude chat, with the line “Cowork is now Claude.”
Where dassi fits
dassi is an AI teammate that works inside the browser you already use, and on a Windows PC that’s often Edge, since it comes preinstalled. It also runs in Chrome and Brave. There’s no VM and no virtualization setting, and Home versus Pro doesn’t enter into it, which for anyone stuck on the problems above is most of the pitch.
You choose the model: Claude, GPT, Gemini, Grok, DeepSeek, Kimi, anything on OpenRouter, or a local one through Ollama. It’s $10 a month with your own API key, or $25 to $300 on a plan with credits included. You teach a job once, in plain English or by walking through it with dassi watching, save it as a workflow, and rerun it on demand or on a schedule.
Logging in to websites
Cowork reaches for connectors first. When it has to browse, its built-in browser (the default since late August) can’t use stored credentials, so you log in by hand; if you route the task through the Claude in Chrome extension instead, it uses the logins already in Chrome.
dassi works on whatever you’re already signed into. If a site has logged you out, it signs in with what your browser’s password manager autofills, and you type the 2FA code yourself. The password stays in the password manager. You never paste it into a chat or into dassi’s settings.
When to choose Claude Cowork
I’d stay with Cowork if the work reaches past the browser into local files or desktop apps, because dassi stays in the browser. Same for anything that has to run while the PC sleeps. Cowork’s scheduled tasks run in Anthropic’s cloud, and dassi’s scheduled runs happen in your browser, so the browser has to be open when a run is due. If you pay for Claude Pro anyway and cloud Cowork handles your tasks, I wouldn’t bolt on a second tool for the sake of it.
When to choose dassi
The obvious case is a Windows 11 Home laptop where local Cowork never started, or a setup that died with KB5124008 while the Friday invoices still need sending. If those tasks live on websites you’re signed into, dassi can take them over now instead of waiting on Redmond. The less obvious case is the model. Some people want GPT or a local model for this kind of work, and Cowork only runs Claude.
We don’t know when Microsoft will ship a patch that fixes KB5124008. When there’s something firmer than a known-issues entry, we’ll update this page.