claude-code - 💡(How to fix) Fix [BUG] Cowork: "Virtualization not available" — VM service not responding, no logs generated (Windows 11 Pro) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47950Fetched 2026-04-15 06:37:42
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Timeline (top)
labeled ×3commented ×2cross-referenced ×1

Error Message

Cowork fails to start with the error: "Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service is not responding. Restart your computer to fix the issue."

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Environment

  • OS: Windows 11 Pro
  • Claude Desktop version: 1.2278.0.0
  • Installation type: Microsoft Store (MSIX package)

What's Wrong?

Cowork fails to start with the error: "Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service is not responding. Restart your computer to fix the issue."

Restarting does not fix the issue. Reinstalling Claude Desktop does not fix the issue.

Prerequisites verified (all met)

  • Hyper-V: Enabled
  • VirtualMachinePlatform: Enabled
  • HypervisorPlatform: Enabled
  • vmms service: Running (Automatic)
  • HvHost service: Running (Manual, started manually)
  • CoworkVMService: Running
  • hcsdiag list: returns empty — VM never starts

Troubleshooting attempted

  1. Restarted PC multiple times
  2. Re-enabled all Hyper-V features via PowerShell (Enable-WindowsOptionalFeature)
  3. Full clean uninstall + reinstall of Claude Desktop (including manual removal of all AppData folders)
  4. Manually started HvHost and CoworkVMService
  5. Reinstalled workspace from within Cowork UI

None of the above resolved the issue.

Additional observations

  • After a clean reinstall, no logs are generated in %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\ — the folder doesn't even exist
  • vm_bundles and claude-code-vm directories are never created
  • Cowork appears to fail before even attempting to initialize the VM

Expected behavior Cowork should start the VM and make the workspace available.

Actual behavior Cowork immediately shows "Virtualization is not available" without generating any diagnostic logs.

What Should Happen?

<img width="1190" height="686" alt="Image" src="https://github.com/user-attachments/assets/8d0d8624-12e5-441e-b9ad-877995f1d17d" />

Error Messages/Logs

Steps to Reproduce

Cowork immediately shows "Virtualization is not available" without generating any diagnostic logs.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.2278.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="1190" height="686" alt="Image" src="https://github.com/user-attachments/assets/ecfa4e37-f4ca-4969-bfda-6d69ab4e919f" />

extent analysis

TL;DR

The issue might be related to the virtualization service not responding, and a potential fix could involve checking the Windows features and services related to Hyper-V and Virtual Machine Platform.

Guidance

  • Verify that all required Windows features for Hyper-V and Virtual Machine Platform are enabled, including Hyper-V, VirtualMachinePlatform, and HypervisorPlatform.
  • Check the status of the vmms, HvHost, and CoworkVMService services to ensure they are running as expected.
  • Consider using the hcsdiag tool to troubleshoot issues with the Hyper-V container service.
  • Since reinstalling Claude Desktop and restarting the PC did not resolve the issue, it may be helpful to investigate further into the system's virtualization settings and services.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to system configuration and services.

Notes

The lack of diagnostic logs and the fact that the vm_bundles and claude-code-vm directories are never created suggest that the issue might be occurring early in the startup process. Further investigation into the system's virtualization settings and services may be necessary to resolve the issue.

Recommendation

Apply workaround: Since the issue is not clearly related to a specific version of Claude Code, and reinstalling the latest version did not resolve the issue, it may be helpful to try troubleshooting the system's virtualization settings and services as a workaround.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork: "Virtualization not available" — VM service not responding, no logs generated (Windows 11 Pro) [2 comments, 3 participants]