Windows 11 update previews KB5120998 push versions 24H2 and 25H2 to build 26100.9278 and 26200.9278 respectively, rolling out a long-awaited fix that allows the taskleiste to be positioned on all four sides of the screen by September 2026, alongside the mainstream debut of Administrator Protection.
Fixing Windows 11’s Most Persistent UI Bottleneck
Ever since Microsoft launched Windows 11, the rigidly anchored taskbar at the bottom of the screen has served as a primary friction point for power users and enterprise administrators alike. According to versions tracked in the preview channels, that lock-in is finally dissolving. In updates arriving toward the September 2026 patch cycle, users can once again pin the taskleiste to the top, left, right, or bottom of any connected monitor.
Reaching these hidden layout controls requires diving into a reorganized settings tree. Navigation runs through Settings, then Personalization, followed by Taskbar, and finally Taskbar Behaviors. Microsoft has streamlined this discovery process by expanding the behavior menu by default, exposing both a new Taskbar Size toggle for compact layouts and a dedicated Taskbar Position dropdown selector.
There are, however, engineering tradeoffs baked into these layout changes. Early evaluation builds highlight that vertical taskbar placements—snapping the bar to the left or right edges—impose temporary limitations on how search boxes and compact icon groups render, as those elements are currently optimized strictly for horizontal top-and-bottom workflows.
Isolating Processes with Administrator Protection
Beyond cosmetic adjustments, the preview bundles a critical security overhaul that Microsoft has been iterating on since late 2024: Administrator Protection. Traditional User Account Control (UAC) has long relied on modifying security tokens for the active user session, permitting applications to execute without elevated privileges until a prompt explicitly demands consent.
Administrator Protection fundamentally alters this privilege escalation model. When an app requests admin rights, the system intercepts the request, prompts the user, and—upon confirmation—spawns the application inside a distinct, derived account possessing administrative rights. This architectural shift creates a far cleaner separation of duties, ensuring that compromised applications run within a heavily sandboxed perimeter rather than directly altering the primary user token.
Microsoft is positioning Administrator Protection strictly as an advanced security mitigation rather than a mere interface nuisance dialog, fundamentally changing how enterprise software handles local system permissions.
Under-the-Hood Security and Containerization Layers
While preview releases typically focus on non-security components ahead of patch day, this update package introduces several architectural additions beneath the OS shell. Microsoft Execution Containers (MXC) arrive in this build cycle, designed to place rigid guardrails around agentic AI workloads by running them inside isolated sandbox environments. Historical data across OS sandboxing shows that escape vulnerabilities inevitably emerge over time, but the integration signals a formal push toward isolating autonomous code execution.
At the cryptographic layer, the update introduces the post-quantum cryptography algorithm ML-KEM as a standalone option for Transport Layer Security (TLS) key exchange. This runs concurrently with the hybrid groups already supported by the OS network stack, future-proofing enterprise cryptographic handshakes against algorithmic decryption threats.
Search Enhancements and Deprecations
Concurrently tested across Insider channels, additional refinements target system navigation and legacy cleanup. A new fuzzy search implementation for applications and settings compensates for user typos and transposed keystrokes, retrieving correct matches even when queries contain structural errors. Furthermore, administrators will note the complete removal of the legacy command-line tool WMIC (Windows Management Instrumentation Command-line) from 24H2 and 25H2 installations, permanently phasing out the deprecated interface in favor of modern PowerShell modules and WMI scripting standards.
