[BUG] Cowork "Virtualization is not available" — Virtual Machine Platform not responding
Resolved 💬 4 comments Opened Apr 18, 2026 by Saran-tech24 Closed Jun 13, 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?
The 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."
What Should Happen?
Restarting the computer does not fix the issue. The VM never initializes.
Error Messages/Logs
Steps to Reproduce
- Install Claude Desktop (latest version) from claude.ai/download
- Open Claude Desktop and navigate to the Cowork tab
- Observe the "Virtualization is not available" error immediately
- Restart the computer — error persists
---
Expected Behavior
Cowork should detect that the system supports virtualization and successfully start the VM workspace.
Actual Behavior
Cowork permanently shows the "Virtualization is not available" error. Only the Cowork tab is affected — regular Claude chat works fine.
---
Environment
- OS: [Windows 10]
- Claude Desktop version: [ Latest Version]
- Subscription: [Pro]
- CPU: [Intel Core i7-12700 ]
- Virtualization in Task Manager → CPU tab: [Enabled ]
---
Checklist
- [ ] Virtual Machine Platform — enabled via
optionalfeatures - [ ] Windows Hypervisor Platform — enabled via
optionalfeatures - [ ] Hyper-V — enabled
- [ ] Virtualization enabled in BIOS/UEFI
- [ ] Restarted after enabling features — error still persists
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.3109.0.0
Platform
Other
Operating System
Windows
Terminal/Shell
Other
Additional Information
<img width="1785" height="787" alt="Image" src="https://github.com/user-attachments/assets/e8f978f4-810e-41ba-9ed7-188e0668d1ab" />
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗