[BUG] Cowork stuck at end of loading bar — VM never finishes initializing (Windows 11 Pro)

Status Fixed / completed
Maintainer reply None cached
Activity 3 comments · opened Mar 20, 2026 · closed Mar 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Related issues: Similar to #27801 and #26646 but different symptom — VM starts but never completes initialization, no API errors, connectivity confirmed OK.

System info:
OS: Windows 11 Pro, build 26200
Device: Lenovo ThinkPad L15 Gen 2 (20X4S27300)
CPU: Intel Core i5-1135G7 @ 2.40GHz (x64)
Claude Desktop: latest version (installed March 2026)

What's wrong:
Cowork loads to the very end of the setup progress bar ("Configurando el espacio de trabajo de Claude") and never completes. Stays there indefinitely (tested 15+ minutes). Regular Chat works fine.
Troubleshooting already done:

  • Uninstalled and reinstalled Claude Desktop multiple times
  • Rebooted multiple times
  • HypervisorPlatform was Disabled — enabled it via PowerShell, rebooted, issue persists
  • Get-HnsNetwork now returns a Default Switch (172.27.176.0/20) after enabling HypervisorPlatform
  • Test-NetConnection api.anthropic.com -Port 443 → TcpTestSucceeded: True
  • cowork-svc process visible and running in Task Manager
  • No ARM processor, no Windows Home edition

What Should Happen?

Expected behavior: Cowork workspace finishes setting up and accepts tasks.

Error Messages/Logs

Steps to Reproduce

  • Open Claude Desktop on Windows 11 Pro
  • Click the "Cowork" tab
  • Wait for workspace setup to complete
  • Progress bar reaches the very end but never finishes — hangs indefinitely (tested 15+ minutes)

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

1.1.7714.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="880" height="598" alt="Image" src="https://github.com/user-attachments/assets/87220392-9b5f-4c0e-b134-85c59ff024fe" />

View original on GitHub ↗

3 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/36392
  2. https://github.com/anthropics/claude-code/issues/32200
  3. https://github.com/anthropics/claude-code/issues/36590

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

rnavarro-bot · 6 months ago

Solved (Windows 11 Pro, ThinkPad L15 Gen 2, Intel i5-1135G7)
Root causes found (multiple):

  1. Intel VT-x disabled in BIOS — (Get-CimInstance Win32_ComputerSystem).HypervisorPresent returned False. Fixed by entering BIOS (F1 on ThinkPad) → Security → Virtualization → Enable Intel Virtualization Technology.
  1. VHDX path mismatch — app looks for vm_bundles in %APPDATA%\Claude\vm_bundles but files are in %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles. Fixed with symlink:
powershell
New-Item -ItemType Directory -Force -Path "$env:APPDATA\Claude"
New-Item -ItemType SymbolicLink -Path "$env:APPDATA\Claude\vm_bundles" -Target "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles"
  1. CoworkVMService not starting automatically — needed to start manually:

powershell
Start-Service CoworkVMService

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.