### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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 is impossible to use on this system. Root cause identified: the vmms service (Virtual Machine Management Service) does not exist. Running Get-Servi

[BUG] Cowork impossible on MSI MPG X570 / Ryzen 9 3900X — vmms service missing, Hyper-V causes boot failure

Status Open

Maintainer reply None cached

Activity 6 comments · opened May 27, 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?

Cowork is impossible to use on this system. Root cause identified: the vmms service (Virtual Machine Management Service) does not exist. Running Get-Service vmms returns "No service found". Without vmms, the Cowork VM cannot start. Enabling Hyper-V or Virtual Machine Platform causes complete Windows 11 boot failure every time — System Restore is required to recover.

What Should Happen?

Cowork should either install the vmms service correctly during setup, or support an alternative virtualization backend (such as WSL2) for systems where Hyper-V causes boot failure.

Error Messages/Logs

Get-Service vmms → "No service found"
Cowork Readiness Check → "Virtual Machine Platform — missing services: vmcompute, HNS, vfpext"
Enabling Virtual Machine Platform → Windows 11 boot failure, automatic repair loop
System Restore required to recover after every attempt
Related issues: #35728, #32409

Steps to Reproduce

Install Claude Desktop on Windows 11 Pro (MSI MPG X570 / AMD Ryzen 9 3900X)
Run Get-Service vmms in PowerShell — returns "No service found"
Enable Virtual Machine Platform and restart
Windows fails to boot — automatic repair loop
System Restore required to recover

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude 1.1.7053 (cc1949) 2026-03-16

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

CPU: AMD Ryzen 9 3900X — MSI MPG X570 Gaming Edge WiFi — 64GB RAM — RTX 4080 SUPER — Windows 11 Pro Build 26200. UEFI mode, Secure Boot enabled, SVM enabled, CSM disabled. Claude Desktop chat works perfectly. Issue is specific to Cowork virtualization layer.

View original on GitHub ↗

6 Comments

witchboywitchboy · 2 months ago

I am experiencing the same issue still as of 6/21/2026
Environment:

Device: ASUS TUF Gaming Laptop
OS: Windows 11 Pro
CPU: AMD (SVM Mode)
Claude Desktop: v1.14271.0 (c8f4d8) — MSIX/Store package (Claude_1.14271.0.0_x64__pzs8sxrjxfjjc)

What's wrong:

Cowork launches and the UI works, but the bash shell fails with HYPERVISOR_VIRT_DISABLED every session, preventing any shell commands from running.

What I've tried:

Enabled SVM Mode in ASUS BIOS — Windows fails to boot with SVM enabled, requiring recovery mode to disable it each time
All Hyper-V Windows features confirmed enabled (Microsoft-Hyper-V-All, HypervisorPlatform, VirtualMachinePlatform, etc.)
bcdedit hypervisorlaunchtype set to Auto
systeminfo confirms all four Hyper-V requirements show Yes including "Virtualization Enabled In Firmware"
Device Guard / VBS confirmed off (VirtualizationBasedSecurityStatus: 0)
Deleted %APPDATA%\Claude\vm_bundles and restarted CoworkVMService — Cowork UI starts but bash shell still disabled
Downloaded installer from claude.ai/download — still installs as MSIX (pzs8sxrjxfjjc), not a true direct installer
(Get-CimInstance Win32_ComputerSystem).HypervisorPresent returns False despite all features enabled — consistent with known WMI reporting bug on this Windows build

Root cause hypothesis:

Two compounding issues:

The MSIX AppContainer call path incorrectly detects virtualization as disabled (consistent with issues #60371, #34323, #33784)
On this ASUS TUF AMD laptop, enabling SVM in BIOS causes Windows boot failure — possibly a firmware conflict — making it impossible to get HypervisorPresent to return True

Ask:

Provide a true non-MSIX direct installer for Windows that bypasses the AppContainer detection bug
Investigate the SVM/boot conflict on ASUS TUF AMD hardware
Consider falling back to a different virtualization detection method that doesn't rely on Win32_ComputerSystem.HypervisorPresent, which is known to report incorrectly on some Windows builds

Related issues: #60371, #34323, #33784, #30997, #27316

aurorebsn · 1 month ago

Same for me

vicmatta · 1 month ago

See similar issue with Cowork. When I click on the Cowork button it says: missing HCS services: HNS, vmcompute, vfpext.
I am using a Snapdragon Elite Sin 11 Microsoft Surface Pro.
Claude chat suggested I reinstall, failing which to report it on Github. The error persisted after a clean uninstall and reinstall. I used the ARM based setup file each time. Please help.

y3 · 1 month ago

same here

baptistevivier1-cmyk · 1 month ago