Anthropic's Claude Desktop application for Windows is automatically spawning a 1.8 GB Hyper-V virtual machine on startup, even when users only require simple chat features. According to detailed bug reports on GitHub, the background process consumes over 11% of total memory on standard 16 GB laptops without user request. Affected developers have uncovered that local session buildup and background service triggers force the virtualization layer to launch unconditionally.
Background VM Spawns Waste System Memory
Windows developers using Anthropic's desktop client discovered that launching the app triggers the Hyper-V Host Compute Service (vmcompute). This service spawns a vmwp.exe process that allocates a 1.8 GB virtual machine in system RAM on every boot regardless of whether advanced agent mode is used.
For users on 16 GB machines, this unexpected footprint pushes idle system RAM consumption from 50% up to 62%, frequently causing overall system sluggishness when combined with other active applications.
Key findings from the user investigation include:
- Memory Footprint: Allocates between 1,796 MB and 1,846 MB of RAM immediately upon launch.
- Prerequisites: Occurs on Windows 11 systems running
VirtualMachinePlatformafter using agent or Cowork features at least once. - Session Accumulation: Diagnostics revealed up to 2,689 uncleaned session files stored in
%APPDATA%\Claude\local-agent-mode-sessions\. - Chat Independence: Basic chat functionality remains operational even after the virtual machine process is manually killed.
Root Cause: Uncleaned Sessions and Service Triggers
Investigation using PowerShell diagnostics confirmed that the issue is tied directly to local session handling rather than external tools like Docker or WSL. When Claude Desktop opens, an RPC interface event triggers services.exe to start the Hyper-V compute infrastructure.
Event logs from the Hyper-V Compute Admin show recurring errors stating that the virtual machine JSON document is invalid (0xC037010D). Even after manually deleting thousands of stale Docker-style session files and terminating running processes, launching the desktop application immediately recreates the 1.8 GB memory footprint.
Notably, the issue filed on GitHub was marked as invalid by maintainers because it was submitted to the claude-code CLI repository instead of the dedicated desktop application feedback channel.
Workarounds for Affected Windows Users
Until an official application patch modifies the initialization logic, developers have identified two primary methods to reclaim system memory: