Windows 11 Multimonitor Update: Open Notification Center on Any Monitor (KB5065789)

  • Thread Author
For years the little clock on a secondary display was a tease — visible but mute — and with the September 29, 2025 preview update Microsoft finally restored the ability to open the Notification Center and calendar flyout from any monitor in a multi‑monitor Windows 11 setup, delivering a long‑requested usability fix that many power users have been demanding since Windows 11’s first release.

Background / Overview​

Windows 11’s redesigned taskbar made a lot of visual and interaction changes when it debuted, and one small regression stuck: in multi‑monitor (Extend) configurations the system tray on secondary displays showed the time and date but didn’t respond to clicks to open the Notification Center or calendar flyout. That forced users to move the cursor back to the primary display to check notifications or a larger clock — a micro‑friction that compounded for people who work across several screens.
Microsoft packaged a practical correction into the September 29, 2025 non‑security preview update KB5065789 (OS builds 26200.6725 and 26100.6725), explicitly noting that “The Notification Center functionality is now available on secondary monitors. To open it, select the date and time in the system tray on the taskbar.” The KB also references an earlier August 2025 update (KB5064081) that reintroduced an optional larger clock with seconds inside the calendar flyout.
Independent tech coverage and community reporting corroborated the change during Insider flights and after the preview release — outlets and forums reported hands‑on confirmations and troubleshooting steps for early adopters.

What exactly changed in KB5065789​

The visible, practical fix​

  • Notification Center access on secondary monitors: Clicking the date/time entry in the system tray on any extended (secondary) monitor now opens the Notification Center and calendar flyout, matching the behavior on the primary display. This restores parity across monitors and eliminates the need to jump back to the primary screen to view or dismiss notifications.
  • Calendar flyout clock with seconds (opt‑in): With KB5064081 (August 2025) Microsoft added an option that displays a larger clock — including seconds — above the calendar grid in the Notification Center. That opt‑in setting is available in Settings > Time & language > Date & time > Show time in Notification Center, and when enabled the seconds clock appears in the calendar flyout on any monitor.

Packaging, builds, and distribution model​

  • Preview (non‑security) update: KB5065789 is a non‑security preview update (C/D‑release), published on September 29, 2025 for Windows 11 versions 25H2 and 24H2. The update includes a variety of quality improvements, feature roll‑outs, and fixes beyond the taskbar change.
  • OS builds: The KB lists OS builds 26200.6725 (25H2 branch) and 26100.6725 (24H2 branch) as the release targets for this preview.
  • Gradual rollout and server‑side gating: Microsoft explicitly uses a staged distribution model for previews and some feature rollouts. That means even after installing the KB package the server‑side feature flag that enables Notification Center on second displays may be rolled out progressively, so not every machine shows the behavior immediately. Allow 24–72 hours post‑install for activation in many cases.

How to get the feature today (practical steps)​

The change is delivered as an optional preview; here are safe, step‑by‑step instructions for testing it.
  • Back up or create a system restore point before testing optional previews.
  • Open Settings > Windows Update.
  • Ensure “Get the latest updates as soon as they are available” or equivalent preview opt‑in is enabled for your device (if required).
  • Look for Optional updates / Preview updates and install KB5065789 if it appears.
  • Reboot your PC (full restart) after installation.
  • If the Notification Center still doesn’t open from a secondary monitor, wait 24–72 hours for server flags to propagate or verify your device isn’t blocked by enterprise policies or compatibility settings.
If you prefer not to install preview packages, the safer path is to wait for the October cumulative release (Patch Tuesday), when preview fixes are typically folded into the mainstream cumulative update and reach wider availability. Independent coverage places the broader roll‑out in the October servicing window, though timing can vary by device.

How to enable the seconds clock (optional)​

  • Open Settings > Time & language > Date & time.
  • Toggle Show time in Notification Center to On.
  • Click the date/time in the system tray to open the Notification Center or calendar flyout; you should see the larger clock including seconds above the calendar grid if the option is enabled and the feature flag has been activated on your machine.

Why this matters — real world impact for multi‑monitor users​

Small interaction details are often dismissed as cosmetic, but they matter in daily workflows. Restoring Notification Center access on secondary displays delivers immediate, cumulative benefits:
  • Fewer context switches: Professionals who use secondary screens for chat, monitoring dashboards, or reference material no longer need to hop back to the primary screen to handle notifications.
  • Improved ergonomics: Cursor travel across large multi‑monitor rigs is reduced, which is a minor but constant ergonomic win.
  • Faster triage: Quick dismissals of low‑priority notifications or glancing at calendar appointments become less disruptive to flow.
  • Parity with prior expectations: Users migrating from Windows 10 or accustomed to multi‑monitor norms regain predictable behavior across displays.
Tech press has framed the change as a pragmatic quality‑of‑life restoration rather than a headline feature, and that characterization fits: the engineering scope is modest, the UX gain is tangible.

Critical analysis — strengths, shortcomings, and risks​

Notable strengths​

  • High value, low risk: The fix addresses a narrowly scoped UX regression with minimal surface area — it does not introduce a new subsystem or major redesign. That typically reduces the regression risk relative to feature‑heavy releases.
  • Official, documented delivery: Microsoft published the change in an official KB with clear build numbers and explicit instructions, removing ambiguity and allowing admins to plan tests.
  • Opt‑in granularity: The decision to keep the seconds clock off by default preserves the minimalist taskbar while giving users who need precise timing a toggle. This is a balanced approach to competing user preferences.

Shortcomings and remaining user requests​

  • Not a full taskbar restore: This fix doesn’t restore other widely requested capabilities — such as moving the taskbar to the top or sides natively, per‑monitor pinned apps, or labels. Those remain in the third‑party tool domain. Many users who hoped this change signaled a broader reversal of taskbar limitations will still be disappointed.
  • Staged activation means uncertainty: Server‑side gating can be confusing: users may install the preview and see nothing change until Microsoft flips a flag hours or days later. This complicates testing and makes user expectations harder to manage.

Risks and cautions​

  • Preview updates are non‑security: Optional previews are intended for testing and may include regressions. They are not substitutes for security patches and should not be deployed widely in production without validation. Enterprises should use pilot rings.
  • Third‑party shell mods: Systems running Explorer replacements or heavy UI customization (ExplorerPatcher, Start11, Windhawk, etc.) might experience conflicts after installing previews. Audit or temporarily disable such mods when testing. Community reports highlight occasional shell‑mod clashes that can be nontrivial to recover from.
  • ViveTool / forced flags: Community tools that forcibly enable feature flags exist, but using them is unsupported and can create difficult states for future updates. Avoid ViveTool on production machines.
  • Enterprise policies: Group policy, WSUS, or other management tooling can block optional previews or server flags; coordinate with IT before testing across managed fleets. Microsoft’s notes include servicing and WSUS fixes, so confirm compatibility.

Troubleshooting checklist (if you installed the preview but don’t see the change)​

  • Confirm KB5065789 shows as installed in Settings > Windows Update > Update history.
  • Reboot the device fully (not just restart explorer.exe).
  • Ensure your device is opted in to preview updates if that was a requirement prior to download.
  • Wait 24–72 hours — server‑side gating often delays visible activation.
  • Check for enterprise policies or WSUS that could hold back non‑security previews.
  • If you use UI mods or shell replacements, test on a clean system to rule out conflicts.
  • If the issue persists and you need to roll back, uninstall the LCU/preview via Settings or use a system restore image — follow standard rollback procedures for combined SSU/LCU packages carefully.

Deployment recommendations for IT admins​

  • Treat KB5065789 as a pilot candidate, not a broad release. Run it in a small ring and monitor app compatibility, shell extensions, and user reports for at least one business week.
  • Confirm your update management (WSUS, Intune, SCCM) handles preview/non‑security packages in a way that aligns with organizational patching policy.
  • Document rollback procedures and ensure backups/system images are available for endpoints where the preview is tested.
  • Communicate expectations to end users: explain the staged rollout behavior so users don’t assume the absence of the feature means the update failed.

Wider context: what this signals about Microsoft’s Windows 11 roadmap​

This restoration is consistent with a pattern: Microsoft launches a modernized, curated UX, then selectively restores legacy affordances that demonstrably improve productivity. The staged activation model is a strategic choice — it separates code delivery from feature activation, lowering risk while enabling rapid rollback if telemetry indicates issues. That architecture is good for stability but can be frustrating for users who want an immediate, deterministic outcome after installing an update.
The same KB also bundled broader improvements — from Click to Do enhancements to File Explorer and Narrator updates — highlighting that Microsoft typically delivers taskbar tweaks alongside other quality and feature updates rather than as isolated fixes. That multi‑feature packaging affects how organizations should approach testing: evaluate the whole update’s surface area rather than the single UX change.

What remains unverifiable or cautious to claim​

  • Any specific timetable for when every device will see the feature after installing KB5065789 is inherently speculative because Microsoft uses server‑side gating. Statements that promise universal availability on a particular date should be treated cautiously. Allow the 24–72 hour propagation window as a practical rule of thumb, but recognize exceptions.
  • Community claims about precise ViveTool IDs or hacky forcing methods are ephemeral and can vary between builds. Those techniques are unsupported and should be treated as experimental anecdotes unless validated by official Microsoft Insider documentation.

Quick reference — TL;DR (for power users)​

  • The Notification Center can now be opened from the date/time on any monitor’s taskbar with KB5065789.
  • The larger calendar clock with seconds is available via an opt‑in toggle introduced in KB5064081 (August 2025).
  • KB5065789 is a non‑security preview released on September 29, 2025 (OS builds 26200.6725 and 26100.6725). Expect staged activation.

Final assessment​

This is exactly the sort of modest, user‑centric correction that improves daily productivity without rewriting the platform: a small engineering change with an outsized practical effect for people who use two or more monitors. Microsoft has documented the change and provided clear paths to test it, which is an unusually neat resolution for a complaint that lingered for years after Windows 11’s initial redesign. That said, the conservative delivery model and the non‑security preview packaging mean the change will roll out at different speeds for different users — and it does not restore wider taskbar customizations that many users continue to want.
For enthusiasts and IT pros: test on non‑critical machines, follow the rollout guidance, and treat preview updates as experimental. For mainstream users: expect the change to arrive more broadly in the October cumulative releases, at which point adoption will be safer and more deterministic.

Conclusion
Restoring Notification Center access to secondary monitors in Windows 11 is a welcome, long‑requested fix delivered via preview with measured caution: it improves multi‑monitor ergonomics and workflow fluidity while preserving Microsoft’s phased rollout safeguards. Users who rely on multi‑monitor setups should welcome the change, but should also respect the preview’s test status — back up, pilot, and roll forward deliberately. The update is small but meaningful: one of those UX restorations that, while unspectacular, quietly makes the desktop a better place to work.

Source: ZDNET Your Windows 11 taskbar just got a major, long-requested feature - what's new