In this analysis
Desktop running modes describe a service lifecycle; their suitability depends on interactive and unattended work patterns rather than GPU specifications alone.
AlwaysOn and AutoStop appeared alongside the hardware specifications in the WorkSpaces G7 announcement. They belong in a workstation migration decision because an interactive session has a lifecycle, not just a GPU requirement. A memory comparison alone cannot describe when a user expects the desktop to be ready.
The release joined hardware and running modes
The September 16, 2026 release introduced Graphics G7 for WorkSpaces Personal and Core. It named Windows BYOL and both running modes with the Blackwell bundles. The announcement establishes those supported options; it does not calculate savings for an arbitrary team’s schedule.
For a designer who works interactively, the relevant unit is the working session. For a long unattended task, the relevant unit may extend beyond the time a person remains connected. Those patterns can lead to different operational requirements even with identical scene data.
Hardware history does not determine session policy
NVIDIA’s March 18, 2025 RTX PRO introduction supplied the hardware precursor. That introduction says nothing by itself about a cloud desktop’s running mode. Service integration adds a second layer of decisions beyond the board.
The causal argument is that migration moves both execution resources and expectations about availability. A faster or larger device cannot compensate for a workflow whose session behavior was misunderstood. This is a workflow dependency, not a claim about a measured G7 failure.
Remote applications supplied a different precedent
The AppStream G6 announcement on July 17, 2025 concerned application streaming. It shows that GPU delivery already had a service lifecycle before this desktop release, but the two service models should not inherit each other’s session assumptions without evidence.
An existing local workstation also carries implicit habits: leaving software open, returning after a break, or expecting a background operation to continue. Migration makes those habits explicit requirements rather than incidental properties of a machine under someone’s desk.
A session map for an illustrative team
| Work pattern | Requirement to describe |
|---|---|
| Scheduled design session | Expected readiness when work starts |
| Long application operation | Behavior beyond active interaction |
| Interrupted workday | State needed on return |
| Shared project handoff | Where durable project outputs reside |
This map does not assign prices or assume either running mode is always preferable. It exposes which parts of the working day depend on the desktop being active and which depend on durable storage or application recovery.
Why the distinction matters historically
The release expanded a managed workstation option, so the adoption question includes session design as well as device selection. AlwaysOn and AutoStop are named service choices, not interchangeable slogans for uninterrupted execution or automatic savings.
GPU reserve capacity discusses availability requirements, while Vast instance stopping versus deletion examines lifecycle distinctions. The migration artifact should explain the desired user experience before attaching a cost conclusion to a running mode. The announcement itself supplies no universal answer for every work schedule.