[BUG] Cowork Windows - "Virtualization is not enabled" despite Hyper-V/VMP/WSL all enabled and CoworkVMService running
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 shows "Virtualization is not enabled - Claude's workspace requires hardware virtualization (Hyper-V)" despite all virtualization features being enabled and the CoworkVMService running. Cowork was working earlier today and broke without any user changes.
Also seeing two MCP connection errors:
"Could not connect to MCP server mcp-registry"
"Could not connect to MCP server Claude in Chrome"
Environment
OS: Windows 11, Lenovo ThinkPad X1 Carbon 7th Gen (20QG)
BIOS: N2HET84W (1.67)
Claude Desktop: MSIX install (Claude_pzs8sxrjxfjjc)
Troubleshooting Already Attempted (all successful, issue persists)
bcdedit /set hypervisorlaunchtype auto → "operation completed successfully"
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all → success
dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-All /all → success
Enabled Windows Subsystem for Linux via optionalfeatures
Multiple restarts
Get-Service CoworkVMService → Status: Running
Key Observation
The CoworkVMService is running and all virtualization prerequisites are confirmed enabled, yet the app reports virtualization is not enabled. This appears to be a false negative in the virtualization detection logic.
What Should Happen?
Expected Behavior
Cowork should detect that virtualization is enabled (as it did earlier today) and start normally.
Error Messages/Logs
No log files found in:
%APPDATA%\Claude\logs\
%LOCALAPPDATA%\Claude\
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\ (no .log files present)
The MSIX install appears to not be generating logs, which is a secondary issue.Steps to Reproduce
- Open Claude Desktop (v1.1.3918.0) on Windows 11
- Click on the "Cowork" tab
- Error displayed: "Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart."
- Also shows: "Could not connect to MCP server mcp-registry" and "Could not connect to MCP server Claude in Chrome"
Note: Cowork was working earlier the same day with no changes made by the user.
Verified via PowerShell:
Get-Service CoworkVMService→ Status: Runningbcdedit /set hypervisorlaunchtype auto→ completed successfullydism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all→ successdism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-All /all→ success- WSL enabled via Windows Features
- Multiple restarts performed
- No log files found in %APPDATA%\Claude\ or %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\
Environment:
- Windows 11, Lenovo ThinkPad X1 Carbon 7th Gen (20QG)
- BIOS: N2HET84W (1.67)
- Claude Desktop: 1.1.3918.0 (MSIX install)
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
Yes — it was working this morning.
Claude Code Version
Claude Desktop Version: 1.1.3918.0
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I have this issue can you investigate if it is indeed a bug or there is anything I can do?
Environment:
OS: Windows 11 Pro 25H2 (Build 26200.7462) — received via standard Windows Update, not Insider Programme
Hardware: Dell Latitude 7400 (physical machine, confirmed not a VM)
Installer: Claude Setup.exe (direct download from claude.ai/download)
Windows Features enabled:
Microsoft-Hyper-V-All ✅
HypervisorPlatform ✅
VirtualMachinePlatform ✅
WSL2 installed with Ubuntu ✅
Services running:
vmms (Running, Automatic)
vmcompute (Running, Manual)
hns (Running, Manual)
Relevant log output from cowork_vm_node.log:
2026-02-21 10:21:44 [info] [cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle... 2026-02-21 10:22:37 [warn] [startVM] VM not supported (win32/x64), skipping
Error shown in UI:
"Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart."
This error is misleading — hardware virtualization is confirmed enabled and all required features are active. The issue appears to be yukonSilver incorrectly flagging this win32/x64 environment as unsupported despite full Hyper-V support being present.
I too have the same issue tried everything but still the error persistent
See my ticket #27427 for additional logs. I am closing as dupe
I have the same issue on two computers. Win10 Home. Installed hyper-v and enabled everything but that didn't help.
Closing as duplicate of #27316 which was very rapidly fixed in the v1.1.3963 release
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.