Cowork VM: 'Virtualization is not enabled' after update to 1.1.3918 - yukonSilver unsupported regression
Status Fixed / completed
Maintainer reply None cached
Activity 6 comments · opened Feb 21, 2026 · closed Feb 22, 2026
Description
After updating Claude Desktop from 1.1.3363 to 1.1.3918 on Windows 11, Cowork shows "Virtualization is not enabled" and refuses to start the VM. This is a regression - Cowork was working on 1.1.3363 (Feb 20).
Environment
- OS: Windows 11 Pro 10.0.26200 (x64)
- CPU: Intel Core Ultra 9 275HX
- RAM: 32 GB
- Claude Desktop version: 1.1.3918.0 (Microsoft Store / MSIX)
- Previous working version: 1.1.3363.0
What happened
- Cowork was working on version 1.1.3363 (Hyper-V event log confirms
cowork-vm started successfullyon Feb 20) - Got an
EBUSYerror on the VHDX copy (separate issue, likely file lock from prior session) - Reinstalled Claude Desktop, which updated to 1.1.3918
- Cowork now shows "Virtualization is not enabled" permanently
- Rebooting, reinstalling, and adding user to Hyper-V Administrators group did not help
Root cause from logs
The cowork_vm_node.log shows the new version is not even attempting to start the VM:
[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
[startVM] VM not supported (win32/x64), skipping
This repeats on every startup attempt. The old version (1.1.3363) did NOT have this behavior - it attempted VM startup normally.
Hyper-V is fully functional
Confirmed via PowerShell:
HypervisorPresent: True- Services running:
vmms,vmcompute,CoworkVMService Get-VM: works (user is in Hyper-V Administrators group)- Hyper-V features installed:
Microsoft-Hyper-V,Microsoft-Hyper-V-Hypervisor,Microsoft-Hyper-V-Services,VirtualMachinePlatform,HypervisorPlatform
Expected behavior
Cowork should start the VM on win32/x64 with Hyper-V enabled, as it did on version 1.1.3363.
Relevant log excerpts
Old version (1.1.3363) - attempted VM start:
[VM:start] Beginning startup, bundlePath=...
[VM:start] Copying smol-bin.x64.vhdx to bundle...
[VM:start] Startup failed: Error: EBUSY: resource busy or locked, copyfile...
New version (1.1.3918) - skips entirely:
[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
[deleteVMBundle] Deleting reinstall files from ...\claudevm.bundle
[startVM] VM not supported (win32/x64), skipping
[Callbacks] Initializing VM event callbacks...
[VM] Loading vmClient (TypeScript) module...
[VM] Module loaded successfully
[Callbacks] VM event callbacks initialized
[startVM] VM not supported (win32/x64), skipping
Steps to reproduce
- Install Claude Desktop 1.1.3918 on Windows 11 with Hyper-V enabled
- Open Claude Desktop and click the Cowork tab
- Observe "Virtualization is not enabled" error
- Check
%APPDATA%\Claude\logs\cowork_vm_node.logforyukonSilver not supported
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Windows 11 25H2 (Build 26200), Dell hardware
IsProcessorFeaturePresent(PF_VIRT_FIRMWARE_ENABLED) returns False due to firmware-enforced VBS
WHvGetCapability also fails (HRESULT 0x80370001)
The fix: use a correct WHvP API check instead
I'm hitting the same thing on Dell hardware
Hacky fix that worked for me (for now):
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.