Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork "Virtualization is not available" on Windows 11 Pro 25H2 — VM never initializes, %APPDATA%\Claude folder never created [3 comments, 2 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#47892•Fetched 2026-04-15 06:39:20
View on GitHub
Comments
3
Participants
2
Timeline
10
Reactions
0
Author
andy-bsbandy-bsb
Participants
andy-bsbandy-bsbgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×3cross-referenced ×2closed ×1

Error Message

Cowork permanently shows the virtualization error. The VM never initializes and no logs or AppData folder are ever created.

Error Messages/Logs

  1. Observe "Virtualization is not available" error — VM never starts, %APPDATA%\Claude folder is never created
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?

What's Wrong?

Cowork tab shows "Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding. Restart your computer to resolve this." Restarting does not resolve the issue. The %APPDATA%\Claude folder is never created, meaning the VM never attempts to initialize.

What Should Happen?

System Info

CheckResult
OSWindows 11 Pro, Version 25H2, OS Build 26200.8037
Claude Desktopv1.2278.0.0
CoworkVMService✅ Running
bcdedit hypervisorlaunchtype✅ Set to Auto
%APPDATA%\Claude folder❌ Does not exist — VM never initializes
Logs at %APPDATA%\Claude\logs\cowork_vm_node.log❌ Does not exist

Expected Behavior

Cowork should detect that virtualization is available and successfully initialize the VM workspace.

Actual Behavior

Cowork permanently shows the virtualization error. The VM never initializes and no logs or AppData folder are ever created.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

  1. Install Claude Desktop v1.2278.0.0 on Windows 11 Pro 25H2
  2. Confirm CoworkVMService is Running
  3. Run bcdedit /set hypervisorlaunchtype auto and restart
  4. Open Claude Desktop and navigate to the Cowork tab
  5. Observe "Virtualization is not available" error — VM never starts, %APPDATA%\Claude folder is never created

Attempted Fixes (none resolved the issue)

  • Restarted computer
  • Ran Claude Desktop as Administrator
  • Ran bcdedit /set hypervisorlaunchtype auto
  • Confirmed CoworkVMService is Running
  • Full uninstall, AppData cleanup, fresh reinstall from claude.ai/download

This appears to be the same issue reported in #27316, #27420, #29887, #32004, #37265, #42227, #45446, #45715. Regular chat in Claude Desktop works fine — only Cowork is affected.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

claude 2.1.107 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This appears to be the same issue reported in #27316, #27420, #29887, #32004, #37265, #42227, #45446, #45715. Regular chat in Claude Desktop works fine — only Cowork is affected.

extent analysis

TL;DR

The issue might be resolved by investigating the virtualization settings and service status, considering the error message and the fact that the %APPDATA%\Claude folder is never created.

Guidance

  • Verify that the virtualization service is properly enabled in the BIOS settings, as the bcdedit /set hypervisorlaunchtype auto command only sets the hypervisor launch type to auto but does not guarantee that virtualization is enabled in the BIOS.
  • Check the event logs for any errors related to the CoworkVMService to understand why the VM never initializes.
  • Consider comparing the system configuration with the requirements for running Claude Desktop's Cowork feature, ensuring all dependencies and prerequisites are met.
  • Since the issue seems to be similar to previously reported issues (#27316, #27420, etc.), reviewing the discussions and potential workarounds in those issues might provide insights.

Example

No specific code snippet can be provided without more details on the implementation, but checking the service status and event logs could be done using PowerShell commands like Get-Service CoworkVMService and Get-EventLog -LogName Application -Source CoworkVMService.

Notes

The fact that regular chat in Claude Desktop works fine suggests that the issue is specific to the Cowork feature and its dependency on virtualization. The lack of creation of the %APPDATA%\Claude folder and logs indicates a failure early in the initialization process.

Recommendation

Apply workaround: Given the similarity to previously reported issues and the lack of a clear resolution, applying workarounds or fixes suggested in those issues (e.g., #27316, #27420) might help resolve the problem, alongside ensuring that virtualization is properly enabled and configured.

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…
#api#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING