[BUG] Cowork yukonSilver marked unsupported for one account but works for another on the same machine — per-account feature flag issue

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?

Support ticket anon.pdf

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?
Two Claude Pro accounts on the same Windows 11 machine (Build 26200.8039, Claude Desktop v1.1.9493.0 MSIX) with identical Hyper-V configuration get different yukonSilver classifications. Account A works perfectly. Account B gets yukonSilver not supported (status=unsupported) on every launch, and the VM bundle is automatically deleted.
Account B previously worked (March 29) — full successful sessions with spawn succeeded. After a BIOS update + Claude auto-update on March 31, it stopped and has not recovered. A missing WinNAT rule was found and recreated, which fixed Account A but not Account B.
This is a server-side per-account feature flag issue, not a system configuration problem. Same machine, same version, same Hyper-V — the only variable is which account is logged in.
Full details, logs, timeline and troubleshooting steps are in the attached document. Account details can be provided via private channel.

What Should Happen?

I should be able to use cowork on both windows accounts with my different claude accounts

Error Messages/Logs

Steps to Reproduce

1. Open claude desktop
2. Try to use cowork

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Version 1.2.234 (2d1855)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_