[BUG] Cowork tab missing — cowork-svc.exe trusts WMI VirtualizationFirmwareEnabled which returns False on i5-5300U despite VT-x working

Resolved 💬 3 comments Opened Apr 19, 2026 by heavy351 Closed Apr 23, 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?

Device: Lenovo ThinkPad X250
CPU: Intel Core i5-5300U
OS: Windows 10 LTSC 21H2 (19045)
Claude Desktop: v1.3109.0 (35cbf6)
Plan: Pro

Task Manager → Performance → CPU → Virtualization: Enabled
WMI: Get-WmiObject Win32_Processor | VirtualizationFirmwareEnabled → False
cowork_vm_node.log: yukonSilver not supported (status=unsupported) on every launch

All virtualization features enabled:

  • Intel VT-x: enabled in BIOS
  • Hyper-V: installed via DISM
  • VirtualMachinePlatform: enabled
  • HypervisorPlatform: enabled
  • bcdedit hypervisorlaunchtype: auto

Same Claude Desktop version + same LTSC image works correctly on
a different machine (SILENCE workstation, different CPU).
Problem is hardware-specific WMI reporting, not OS edition.

cowork-svc.exe isHardwareVirtEnabled() appears to rely on
Win32_Processor.VirtualizationFirmwareEnabled which returns False
on i5-5300U firmware despite VT-x being fully functional.
Task Manager is the reliable source — WMI is not.

Related: #27357, #27462, #32004

What Should Happen?

Claude should load Cowork

Error Messages/Logs

Steps to Reproduce

Device: Lenovo ThinkPad X250
CPU: Intel Core i5-5300U
OS: Windows 10 LTSC 21H2 (19045)
Claude Desktop: v1.3109.0 (35cbf6)
Plan: Pro

Task Manager → Performance → CPU → Virtualization: Enabled
WMI: Get-WmiObject Win32_Processor | VirtualizationFirmwareEnabled → False
cowork_vm_node.log: yukonSilver not supported (status=unsupported) on every launch

All virtualization features enabled:

  • Intel VT-x: enabled in BIOS
  • Hyper-V: installed via DISM
  • VirtualMachinePlatform: enabled
  • HypervisorPlatform: enabled
  • bcdedit hypervisorlaunchtype: auto

Same Claude Desktop version + same LTSC image works correctly on
a different machine (SILENCE workstation, different CPU).
Problem is hardware-specific WMI reporting, not OS edition.

cowork-svc.exe isHardwareVirtEnabled() appears to rely on
Win32_Processor.VirtualizationFirmwareEnabled which returns False
on i5-5300U firmware despite VT-x being fully functional.
Task Manager is the reliable source — WMI is not.

Related: #27357, #27462, #32004

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

v1.3109.0 (35cbf6)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

same image different result

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗