After remote use, an apparently idle Windows desktop may still have a background application waking the discrete GPU, while a Mac virtual ultrawide display remains enabled. These are separate systems and require separate evidence.

This article combines LegionZone attribution and RustDesk display-cleanup records: identify resource users, establish session state, then consider a configuration change or display action. Historical GPU observations remain intact; the original single-connection cleanup script is not presented as validated automation.

A standard Windows Server AMI on g4dn or g5 may initially expose only Microsoft Basic Display Adapter, with no working nvidia-smi. After installing the driver, another gap appears: the Windows CloudWatch Agent cannot use the Linux nvidia_gpu receiver.

This guide connects both steps—installing an AWS GRID driver and publishing parsed nvidia-smi values as custom CloudWatch metrics.

After upgrading to Hermes v0.17.0, the Mac's idle power draw jumped from a normal 3-5W to 19W and the fans spun up. Using powermetrics to quantify, ps to localize the process, and sample to grab the call stack, I traced it all the way to Chromium's Rust font engine fontations and the Rust implementation of the Temporal API, temporal_rs, repeatedly formatting time strings and validating glyphs every frame, pinning the GPU at full load. This post records the full investigation.