[BUG] Cowork incompatible with Universal Audio Apollo (UAD kernel drivers) on Windows 11 Pro — Hyper-V conflicts with pro audio hardware
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?
Cowork cannot be used on a professional audio production system running Universal Audio Apollo hardware. Enabling Hyper-V (required for Cowork) conflicts with UAD's kernel-level DSP drivers, causing Windows to fail to boot entirely.
What Should Happen?
Cowork should either support WSL2 as an alternative backend that doesn't require full Hyper-V, or detect and warn users that pro audio kernel-level drivers are incompatible before enabling Hyper-V.
Error Messages/Logs
No Cowork error log generated — system fails to boot before reaching Windows. Boot failure occurs when both Hyper-V (hypervisorlaunchtype=Auto) and Intel VT-x are active simultaneously with UAD drivers installed.Steps to Reproduce
- Install UAD Console software with Universal Audio Apollo connected via Thunderbolt
- Enable Intel VT-x in BIOS
- Run: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
- Set: bcdedit /set {current} hypervisorlaunchtype auto
- Install Claude Desktop with Cowork
- Reboot — system fails to boot into Windows
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
Claude Desktop
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
Windows 11 Pro Build 26200.8246. UAD Apollo Thunderbolt. Confirmed fix: removing Hyper-V and setting bcdedit hypervisorlaunchtype=Off restores stable boot. VirtualMachinePlatform and WSL remain enabled without conflict. Related WSL2 backend requests: #6191, #31991. This affects all professional audio users running UAD hardware — a significant Claude Pro user segment.