[BUG] Cowork "Virtualization is not available" on Windows 10 Pro — logs and vm_bundles folder never created

Resolved 💬 5 comments Opened Mar 11, 2026 by achim-warbruck Closed Apr 11, 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?

What's Wrong?
Cowork shows "Virtualization is not available — Claude's workspace requires Hyper-V, but the virtualization service isn't responding" on Windows 10 Pro. The VM never initializes.

Environment:

  • OS: Windows 10 Pro x64
  • Claude Desktop: latest version

Verification Steps Completed:
| Check | Result |
|---|---|
| Microsoft-Hyper-V | ✅ Enabled (was disabled, enabled via PowerShell) |
| CoworkVMService | ✅ Running |
| vmcompute service | ✅ Running |
| %APPDATA%\Claude\vm_bundles | ❌ Does not exist |
| %APPDATA%\Claude\logs | ❌ Does not exist |

Expected behavior:
Cowork detects Hyper-V and launches the workspace VM.

Actual behavior:
Cowork shows the error immediately. No logs or VM bundles are ever created, meaning the VM never attempts to start.

What Should Happen?

Cowork detects Hyper-V and launches the workspace VM.

Error Messages/Logs

Steps to Reproduce

Cowork shows the error immediately. No logs or VM bundles are ever created, meaning the VM never attempts to start.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

latest

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗