Following months of signaling a shift toward unified update management, Microsoft is now testing a mechanism to decouple application updates from the Microsoft Store client.
New code discovered in recent preview builds reveals a dedicated “App updates” section within the main Windows Update settings panel. This integration allows users to maintain installed applications directly through the operating system’s primary update service.
Crucially, the feature functions independently of the Store app itself. This capability addresses a longstanding friction point for enterprise environments where the Store client is often blocked by policy or removed entirely.
Promo
Decoupling Updates from the Store Client
Microsoft is actively testing a new “App updates” toggle within the main Windows Update settings page, distinct from the Microsoft Store application. Discovered in Windows 11 Builds 26100.7309 and 26200.7309, the feature currently appears as a placeholder but signals imminent functionality.
By moving app maintenance directly into the core OS settings, the company is effectively separating the update mechanism from the storefront experience. The primary technical shift is the ability to check for and install application updates without launching, or even having installed the Microsoft Store client.
This mechanism mirrors Linux package managers, centralizing maintenance for both the operating system and user-space applications in one location. While currently non-functional in the Release Preview Channel, the UI explicitly separates these checks from standard OS patches.
The ‘Grand Plan’ for Unified Orchestration
Central to this strategy is Microsoft’s broader goal to create a single “orchestration platform” for all Windows components. By unifying the update pipeline, Microsoft aims to reduce fragmentation where drivers, firmware, and apps currently rely on disparate updaters.
The company’s official documentation defines the scope of this ambition as a “unified, intelligent update orchestration platform capable of supporting any update (apps, drivers, etc.) to be orchestrated alongside Windows updates.”
This unified approach suggests a future where third-party Win32 apps might also leverage this pipeline, though current testing is limited to Store apps.
However, critics remain skeptical about centralizing control, citing past reliability issues with Windows Update. Concerns persist that a single point of failure could impact the stability of critical third-party software. As one developer questioned, “Do you really want a 3rd party app update to bork your system?”
Solving the Enterprise Friction Point
For IT administrators, the reliance on the Microsoft Store app has been a significant pain point in managed environments. Many organizations block the Store client via policy to prevent unauthorized downloads, inadvertently complicating legitimate app updates.
This new Settings-based approach allows admins to keep essential apps (like Calculator or Photos) updated without enabling the full Store experience. The change comes amid heightened sensitivity from the admin community following recent controversies over update naming conventions.
Administrators voiced strong opposition when Microsoft recently attempted to simplify update names by removing dates, leading to significant administrator backlash.
Microsoft’s initial justification for the change was rooted in a desire to simplify the user experience, arguing that technical specifics were unnecessary for the average consumer. The company contended that removing platform architecture and date prefixes would make the update process less intimidating for non-technical users.