[BUG] Cowork "Virtualization is not available" on Windows 11 — ThinkPad E14 G14, Intel i5-1335U, all virtualization features enabled
Resolved 💬 3 comments Opened Apr 22, 2026 by shadilion2-max Closed Apr 26, 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 permanently shows "Virtualization is not available — Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding." Restarting and reinstalling does not fix it. The %APPDATA%\Claude\logs folder is never created, meaning the VM never attempts to initialize.
What Should Happen?
Cowork should detect that virtualization is fully enabled and successfully start the VM workspace.
Error Messages/Logs
"Virtualization is not available — Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding. Restart your computer to resolve this."
%APPDATA%\Claude\logs folder does not exist — VM never initializes.
Steps to Reproduce
- Install Claude Desktop as Administrator on Windows 11
- Open Claude Desktop and sign in
- Navigate to the Cowork tab
- Error appears immediately
- Restarting does not resolve it
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
Latest version from claude.ai/download (Cowork - desktop app, not Claude Code CLI)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
- VirtualMachinePlatform: Enabled via DISM (successful)
- HypervisorPlatform: Enabled via DISM (successful)
- bcdedit /set hypervisorlaunchtype auto: ran successfully
- Full clean uninstall + AppData deleted + fresh reinstall as Administrator — same error
- Regular Claude chat works perfectly, only Cowork is affected
- Related issues: #27420, #32004, #45715, #50348
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗