The Complete Windows Guide to Claude Desktop Cowork

While Anthropic's Claude Desktop app was initially highly optimized for macOS, Windows is now a fully supported first-class citizen for Claude Cowork. However, configuring local paths, managing shell commands in PowerShell, and working with WSL (Windows Subsystem for Linux) can introduce several Windows-specific friction points.

This guide provides a comprehensive setup walk-through, troubleshooting tips, and integration patterns for Windows power users.

Table of Contents

  1. Locating the Windows Config File
  2. PowerShell vs. CMD: Environment Configuration
  3. Windows-Specific Permission Challenges
  4. WSL (Windows Subsystem for Linux) Integration
  5. Frequently Asked Questions for Windows Users

Locating the Windows Config File

On macOS, your Claude Desktop config is stored in your Library folder. On Windows, it is located in the user's roaming AppData directory.

The Config File Path

Your claude_desktop_config.json must be created or edited at:

%APPDATA%\Claude\claude_desktop_config.json

Quick Access via Explorer or Terminal

To edit this file, you can quickly open it using the following methods:

  • Via Windows Run (Win + R): Copy and paste: notepad %APPDATA%\Claude\claude_desktop_config.json and press Enter.
  • Via PowerShell: 
    notepad "$env:APPDATA\Claude\claude_desktop_config.json"

[!NOTE] If the Claude folder or claude_desktop_config.json file does not exist, you can manually create them in your %APPDATA% folder. Our Config Generator is a great tool to bootstrap this file.

PowerShell vs. CMD: Environment Configuration

When Claude Cowork runs local tools or MCP (Model Context Protocol) servers on Windows, it spawns terminal sessions.

By default, Claude uses the Windows shell environment, which inherits system environment variables. However, node package managers (npx, npm) and python processes must be mapped properly in your environment variables path.

1. The Global Node/NPM Path Issue

If Claude fails to execute an MCP server with exit code 127 (Command Not Found), it usually means Claude cannot resolve your node or npx path.

  • Fix: Ensure your Node.js path is added to your User Environment Variables.
  • Verify by running where.exe node in command prompt. The output path (e.g., C:\Program Files\nodejs\node.exe) must match your system PATH.

2. Passing Environment Variables in JSON

When defining tools, Windows often requires explicit variables such as USERPROFILE or PATH passed through the config's env block.

{
  "mcpServers": {
    "my-local-tool": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-everything"],
      "env": {
        "PATH": "C:\\Program Files\\nodejs\\;C:\\Windows\\system32",
        "USERPROFILE": "C:\\Users\\YourUsername"
      }
    }
  }
}

Windows-Specific Permission Challenges

Because Cowork operates locally, Windows Defender or your local User Account Control (UAC) might occasionally block file manipulation or script execution.

Windows Defender SmartScreen

When Claude Desktop downloads node modules or writes scripts in the sandbox, Windows Defender might flag them as untrusted files.

  • Recommended Action: Create a dedicated workspace directory for Claude (e.g., C:\Users\YourUsername\ClaudeWork). Scope your folder access permissions in Claude Desktop strictly to this directory to avoid full drive scans triggers.
  • Execution Policies: If your workflow runs local PowerShell scripts, ensure your system policy allows it by running: 
    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

WSL (Windows Subsystem for Linux) Integration

Many developers prefer to run their codebases and tools inside WSL. Since Claude Desktop runs as a native Windows application, it needs helper settings to access WSL directories.

Accessing WSL Files

To grant Claude access to a folder inside WSL, use the network path:

\\wsl$\Ubuntu\home\username\projects\my-project

When Claude asks to select a folder in the graphical user interface, paste the \\wsl$ address into the Windows File Explorer search bar.

Executing Commands in WSL

If your MCP configurations require WSL commands, wrap them using the wsl.exe launcher:

{
  "mcpServers": {
    "wsl-git": {
      "command": "wsl.exe",
      "args": ["git", "status"]
    }
  }
}

FAQ

Does Windows support the "Computer Use" feature?

Yes. The latest Claude Desktop Cowork updates support screen interaction on Windows. However, you must grant administrative or standard app focus permissions if Windows security dialogs intercept focus.

Why does the terminal pop up briefly during tasks?

Claude Desktop launches sub-processes to run script files and command utilities. This is expected behavior on Windows. Ensure your script executions are headless to prevent focus stealing.

Last updated: June 15, 2026

This article is part of CoworkHow.com, an independent resource for Claude Cowork users. We are not affiliated with Anthropic.