[BUG] Cowork shows "Virtualization is not enabled" on Windows 11 despite Hyper-V fully enabled (Lenovo ThinkPad)
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 "Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart." — despite all virtualization settings being fully enabled and confirmed working at every level.
All of the following have been verified:
- BIOS: Intel Virtualization Technology (VT-x) = ON, Intel VT-d = ON
- Windows Features: Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Sandbox — all enabled
- bcdedit hypervisorlaunchtype = Auto
- systeminfo confirms: "A hypervisor has been detected"
- CoworkVMService: Running
- Hyper-V Host Compute Service (vmcompute): Running
- No logs folder created at %APPDATA%\Claude\logs — Cowork VM never initializes
- Multiple full reinstalls of Claude Desktop attempted — same result every time
What Should Happen?
Cowork should detect that hardware virtualization is fully enabled at both the BIOS and Windows level, successfully start the VM, create the logs folder, and allow access to the Cowork workspace without showing the "Virtualization is not enabled" error.
Error Messages/Logs
Error displayed in Cowork tab:
"Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart."
No logs available — %APPDATA%\Claude\logs folder does not exist.
The only file in %APPDATA%\Claude\ is claude_desktop_config.json.
Steps to Reproduce
- Install Claude Desktop on Windows 11 (Build 26200.7840) on Lenovo ThinkPad with Intel CPU
- Ensure BIOS virtualization is enabled (Intel VT-x and VT-d both ON)
- Enable all Windows features: Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform
- Confirm bcdedit hypervisorlaunchtype is set to Auto
- Confirm CoworkVMService and vmcompute services are Running
- Open Claude Desktop and navigate to the Cowork tab
- Error "Virtualization is not enabled" appears despite everything being correctly configured
- No logs folder is created under %APPDATA%\Claude\logs
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Desktop (not Claude Code CLI) — latest version downloaded Feb 2026
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
System Details:
- Device: Lenovo ThinkPad
- OS: Windows 11 (Build 26200.7840)
- CPU: Intel (VT-x and VT-d supported and enabled)
- Hyper-V: Fully enabled (all sub-features)
- Virtual Machine Platform: Enabled
- Windows Hypervisor Platform: Enabled
- Windows Sandbox: Enabled
- bcdedit hypervisorlaunchtype: Auto
- systeminfo: "A hypervisor has been detected. Features required for Hyper-V will not be displayed."
- CoworkVMService: Running
- vmcompute (Hyper-V Host Compute Service): Running
Key observation: The %APPDATA%\Claude\logs folder does not exist at all, suggesting the Cowork VM never even attempts to initialize. The only file in %APPDATA%\Claude\ is claude_desktop_config.json.
This appears to be the same issue as #27316 and related to #25155, #27363, #25136.
Attach screenshots of: BIOS settings, Windows Features, PowerShell outputs, and the Cowork error message.
This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗