How to Set Up Claude Cowork on Windows: Installation and Configuration

Three open issues on Anthropic's GitHub repository, filed between February and May 2026, each report the same failure: Claude Cowork refuses to start on Windows Home edition. The root cause is that Cowork's sandbox depends on Hyper-V, which Microsoft excludes from Home SKUs entirely. Anthropic's official getting-started article still does not call out this requirement prominently, leaving users to discover it after purchasing a Claude Pro subscription.

Anthropic launched Claude Cowork on Windows on February 10, 2026, one month after the macOS release. The Windows build has full feature parity with macOS: the same task modes, the same permission model, and the same plugin ecosystem. But the installation path diverges in ways that macOS users never encounter. Windows has two processor architectures in active use (x64 and ARM64), an OS edition that silently blocks the core virtualization layer, and security software that can quarantine the VM service before Cowork runs its first task.

This guide covers the gaps. You will check your architecture, verify your Windows edition, install the app, configure file permissions, handle Windows Defender, and set up a storage workflow for your Cowork output.

Before downloading anything, verify three things: your Windows edition, your processor architecture, and your virtualization support.

Windows Edition Cowork needs full Hyper-V, not the stripped-down "Virtual Machine Platform" that ships with Windows Home. Only Windows Pro, Enterprise, and Education include the vmms (Virtual Machine Management) service that Cowork depends on.

To check your edition, press Win+I to open Settings, then go to System and About. Look for the "Edition" line. If it says "Windows 11 Home" or "Windows 10 Home," you need to upgrade to Pro before Cowork will work. Microsoft sells the upgrade for $99 through the Microsoft Store, or you can enter a Pro product key in Settings under System, then Activation.

To confirm that Hyper-V is available, open PowerShell as administrator and run:

Get-Service vmms

If the command returns a running or stopped service, your edition supports Hyper-V. If it returns an error, you are on Home.

Processor Architecture

Anthropic provides separate installers and readiness checkers for x64 (Intel and AMD) and ARM64 (Qualcomm Snapdragon, Microsoft SQ series). Most Windows desktops and laptops use x64. Surface Pro X, Surface Pro 9 with 5G, and newer Copilot+ PCs use ARM64.

To check which architecture you are running, open Settings, go to System, then About, and look for "System type." It will say either "64-bit operating system, x64-based processor" or "64-bit operating system, ARM-based processor."

Hardware and Software Minimums

• Windows 10 version 1909 or later, or Windows 11
• 8 GB RAM minimum, 16 GB recommended for larger tasks
• About 10 GB of free disk space for the app and its VM sandbox
• Active internet connection throughout every session
• A paid Claude plan: Pro ($20/month), Max ($100 or $200/month), Team ($25/seat/month), or Enterprise

The installation involves four steps: downloading the readiness checker, running it, installing Claude Desktop, and verifying the VM service.

Step 1: Download and Run the Readiness Checker

Go to the Claude Cowork support page and download the readiness check tool for your architecture. There are separate downloads for Windows x64 and Windows ARM64. Pick the one matching your processor.

Run the downloaded executable. It checks your OS version, virtualization status, and Hyper-V availability. If everything passes, you see: "This computer is ready for Cowork."

One known issue: the readiness checker has been reported to pass incorrectly on some Windows Home systems by misidentifying the OS version. If you are on Windows Home and the checker says you are ready, run the Get-Service vmms command from the previous section to verify manually.

Step 2: Enable Virtualization Features

If the readiness check fails on virtualization, you may need to enable it in two places.

First, check your BIOS/UEFI settings. Restart your computer and enter BIOS (usually by pressing F2, F12, or Delete during boot). Look for a setting called "Intel Virtualization Technology" (VT-x) or "AMD SVM Mode" and enable it.

Second, enable Hyper-V in Windows. Open Control Panel, go to Programs, then "Turn Windows features on or off." Check "Hyper-V" (both the Management Tools and Platform checkboxes). Click OK and restart your computer.

Step 3: Install Claude Desktop

Visit claude.com/download and download the Windows installer. The package is an MSIX file. Double-click it to install. Administrator privileges are required because the installer registers CoworkVMService, the background service that runs the Cowork sandbox.

If you already have Claude Desktop installed, check for updates first. Cowork requires the latest version of the desktop app.

Step 4: Verify the VM Service

After installation, confirm the VM service is running. Open PowerShell and run:

Get-Service "Claude VM Service"

The status should show "Running." If it shows "Stopped," start it with:

Start-Service "Claude VM Service"

If the service does not exist at all, reinstall Claude Desktop from claude.com/download. The installer should register the service automatically.

Troubleshooting: EXDEV Error

If you see "EXDEV: cross-device link not permitted" during setup, the storage path is pointing to a drive other than C:. Cowork's VM sandbox must live on your system drive. Reset the storage path to C:\ in Claude Desktop settings, uninstall, and reinstall.

Keep Cowork output searchable and shareable across your team

Upload Claude Cowork deliverables to a Fast.io workspace. Files are auto-indexed for AI search, shareable through branded links, and accessible through the MCP server. Starts with a 14-day free trial.

Start 14-Day Trial

When you first click the Cowork tab in Claude Desktop, the app asks you to approve file access. Cowork operates inside a VM sandbox and can only reach files you explicitly grant access to.

Choosing a Working Folder

Set up a dedicated working folder rather than granting access to your entire user profile. Something like C:\Users\YourName\CoworkFiles keeps your personal documents, credentials, and browser data out of reach.

Your working folder must be on your system drive (C:) and within your user profile directory. Network drives, external USB drives, and secondary partitions may not mount correctly inside the VM sandbox. If you need to process files from another location, copy them into your working folder first.

Permission Modes

Cowork offers two permission modes that control how much autonomy Claude gets during a task.

Standard mode (default): Claude pauses between steps and asks for your approval before each action. You see exactly what Claude plans to do, whether that is reading a file, writing a new document, or deleting something. This is the right mode when you are learning the tool or working with sensitive files.

Act Without Asking mode: Claude runs continuously without pausing for approval between steps. This is faster for bulk tasks like organizing a large folder or processing dozens of documents, but you lose the ability to review each action before it happens.

One permission is never skippable regardless of mode: Cowork always asks before permanently deleting any file. Even in Act Without Asking mode, you see a permission prompt and must click "Allow" before any deletion proceeds.

What Claude Can and Cannot Access

Inside its sandbox, Claude can read file contents, create new files, rename and move files, edit documents, and open installed applications with your permission. It cannot access files outside your designated working folder, modify system files, install software, or make network requests to arbitrary endpoints. Browser access is limited to sites you explicitly approve.

Windows Defender and third-party antivirus tools sometimes interfere with Cowork's VM service. The MSIX package is signed by Anthropic, so Defender should not flag the application itself. But the background VM service creates and manages processes that some security tools treat as suspicious.

Windows Defender Exclusions

If Cowork tasks fail or the VM service stops unexpectedly, add exclusions for the Claude Desktop installation directory and the VM service process. Open Windows Security, go to Virus & Threat Protection, click "Manage settings" under Virus & Threat Protection Settings, scroll to Exclusions, and add the Claude Desktop folder (typically under C:\Program Files\Claude or your user's AppData directory).

Enterprise Deployments

For organizations using AppLocker or Windows Defender Application Control (WDAC), the MSIX package is signed but may need an explicit allowlist entry. IT administrators should create a publisher-based rule that trusts the Anthropic signing certificate rather than hash-based rules that break on every update.

Group Policy can push Claude Desktop and enable Hyper-V across managed machines. Anthropic's enterprise deployment documentation covers GPO and Intune deployment paths for organizations rolling out Cowork at scale.

Third-Party Antivirus

If you run antivirus software alongside Defender (Norton, Bitdefender, Kaspersky, or similar), you may need to add exclusions for the Claude VM Service in that tool as well. Look for real-time protection settings and add both the Claude Desktop directory and the CoworkVMService process name to the exclusion list.

Cowork saves everything to your local file system. That works fine for solo use, but creates friction the moment you need to share a deliverable, access results from another machine, or let a teammate review what Claude produced.

Standard cloud storage (Google Drive, Dropbox, OneDrive) solves the access problem but treats files as static objects. You upload a Cowork-generated report and get a shareable link, but the platform does not index the document's content for search or analysis.

Fast.io works differently for teams that combine AI output with human review. When you upload Cowork deliverables to a Fast.io workspace, Intelligence Mode auto-indexes the files for semantic search and AI-powered chat. Your team can ask natural language questions across a batch of Cowork-generated reports without opening each one individually.

The setup is straightforward: create a workspace on Fast.io, drag your Cowork output folder into it, and share access with collaborators through branded Send and Exchange links. Intelligence Mode indexes the files automatically with no configuration needed.

For developers building automated pipelines around Cowork, Fast.io exposes a Model Context Protocol server with Streamable HTTP at /mcp. Agents can read, write, search, and organize files programmatically. Combined with webhooks for change notifications and file locks for concurrent access, this creates a persistent layer where Cowork output is stored, queried, and handed off to reviewers.

Plans start with a 14-day free trial, with workspaces, monthly credits, and storage scaled to each tier. That gives you room to store months of Cowork output while keeping it searchable and shareable.