Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork tab missing — yukonSilver marked as unsupported despite VM service running and Hyper-V enabled

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…

Error Message

Error Messages/Logs

Root Cause

Same root cause as #47327, #25136, #25692. The platform detection logic incorrectly classifies this system as unsupported despite all required virtualization components being present and running

Code Example

Log from cowork_vm_node.log:
[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
[VM] Loading vmClient (TypeScript) module...
[VM] Module loaded successfully
[logout] Failed to stop VM on logout: not configured: call 'configure' first
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?

The Cowork tab does not appear in Claude Desktop. On every launch, cleanupVMBundleIfUnsupported marks yukonSilver as unsupported and cleans up the VM bundle before it can initialize. The VM module itself loads successfully, but is never configured. System info:

OS: Windows 11 Home 25H2 Hyper-V: enabled Claude Desktop: 1.3109.0.0 (MSIX, x64) Subscription: Pro CoworkVMService: Running

What Should Happen?

Cowork tab should appear and VM should initialize successfully. CoworkVMService is running, Hyper-V is enabled, VM module loads without errors — platform detection should not block initialization.

Error Messages/Logs

Log from cowork_vm_node.log:
[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
[VM] Loading vmClient (TypeScript) module...
[VM] Module loaded successfully
[logout] Failed to stop VM on logout: not configured: call 'configure' first

Steps to Reproduce

Install Claude Desktop (MSIX, x64) on Windows 11 Home 25H2 with Hyper-V enabled Confirm CoworkVMService is running (Get-Service CoworkVMService) Confirm vmms service is running (Get-Service vmms) Launch Claude Desktop Observe: Cowork tab does not appear Check %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\cowork_vm_node.log — shows repeated yukonSilver not supported (status=unsupported) on every launch, VM never initializes

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

1.3109.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Same root cause as #47327, #25136, #25692. The platform detection logic incorrectly classifies this system as unsupported despite all required virtualization components being present and running

extent analysis

TL;DR

The issue can be fixed by re-evaluating the platform detection logic to correctly classify the system as supported when all required virtualization components are present and running.

Guidance

  • Review the cleanupVMBundleIfUnsupported function to understand why yukonSilver is being marked as unsupported despite Hyper-V being enabled and CoworkVMService running.
  • Verify that the system meets all requirements for virtualization support, including Hyper-V and vmms service status.
  • Investigate the similarities with issues #47327, #25136, and #25692 to identify a potential pattern or common cause.
  • Consider temporarily bypassing the cleanupVMBundleIfUnsupported check to test if the VM initializes successfully.

Example

No code snippet is provided as the issue does not contain sufficient information about the cleanupVMBundleIfUnsupported function or the platform detection logic.

Notes

The issue seems to be related to a misclassification of the system as unsupported by the platform detection logic. The fact that it never worked and is similar to other issues suggests a deeper problem that may require changes to the detection logic.

Recommendation

Apply a workaround to bypass the cleanupVMBundleIfUnsupported check, as the system appears to meet all requirements for virtualization support. This will help determine if the issue is indeed related to the platform detection logic.

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#dependency error#configuration error#environment variable#network issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork tab missing — yukonSilver marked as unsupported despite VM service running and Hyper-V enabled