Claude Cowork Not Working? The Complete Troubleshooting Guide

Quick checklist before you dig in

1. Paid plan. Cowork needs Pro, Max, Team, or Enterprise. It is not available on the free plan. See Cowork pricing.
2. Latest app. Update the Claude desktop app and fully quit it (not just close the window) before reopening.
3. Internet connection. Cowork needs a live connection for the whole task, even for local files.
4. Service status. Check status.claude.com. If there is an active incident, Cowork not working is on Anthropic's side and not something you can fix locally.
5. Organization settings. On Team and Enterprise, an admin has to enable Cowork. If colleagues also lack it, ask your admin.

Or jump straight to the symptom you searched for:

It also helps to know where Cowork runs. Sessions now run in the cloud by default (in beta): the agent works on Anthropic's servers and saves sessions to your account. The desktop app is still needed for local files, browser use, computer use, and plugins with local MCP servers, and it runs code for local sessions inside a virtual machine on your computer. Many desktop errors come from that virtual machine, which is why so many fixes below involve virtualization.

Cowork not showing up in the desktop app

The most basic version of Cowork not working is not seeing it at all. If you cannot find Cowork, work through these causes:

• New app layout. Recent versions removed the separate Chat and Cowork tabs. Choose Cowork in the message box instead of looking for a tab.
• Wrong Windows installer. Cowork requires the .msix package. Machines set up with the legacy .exe installer get Claude Desktop without Cowork. Reinstall from the official download page.
• No admin rights on Windows. Anthropic notes that users without admin access can install Claude, but Cowork on desktop will not be available.
• Unsupported system. Current requirements are macOS 14 Sonoma or later, or Windows 10 build 19041 (version 2004) or later, including Windows 11. Windows machines must be x64 or Arm64. There is no Linux version; Linux users can look at open source alternatives.
• Virtual machines and VDI. Cowork cannot run inside a VM or virtual desktop that lacks nested virtualization.

Cowork not working on Windows: virtualization errors

Most reports of Claude Cowork not working come from Windows, and most of those are virtualization problems. Errors such as “Virtualization is not enabled” or “Virtualization is not available” mean the workspace virtual machine cannot start. Cowork on Windows needs working hardware virtualization, the Windows hypervisor, and the Virtual Machine Platform optional feature. Fix them in this order:

1. Turn on virtualization in BIOS/UEFI. The setting is usually called Intel VT-x, Intel Virtualization Technology, or AMD SVM. It is sometimes off by default.
2. Enable Virtual Machine Platform. Run PowerShell as administrator: Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -All
3. Make the hypervisor launch at boot. Run bcdedit and confirm hypervisorlaunchtype is Auto. If not, run bcdedit /set hypervisorlaunchtype auto.
4. Use Restart, not Shut down. With Fast Startup on, a shutdown and power-on can leave virtualization services uninitialized. Anthropic specifically recommends a real restart.
5. Close other hypervisors. VirtualBox, VMware, or Docker in some modes can hold the hypervisor. Quit them and try again.

To see what the app detected, open Help → Troubleshooting → Show Logs in Claude Desktop and look at supported-features-info.json. For a full setup walkthrough, see our Cowork on Windows guide.

Windows Home editions

Anthropic's documentation lists Virtual Machine Platform as the Windows requirement, but a number of Windows 10 and 11 Home users have reported virtualization errors on GitHub even with it enabled. If you are on Home and Cowork is not working after every step above, run the readiness check and include its result when you contact support.

“Couldn't connect your C: drive” after a Windows update

If Cowork was not working for local commands in September 2026 and showed a message that it couldn't connect your C: drive to its workspace, the cause was not Claude. Microsoft's September 8, 2026 security update (KB5124008) changed how Hyper-V shares host folders with Linux virtual machines over Plan9, which broke the folder share Cowork uses. Anthropic marked Cowork on Windows as degraded while reinstalling did not help.

Microsoft fixed it in the out-of-band update KB5129195 (September 14, 2026) for Windows 11 24H2 and 25H2. The fix: open Settings → Windows Update, install KB5129195, restart, and confirm your build with winver. Insider builds on separate branches may not receive that fix.

Stuck on “Setting up Claude's workspace” or “Failed to start Claude's workspace”

One of the most common forms of Cowork not working is a workspace that never finishes starting. The first time Cowork runs locally, Claude Desktop downloads a workspace bundle (more than 1 GB) and a helper binary from downloads.claude.ai. If that download fails or is altered in transit, you will see Failed to start Claude's workspace followed by an error like “Checksum/decompress failed,” “Download failed,” or “Request error.” A missing helper shows as “Host Claude Code binary not available.”

• Restart the app to retry the download. This is enough when an earlier attempt was just interrupted.
• Check proxies, VPNs, and web filters. If the same error returns every time, something between you and downloads.claude.ai is blocking or cutting off the file. Let the Claude app itself, not only your browser, reach that domain.
• Check security software. Antivirus or EDR tools can quarantine the downloaded files or block the helper from launching. Allowlist the helper by its publisher, Anthropic, PBC.
• Free up disk space. The workspace needs room for its image; a nearly full drive stops it from being unpacked.

“Cowork requires a newer installation”

This message usually means your app build is out of date or was installed with the wrong package. Download a fresh installer, install it with admin rights, and restart the computer. If it persists on a supported Windows build, generate a diagnostic report (below) and send it to support.

“Workspace unavailable”

When the local virtual machine is down, Cowork keeps running its file and web tools, but shell commands and code execution report “workspace unavailable” until the VM recovers. Quit and relaunch the app, then restart the computer if needed.

Cowork not working on Mac

On macOS, Cowork runs local code in a virtual machine built on Apple's Virtualization framework. Check that you are on macOS 14 Sonoma or later and have enough free disk space. If Cowork is not working on your Mac after an update, fully quit Claude from the menu bar, reopen it, and let the workspace rebuild. Grant folder access when macOS asks, and review System Settings → Privacy & Security if you dismissed the prompt. More setup detail is on our Cowork for Mac page.

Cowork not working after an update

A surprising share of reports about Cowork not working appear right after an update, either to Claude Desktop or to the operating system. Updates can replace the workspace image, reset the hypervisor, or change how folders are shared with the virtual machine.

1. Fully quit Claude Desktop and reopen it so the new version finishes installing. The app also restarts itself within 72 hours of downloading an update.
2. Restart the computer once, using Restart rather than Shut down on Windows.
3. Give the first task a minute or two while the workspace rebuilds.
4. If Cowork is not working only for local commands after a Windows update, check the C: drive section above and install the latest Windows updates.
5. Still broken? Check status.claude.com, then generate a diagnostic report as described at the end of this guide.

Cowork not working with your files

When Cowork is not working with your files, the cause is almost always access. Cowork only touches folders you have connected on the desktop, and it checks every local tool call against your permissions. If it says a file does not exist or it cannot write to a folder:

• Connect the folder again from the desktop app, and make sure you picked the parent folder that actually contains the files.
• Keep the desktop app open and online. A cloud session can keep working with the app closed, but it loses access to local files until the app reconnects.
• Move files off network shares or removable drives into a local folder if access keeps failing.
• Remember the Cowork sandbox is doing its job: it will not reach outside the folders you shared.

Cowork not working with connectors or plugins

If Cowork is not working with a connected app, the task usually fails at the step where it calls that service. Check these first:

• Connector not signed in. Installing a plugin does not connect its services. Open the plugin's Connectors tab and connect each one. Our connectors page explains how.
• Local MCP server on the web. Plugins and connectors that use a local MCP server only work in the desktop app.
• Expired authorization. Disconnect and reconnect the service, then start a new task.
• Admin restrictions. On Team and Enterprise, admins control which Cowork plugins and connectors members can use.

Cowork not working on long tasks

Sometimes Cowork is not working in the sense that a task stalls, slows down, or stops halfway. Cowork tasks take many steps, so they use more of your plan's usage than a normal chat. If a task stops partway, check whether you hit a usage limit. The Auto permission mode also uses more of your limit because it adds safety checks. To make long jobs more reliable:

• Split one huge request into smaller tasks with clear outputs.
• Point Cowork at a smaller folder instead of your whole drive.
• Use scheduled tasks for recurring work instead of one very long session.
• Close heavy apps if your computer is short on memory during local sessions.

Still stuck? Collect a diagnostic report

If Cowork is still not working, open Help → Troubleshooting → Generate Diagnostic Report in Claude Desktop and click Export to file. The zip includes configuration state, app logs, and environment details, but no conversation content. Send it to Claude support, or search the public issue tracker on GitHub, where many Cowork errors are already documented with workarounds.

Frequently asked questions