Claude Cowork for Windows: How to Download/Install the AI Assistant

Claude Cowork is Anthropic’s agentic workspace for handing off multi-step tasks to Claude — things like organizing a messy folder of files, synthesizing research from a stack of PDFs, or turning rough notes into a polished document. Unlike a standard chat window, Cowork can reach into your local files, use a browser, and even interact with your screen, which means it needs a bit more than just an internet connection to run. On Windows, that extra layer comes from the Claude Desktop app and a lightweight virtualization component that keeps Cowork’s actions sandboxed and safe.

If you’ve used Claude in a browser before, the good news is that Cowork isn’t a separate product you install on its own. It lives inside Claude Desktop, and once that app is installed and you’re signed into a paid plan, Cowork simply appears as an option alongside your regular chat. The setup process is short, but there are a handful of Windows-specific details — administrator rights, a virtualization feature, and architecture (x64 vs. ARM64) — that are worth understanding before you start, especially if the installation doesn’t go smoothly on the first try.

This guide walks through what Cowork actually needs to run on Windows, four practical ways to get it installed depending on your situation (a solo user, a managed work laptop, or someone troubleshooting a stalled setup), and answers to the questions people run into most often.

What You Need Before You Install

A few things determine whether Cowork will work smoothly once Claude Desktop is on your machine:

• A paid Claude plan. Cowork is available on Pro, Max, Team, and Enterprise plans. A free account lets you install Claude Desktop and chat, but the Cowork option won’t appear in the message box.
• Windows 10 or Windows 11 (64-bit). Both are supported, and Cowork works the same way on Home and Pro editions.
• The right processor architecture. Most Windows PCs use a standard x64 processor. A smaller number of newer machines — Copilot+ PCs, Surface Pro X and similar ARM-based devices — use ARM64 instead. Windows offers separate installers for each, so it’s worth checking which one you have. You can find this under Settings > System > About, where “System type” will list either an x64-based or ARM-based processor.
• Administrator access. Installing Claude Desktop with full Cowork support requires admin rights on the machine, because the installer needs to enable a Windows virtualization feature in the background. If you’re on a locked-down work laptop without admin access, Claude Desktop itself may still install, but Cowork’s desktop capabilities won’t be available until an administrator enables that feature.
• The Virtual Machine Platform feature. Cowork’s file and browser access on Windows runs through an isolated environment that depends on this built-in Windows feature. It’s usually enabled automatically during setup, but it’s the most common thing to check if Cowork doesn’t start afterward.

With those basics in mind, here are four ways to actually get Cowork running, depending on your setup.

Method 1: Standard Installation for a Personal Computer

This is the path most individual users will take, and it’s the simplest.

1. Go to the official download page. Visit claude.com/download from your browser. Avoid third-party download sites — Claude Desktop should only ever come from Anthropic’s own domain.
2. Choose the correct Windows build. You’ll typically see a standard Windows option alongside a Windows (ARM64) option for Arm-based devices. Pick the one that matches the processor type you checked earlier.
3. Run the installer. Once the file finishes downloading, double-click it. You’ll likely see a Windows User Account Control (UAC) prompt asking for permission to make changes to your device — this is expected, since the installer needs to register the background service that powers Cowork’s sandbox.
4. Sign in. After installation completes, open Claude Desktop and sign in with your existing Claude account, or create one if you’re new. If Cowork is included in your plan, you’ll see it appear as an option next to “Chat” in the message box.
5. Grant folder access for your first task. The first time you ask Cowork to do something involving your local files, it will ask you to choose and approve a working folder. Nothing outside that folder is accessible unless you explicitly widen the permission later.
6. Let the one-time setup finish. On first use, Cowork downloads a workspace image that creates its isolated environment. This only happens once; after that, sessions start much faster.

For most home users on a personal machine with admin rights, this is the entire process, and it typically takes only a few minutes beyond the download itself.

Method 2: Verifying and Enabling Virtualization Manually

Occasionally, Claude Desktop installs fine, but Cowork won’t start, or it reports that a required service is missing. This usually comes down to the Virtual Machine Platform feature not being active, and it’s straightforward to check and fix yourself.

1. Open PowerShell as an administrator. Right-click the Start button and choose “Windows PowerShell (Admin)” or “Terminal (Admin).”
2. Check whether the feature is enabled. Run:

   Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

If the output shows it’s disabled, that’s the likely cause of the problem. 3. Enable it if needed. Run:

   Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

You’ll be prompted to restart your computer for the change to take effect. 4. Confirm the supporting services are running. After restarting, you can check the status of the services Cowork depends on with:

   Get-Service vmcompute, hns

If either service is missing or stopped, it usually means the Virtual Machine Platform stack isn’t fully registered, and reinstalling Claude Desktop with admin rights typically resolves it. 5. Reopen Claude Desktop. With the feature enabled and the services running, the Cowork tab should now function normally.

This method is worth trying any time Cowork appears in the app but won’t launch, since it addresses the single most common root cause on Windows.

Method 3: Deploying Cowork Across an Organization (IT Admins)

If you’re setting up Claude Desktop for a team rather than a single machine, Anthropic supports centralized deployment so individual users don’t have to run the installer themselves.

1. Use the MSIX package for silent installs. Rather than the interactive installer, IT administrators can deploy Claude Desktop as an MSIX package through tools like Microsoft Intune, SCCM, or Group Policy.
2. Deploy machine-wide, not per-user. A per-user installation (using a command like Add-AppxPackage) can complete successfully but fail to register the Cowork virtualization service properly. To ensure Cowork works for every user on the device, deploy with a provisioning approach such as Add-AppxProvisionedPackage, which registers the service at the machine level.
3. Pre-enable the Virtual Machine Platform fleet-wide. Rather than relying on each install to trigger this, administrators can push the same Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform command through their endpoint management tooling ahead of time.
4. Control Cowork access at the organization level. Team and Enterprise owners can also manage whether Cowork is available at all, along with settings like the built-in browser and automatic approval modes, from Organization Settings > Cowork in the admin console — independent of whether the app itself is installed.
5. Manage plugins centrally, if relevant. Organizations can also curate which Cowork plugins are available, installed by default, or hidden entirely, giving admins control over what capabilities show up for their teams.

This approach is the more reliable option in managed environments, since it avoids the permissions issues that can come up when individual employees try to install Claude Desktop themselves without admin rights.

Method 4: Fixing a Stalled or Incomplete Installation

Sometimes the installer runs, but something along the way doesn’t complete correctly. A few checks cover most of the issues people run into.

1. Confirm you’re on the latest version. Cowork requires a current build of Claude Desktop, so if you installed the app some time ago, check for updates before troubleshooting further.
2. Watch for storage path errors. If you see an error referencing a “cross-device link,” it usually means Cowork’s workspace image is pointing at a drive other than your main system drive. Resetting the storage location to your C: drive in Claude Desktop’s settings, then reinstalling, typically resolves this.
3. Check for missing HCS services. An error mentioning missing services like HNS, vmcompute, or vfpext points back to the Virtual Machine Platform not being fully registered — see Method 2 above for the fix.
4. Reinstall rather than repair. If Cowork was working before but suddenly isn’t, a clean reinstall from claude.com/download (rather than trying to patch the existing install) is usually the fastest path back to a working state, since the installer re-registers the background service automatically.
5. Rule out antivirus interference. Some antivirus tools quarantine the installer or block the background service from registering. If installation stalls with no clear error, temporarily checking your antivirus’s quarantine list is worth doing before assuming something is broken on Anthropic’s end.

Conclusion

Getting Claude Cowork running on Windows really comes down to two things: having Claude Desktop installed with a paid plan, and making sure the underlying Virtual Machine Platform feature is enabled so Cowork’s sandboxed environment can run. For most people on a personal computer with administrator access, that’s a five-minute process — download, install, sign in, and grant folder access to your first task. Where it gets more involved is in managed environments, where IT teams need to deploy the app machine-wide rather than per-user, or in troubleshooting scenarios where a missing service or a misconfigured storage path is quietly blocking Cowork from starting.

Once it’s up and running, Cowork works the same way whether you’re on Windows Home or Pro, and it opens up genuinely different territory from a normal chat: reading and writing files directly in a folder you designate, working across a browser, and handling long-running tasks like research synthesis or document generation without you needing to babysit each step. If something isn’t working, the fixes above cover the vast majority of cases — and if none of them apply, Anthropic’s own Help Center has more detailed troubleshooting for edge cases specific to your setup.

FAQ

1. Do I need a paid Claude plan to use Cowork on Windows? Yes. Cowork is available on Pro, Max, Team, and Enterprise plans. A free account can install and use Claude Desktop for chat, but the Cowork option won’t be available in the message box until you upgrade.

2. Why don’t I see the Cowork option after installing Claude Desktop? This is usually one of two things: you’re on a free plan, or you installed without administrator rights, which prevents the Cowork virtualization service from registering. Reinstalling with admin privileges, or having your IT administrator deploy it machine-wide, typically resolves this.

3. Does Cowork work the same on Windows as it does on macOS? Yes, in terms of features. Cowork reached general availability on both Windows and macOS after starting as a macOS-only beta, and the two platforms don’t differ in what Cowork can do — file access, browser use, and computer use are all supported on Windows through the Claude Desktop app.

4. What if Cowork says virtualization isn’t available on my machine? Check that the Virtual Machine Platform feature is enabled in Windows by running Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform in an administrator PowerShell window. If it’s disabled, enabling it and restarting your computer usually fixes the issue. On rare occasions, this also requires enabling hardware virtualization in your computer’s BIOS or UEFI settings if it’s turned off at the firmware level.