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

Resolved 💬 3 comments Opened Mar 24, 2026 by civitfran-maker Closed Mar 27, 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?

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Desktop

What's Wrong?

Cowork displays "La virtualización no está disponible — El espacio de trabajo de Claude requiere Virtual Machine Platform, pero el servicio de virtualización no responde" on every launch. Restarting does not resolve it.

The %APPDATA%\Claude folder is created after installation but remains completely empty — no logs are generated, which indicates the Cowork VM never attempts to initialize.

Environment

| Component | Status |
|---|---|
| OS | Windows 10 Pro 22H2 (Build 19045) |
| Claude Desktop | Latest (downloaded from claude.ai/download) |
| Subscription | Pro |
| Virtual Machine Platform | ✅ Enabled |
| Windows Hypervisor Platform | ✅ Enabled |
| Hyper-V | ✅ Enabled |
| CoworkVMService | ✅ Running |
| %APPDATA%\Claude folder | ✅ Exists but empty |
| cowork_vm_node.log | ❌ Does not exist |

Steps to Reproduce

  1. Install Claude Desktop on Windows 10 Pro 22H2 with all virtualization features enabled
  2. Launch Claude Desktop
  3. Navigate to the Cowork tab
  4. Observe: "La virtualización no está disponible" error appears immediately
  5. No logs are generated under %APPDATA%\Claude\logs\

What Was Tried

  • Restarted PC multiple times
  • Reinstalled Claude Desktop as administrator
  • Enabled Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform via Windows Features
  • Ran Restart-Service CoworkVMService -Force — service restarts successfully but issue persists
  • Cleared MSIX package cache (wsreset.exe)
  • Removed leftover MSIX temp files from %LOCALAPPDATA%\Temp\Claude-*
  • Repaired Windows image via DISM /Online /Cleanup-Image /RestoreHealth — completed successfully
  • Verified no orphaned AppX packages via Get-AppxPackage -AllUsers

Expected Behavior

Cowork should detect that all virtualization features are active and initialize the workspace successfully.

Actual Behavior

The error appears immediately. The VM never attempts to start. No log files are created.

Additional Notes

Chat and Code tabs work correctly. Only Cowork is affected. This appears to be the same issue reported in #25136, #27316, #27420, #29887, and #32004.

What Should Happen?

Cowork should detect that all virtualization features are active and initialize the workspace successfully, generating logs under %APPDATA%\Claude\logs\

Error Messages/Logs

CoworkVMService: Running
%APPDATA%\Claude folder: exists but completely empty
cowork_vm_node.log: does not exist — VM never attempts to initialize

ClaudeSetup.log errors:
MSIX installation failed: AddPackage failed with HRESULT 0x80073CF6
Administrator access is required to install Claude with full features.

Steps to Reproduce

  1. Install Claude Desktop on Windows 10 Pro 22H2 with all virtualization features enabled (Virtual Machine Platform, Windows Hypervisor Platform, Hyper-V)
  2. Launch Claude Desktop
  3. Navigate to the Cowork tab
  4. Observe: "La virtualización no está disponible" error appears immediately
  5. Check %APPDATA%\Claude\logs\ — folder exists but is completely empty, no logs generated

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Desktop (latest, downloaded from claude.ai/download)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Related issues: #25136, #27316, #27420, #29887, #32004
Chat and Code tabs work correctly. Only Cowork is affected.
Ran DISM /RestoreHealth successfully. Cleared MSIX temp files. Ran wsreset.exe. Issue persists.

View original on GitHub ↗

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