Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork tab missing — cowork-svc.exe trusts WMI VirtualizationFirmwareEnabled which returns False on i5-5300U despite VT-x working [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50794•Fetched 2026-04-20 12:12:52
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
heavy351heavy351
Participants
github-actions[bot]github-actions[bot]heavy351heavy351
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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

extent analysis

TL;DR

The issue can be resolved by modifying the isHardwareVirtEnabled() function in cowork-svc.exe to rely on the Task Manager's virtualization status instead of WMI's Win32_Processor.VirtualizationFirmwareEnabled property.

Guidance

  • Investigate alternative methods for detecting virtualization support, such as using the Task Manager's API or other system calls that accurately report virtualization status.
  • Consider adding a fallback or override mechanism to isHardwareVirtEnabled() to handle cases where WMI reporting is incorrect, as seen with the i5-5300U firmware.
  • Review related issues (#27357, #27462, #32004) for potential insights or workarounds that may apply to this specific hardware configuration.
  • Verify that the modified isHardwareVirtEnabled() function correctly identifies virtualization support on the affected hardware (Lenovo ThinkPad X250 with i5-5300U CPU).

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The problem appears to be hardware-specific, related to incorrect WMI reporting on the i5-5300U firmware. The solution may need to account for this specific hardware configuration.

Recommendation

Apply a workaround by modifying the isHardwareVirtEnabled() function to use a more reliable method for detecting virtualization support, as the current implementation relying on WMI is flawed for this particular hardware.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING