Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork "Virtualization is not available" on Windows 10 Pro — VM never initializes, no logs created [1 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#50872•Fetched 2026-04-20 12:10:44
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
nrjslovensko-stacknrjslovensko-stack
Participants
github-actions[bot]github-actions[bot]nrjslovensko-stacknrjslovensko-stack
Timeline (top)
labeled ×4commented ×1cross-referenced ×1unlabeled ×1

Error Message

No logs available — the %APPDATA%\Claude\logs folder does not exist at all. The VM never reaches the initialization stage, therefore no log files (including cowork_vm_node.log) are generated despite multiple reinstalls and restarts.

PowerShell diagnostics confirm all prerequisites are met:

  • Get-Service CoworkVMService → Status: Running
  • Get-WindowsOptionalFeature Microsoft-Hyper-V-All → State: Enabled
  • Get-WindowsOptionalFeature HypervisorPlatform → State: Enabled
  • Get-WindowsOptionalFeature VirtualMachinePlatform → State: Enabled

The only anomaly detected:

  • systeminfo | findstr /i "hyper-v" → Error: "Classe non valide" (invalid class) — this may be related to the platform detection bug.

Code Example

No logs available — the %APPDATA%\Claude\logs folder does not exist at all.
The VM never reaches the initialization stage, therefore no log files 
(including cowork_vm_node.log) are generated despite multiple reinstalls 
and restarts.

PowerShell diagnostics confirm all prerequisites are met:
- Get-Service CoworkVMService → Status: Running
- Get-WindowsOptionalFeature Microsoft-Hyper-V-All → State: Enabled
- Get-WindowsOptionalFeature HypervisorPlatform → State: Enabled
- Get-WindowsOptionalFeature VirtualMachinePlatform → State: Enabled

The only anomaly detected:
- systeminfo | findstr /i "hyper-v" → Error: "Classe non valide" 
  (invalid class) — this may be related to the platform detection bug.
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?

Cowork tab shows "Claude's workspace requires the Virtual Machine Platform, but the virtualization service is not responding." Restarting does not fix the issue. The %APPDATA%\Claude\logs folder does not exist — the VM never attempts to initialize.

Environment

  • OS: Windows 10 Pro
  • Claude Desktop: latest version from claude.ai/download (installed as Administrator)
  • Subscription: Pro

Verification Results

CheckResult
CoworkVMService✅ Running
Hyper-V (Microsoft-Hyper-V-All)✅ Enabled
HypervisorPlatform✅ Enabled
VirtualMachinePlatform✅ Enabled
%APPDATA%\Claude\logs folder❌ Does not exist — VM never initializes

Steps Taken

  • Full uninstall of all Claude versions including Claude 1.0
  • Deleted %APPDATA%\Claude and %LOCALAPPDATA%\claude-code-vm residual files
  • Reinstalled Claude Desktop as Administrator
  • Restarted PC multiple times
  • Issue persists after every restart and reinstall

Expected Behavior Cowork should detect that all virtualization features are enabled and successfully start the VM workspace.

Related Issues #27316, #29887, #32004, #38632, #43604, #45715

What Should Happen?

Cowork should detect that all virtualization features are properly enabled (Hyper-V, VirtualMachinePlatform, HypervisorPlatform all Enabled, CoworkVMService Running) and successfully initialize the VM workspace, creating the %APPDATA%\Claude\logs folder and allowing access to the Cowork tab without any error message.

Error Messages/Logs

No logs available — the %APPDATA%\Claude\logs folder does not exist at all.
The VM never reaches the initialization stage, therefore no log files 
(including cowork_vm_node.log) are generated despite multiple reinstalls 
and restarts.

PowerShell diagnostics confirm all prerequisites are met:
- Get-Service CoworkVMService → Status: Running
- Get-WindowsOptionalFeature Microsoft-Hyper-V-All → State: Enabled
- Get-WindowsOptionalFeature HypervisorPlatform → State: Enabled
- Get-WindowsOptionalFeature VirtualMachinePlatform → State: Enabled

The only anomaly detected:
- systeminfo | findstr /i "hyper-v" → Error: "Classe non valide" 
  (invalid class) — this may be related to the platform detection bug.

Steps to Reproduce

  1. Install Windows 10 Pro with Hyper-V, VirtualMachinePlatform and HypervisorPlatform enabled via Windows Features (optionalfeatures)

  2. Download and install latest Claude Desktop from claude.ai/download as Administrator

  3. Launch Claude Desktop and navigate to the Cowork tab

  4. Observe "Virtualization is not available" error message immediately

  5. Restart computer → error persists

  6. Verify CoworkVMService is Running via PowerShell: Get-Service CoworkVMService → Status: Running

  7. Verify all virtualization features are enabled via PowerShell: Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All → Enabled Get-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform → Enabled Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform → Enabled

  8. Check %APPDATA%\Claude\logs → folder does not exist, no logs generated, VM never initializes

  9. Full uninstall of Claude Desktop, delete %APPDATA%\Claude and %LOCALAPPDATA%\claude-code-vm, reinstall as Administrator → same result

  10. Error persists after every restart and reinstall attempt.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

The last

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The issue with Claude's Cowork tab failing to initialize the VM workspace due to a virtualization service not responding may be related to a platform detection bug, and checking the system's Hyper-V configuration and ensuring all virtualization features are correctly enabled could provide a workaround.

Guidance

  • Verify that Hyper-V is properly configured and all its components are enabled, as the error message "Classe non valide" (invalid class) when running systeminfo | findstr /i "hyper-v" suggests a potential issue with Hyper-V.
  • Check for any conflicts or issues with other virtualization software that might be interfering with Claude's VM initialization.
  • Consider disabling and re-enabling Hyper-V and other virtualization features to ensure they are properly registered and recognized by the system.
  • Since the %APPDATA%\Claude\logs folder does not exist and no logs are generated, there might be an issue with the VM's ability to write logs, indicating a deeper configuration or permission problem.

Example

No specific code example is applicable in this scenario as the issue seems to be related to system configuration and virtualization settings rather than code.

Notes

The problem might be specific to the Windows 10 Pro environment and the configuration of Hyper-V and other virtualization features. The fact that the VM never attempts to initialize and no logs are generated limits the ability to diagnose the issue further without additional system information.

Recommendation

Apply workaround: Given the potential complexity of the issue and the lack of clear diagnostic information, attempting to troubleshoot and resolve the Hyper-V and virtualization feature configuration is the most straightforward next step. This approach may help identify or resolve the underlying cause of the virtualization service not responding.

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#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING