A step-by-step guide to setting up Claude Desktop, Desktop Commander, and Claude Code on Windows — plus ready-to-use prompts you can copy and paste.
Setting up Claude Desktop, Desktop Commander, and Claude Code on Windows
This guide uses Claude Desktop + Desktop Commander as a "bootstrap" to help install Claude Code. You get two powerful tools:
Using Desktop Commander to install prerequisites reduces manual troubleshooting and lets Claude help you through any errors.
Sign up for a Claude account if you don't already have one.
Link: https://claude.ai
You'll need either:
Claude Desktop is the chat application that runs on your computer and supports MCP (Model Context Protocol) extensions.
Download: https://claude.ai/download
Installation steps:
Desktop Commander is an MCP server that gives Claude Desktop access to your terminal and file system. This turns Claude into a powerful automation assistant.
Smithery (Recommended): https://smithery.ai/server/@wonderwhy-er/desktop-commander
Alternative — Manual Installation:
npx @wonderwhy-er/desktop-commander@latest setupOnce installed, Claude Desktop can:
Now use Claude Desktop with Desktop Commander to install the tools Claude Code needs. Open Claude Desktop and ask it to help you install:
Link: https://git-scm.com/downloads/win
Git Bash is required for Claude Code on Windows. Ask Claude:
"Install Git for Windows using winget"
Or manually: winget install --id Git.Git
Link: https://nodejs.org/en/download
Node.js provides a more stable environment for Claude Code. Ask Claude:
"Install Node.js LTS using winget"
Or manually: winget install --id OpenJS.NodeJS.LTS
Link: https://www.python.org/downloads/
Python enables data analysis capabilities in Claude Code. Ask Claude:
"Install Python using winget"
Or manually: winget install --id Python.Python.3.12
Important: After installing these tools, close and reopen your terminal to refresh your PATH.
Running as Administrator reduces UAC (User Account Control) prompts when Claude Code needs to modify files or install packages.
With prerequisites installed, you can now install Claude Code. Choose one method:
In PowerShell (as Administrator):
irm https://claude.ai/install.ps1 | iexIn Git Bash (as Administrator):
npm install -g @anthropic-ai/claude-codeIn PowerShell:
winget install --id Anthropic.ClaudeCodeAfter installation, authenticate Claude Code with your account:
claude and press EnterConfirm everything is working:
node --version
python --version
git --version
claude --versionclaude doctorNavigate to a project folder and run:
claudeThen ask Claude Code something simple like:
"What files are in this directory?"
node --versionCLAUDE_CODE_GIT_BASH_PATH=C:\Program Files\Git\bin\bash.exeNow that you have both tools installed:
Check out the Claude Code Prompts page for ready-to-use prompts that automate common tasks.
Click a card to expand it. Each prompt was built from hands-on sessions and tested on production systems.
Perform a broad system performance configuration sweep on this Windows machine. Follow this process:
PHASE 1 - DIAGNOSE:
Scan and report on all of the following in parallel where possible:
- System info: OS, CPU, RAM, disk type/health, uptime
- Current resource usage: top 15 processes by memory, CPU load
- Power plan: active scheme, processor min/max throttle (AC and DC)
- Startup programs: all entries in HKCU and HKLM Run registry keys
- Scheduled tasks: all non-Microsoft tasks, focusing on OEM bloatware (Lenovo, Dell, HP, etc.)
- Services: count of automatic services running vs stopped
- Windows Defender: current exclusion paths
- Network: active adapters, DNS configuration
- Visual effects setting
- Sleep/hibernate settings: sleep timers, hibernate timers, lid close actions (AC and DC)
- Modern Standby: check if system uses S0 Low Power Idle vs traditional S3
- Wake-armed devices that can wake the computer
Present findings as a structured report with a prioritized list of recommended changes ranked by impact.
PHASE 2 - FIX (one at a time, ask permission before each):
For each recommendation, explain what it does and ask for permission before proceeding. After each fix, verify the change took effect and report results. Common fixes include:
1. Defender exclusions - Find development/build directories and add them as exclusions to reduce MsMpEng CPU usage. Ask the user where their project files are.
2. OEM scheduled tasks - Categorize all OEM tasks into "disable" (telemetry, heartbeats, ads, bloatware) vs "keep" (driver updates, battery health, hardware monitoring). Present both lists for approval before disabling.
3. Startup cleanup - Identify unnecessary startup entries (OEM updaters, browser preloaders, etc.) and remove them from the registry. Keep functional items the user relies on.
4. Power plan optimization - Instead of switching plans, modify the current plan: set AC processor min state to 100% for full performance when plugged in, keep DC settings conservative for battery life.
5. Sleep/hibernate fixes for laptops - If the system uses Modern Standby (S0 Low Power Idle), check and fix:
- Set lid close on battery (DC) to Hibernate
- Enable hibernate on battery after 30 minutes as a safety net
- Keep lid close on AC as Sleep so docked wake-from-keyboard still works
- Unhide the lid close setting if Windows has hidden it on Modern Standby systems
6. DNS optimization - ONLY if the machine is NOT domain-joined or Azure AD joined. Skip this on corporate machines to avoid breaking Conditional Access, Tailscale MagicDNS, or M365 service discovery.
IMPORTANT GUIDELINES:
- Always diagnose before fixing -- never make blind changes
- Ask the user before each fix category
- Verify every change after applying it
- Use elevated PowerShell (Start-Process -Verb RunAs) for changes that require admin
- Clean up any temporary scripts or files created during the process
- Present a final summary table of all changes made