原文 · 未翻译
Notifications You must be signed in to change notification settings
Fork 21.4k
Star 132k
[BUG] Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use #29045
Description
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?
[BUG] Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use Environment
Note: This issue is specific to the Claude Desktop app (Windows), not Claude Code CLI.
OS: Windows 11 Pro 25H2, Build 26200.7840 Hardware: Razer Blade 15 Base Model (Late 2020), i7-10750H, 16 GB RAM Claude Desktop: Latest version as of 2/26/2026 Windows Features: VirtualMachinePlatform enabled; Hyper-V, WSL, Docker, and Windows Sandbox are all disabled Core Isolation / Memory Integrity: Off
Summary The Claude Desktop app launches a Hyper-V virtual machine (Vmmem) consuming approximately 1.8 GB of RAM every time it starts — even when the user only needs chat functionality and has no intention of using Cowork or agent mode. On a 16 GB laptop, this represents over 11% of total memory consumed by infrastructure that isn't being used. Steps to Reproduce
Install Claude Desktop on Windows 11 with VirtualMachinePlatform enabled Use Cowork/agent mode at least once (this creates session files) Close and reopen Claude Desktop — or simply reboot the machine Open Task Manager and observe Vmmem consuming ~1,800 MB
What Happens On every launch, the Claude Desktop app triggers the Hyper-V Host Compute Service (vmcompute) via an RPC interface event, which spawns a vmwp.exe process hosting a full virtual machine. This VM appears as "Vmmem" in Task Manager at approximately 1,796–1,846 MB. The Hyper-V Compute Admin event log shows repeated errors: "The specified property query is invalid: The virtual machine or container JSON document is invalid. (0xC037010D, 'Invalid JSON document '$'')" These errors have been occurring since at least 2/19/2026, triggered on every boot and app launch. Root Cause Investigation Through extensive PowerShell diagnostics, we confirmed:
WSL is not installed — wsl --shutdown returns "not installed" Hyper-V management tools are not installed — Get-VM fails Docker is not installed — no Docker processes found Windows Sandbox is disabled Core Isolation / Memory Integrity is off (and was off before this issue started) VirtualizationBasedSecurityStatus shows 2 (running), likely due to LSA Protection being enabled — but this alone doesn't explain the 1.8 GB VM The only enabled virtualization feature is VirtualMachinePlatform