[BUG] [Window 11] Claude Cowork does not show up

Resolved 💬 3 comments Opened Feb 12, 2026 by Abhi-Prad Closed Feb 15, 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?

Environment:

  • Claude Desktop v1.1.2685 (latest)
  • Windows 11 Enterprise 10.0.26100 (x64)
  • Intel Core Ultra 7 268V, 32GB RAM

Cowork tab does not appear in Claude Desktop UI. Our org admin has enabled cowork, but the feature flag is not
reaching the client.

What's working (local infra is ready):

  • CoworkVMService is running
  • vmcompute (Hyper-V Host Compute Service) is running
  • HNS network cowork-vm-nat exists
  • Hypervisor is present and enabled
  • Hyper-V Management PowerShell module installed
  • App starts successfully, account is active and logged in

What's not working:

  • GrowthBook loads 19 features on startup — none trigger cowork initialization
  • cowork_vm_node.log only shows yukonSilver not supported (status=unsupported) cleanup — no VM boot is attempted
  • main.log has zero cowork-related entries
  • No Cowork tab visible in the UI
  • Logged out and back in — no change

What Should Happen?

Cowork tab should appear next to "Chat" in the mode selector, and clicking it should boot the Windows VM.

Relevant logs:

  • main.log — no cowork initialization, can_elevate: false
  • cowork_vm_node.log — only yukonSilver cleanup, no Windows VM path executed
  • No claude_vm_node.log created (VM never boots)

Error Messages/Logs

Steps to Reproduce

Download pacakge for Claude cowork.
Install it
Open Claude desktop

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

NA

Platform

Other

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

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