[BUG] Cowork "Virtualization is not available" on Windows 10 Pro — VM never initializes, no logs created

Resolved 💬 3 comments Opened Apr 19, 2026 by nrjslovensko-stack Closed Apr 23, 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?

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
| Check | Result |
|---|---|
| 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)

  1. Download and install latest Claude Desktop from claude.ai/download

as Administrator

  1. Launch Claude Desktop and navigate to the Cowork tab
  1. Observe "Virtualization is not available" error message immediately
  1. Restart computer → error persists
  1. Verify CoworkVMService is Running via PowerShell:

Get-Service CoworkVMService → Status: Running

  1. 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

  1. Check %APPDATA%\Claude\logs → folder does not exist,

no logs generated, VM never initializes

  1. Full uninstall of Claude Desktop, delete %APPDATA%\Claude

and %LOCALAPPDATA%\claude-code-vm, reinstall as Administrator → same result

  1. 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_

View original on GitHub ↗

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