Recently, many Windows platform users have expressed strong dissatisfaction with the
According to user feedback in the community, the problem lies in the resource calling mechanism of this program on the Windows system. Once a user has experienced Claude Cowork or the Agent mode, the software will silently start a 1.8GB Hyper-V virtual machine process in the background. The awkward part is that even if the user only performs the most basic conversation, this process will not end.
What troubles users even more is that during daily use, every time they launch Claude Code, the system automatically creates this large process, which appears as "Vmmem" in Task Manager. Although the CPU usage is almost zero, the long-term occupation of 1.8GB of memory is undoubtedly a heavy burden for devices with limited memory resources.
It is worth noting that this issue is not new. By checking the developer feedback records on GitHub, it can be found that users had already reported this Bug as early as February this year, but unfortunately, it has not yet been effectively fixed by the official team. This lack of response has led some loyal users to uninstall the program.
The technical community has analyzed this issue and believes that the design logic of this process has room for optimization. Users generally call on the development team to improve their resource scheduling strategy, meaning that this virtual machine process should only be started on demand when the Agent mode is explicitly triggered, and related session files should be actively cleaned up after the task is completed, rather than running constantly in the background.
At present, this issue is limited to the Windows platform, and the CLI client and other platforms are not yet affected. For Windows users who still rely on Claude Desktop for daily work, before the official releases a clear update patch, they may have to manually terminate the relevant processes or look for alternative solutions.
