Windows 11 Restores Secondary Display Notification Center and Seconds Clock (KB5065789)

Microsoft has quietly restored a pair of long‑requested taskbar behaviors to Windows 11 — the Notification Center (and calendar flyout) can now be opened from a secondary display on multi‑monitor setups, and the larger calendar clock with seconds has returned to the Notification Center — delivered as part of the optional preview update KB5065789 for Windows 11 versions 24H2 and 25H2.

Background​

For years, Windows power users have lived with a jarring inconsistency: on multi‑monitor systems the taskbar on secondary displays showed the time and date, but clicking them did not open the Notification Center or calendar flyout. That interactivity was only available on the primary display, forcing users with desks full of monitors to move the cursor across screens to check notifications or glance at a larger calendar clock. Windows 10 had the more intuitive behavior; when Windows 11 first shipped, Microsoft’s redesigned taskbar removed or altered several small but useful features — and multi‑monitor notification access was one of the most frequently mentioned omissions.
Microsoft’s recent preview update, KB5065789 (released as a non‑security preview on September 29, 2025, and staged for inclusion in the October patch cycle), reunites Windows 11 with these elements. The update is published for both the 24H2 and 25H2 branches, reflecting Microsoft’s shared codebase between those two servicing channels. Microsoft’s support notes document KB5065789 as a preview that includes a broad set of quality fixes and feature roll‑outs delivered in a gradual fashion.

---

What changed in KB5065789​

Notification Center and calendar flyouts on secondary displays​

One of the most visible changes is functional parity for the system tray across multiple monitors: clicking the date/time area on a secondary display now opens the Notification Center and calendar flyout — the same behavior users already had on the primary display. This is a user‑experience fix more than a technical overhaul, but its impact on productivity for people using two or more monitors is immediate. Tech press coverage and early Insider reporting confirm the change landed in Dev/Beta preview builds and has been folded into the preview KB for general testing.

Calendar flyout clock with seconds​

Windows 11 now offers the larger calendar flyout clock that was absent from early Windows 11 builds. The flyout can show a larger clock display with seconds — a feature many longed for after the Windows 11 taskbar initially removed several Windows 10 conveniences. The clock is off by default and is controlled by a new toggle in Settings: Settings > Time & language > Date & time > Show time in Notification Center. When turned on, the calendar flyout displays the time (including seconds) above the date and calendar grid. Several Windows how‑to sites and Insider reports document the new setting and how to enable it.

Delivery channel and rollout model​

KB5065789 is a non‑security preview (C/D‑release) update that Microsoft published on September 29, 2025. Microsoft uses a staged rollout model: the preview is available as an optional install (visible when users enable “Get the latest updates as soon as they are available”), and fixes and features may be gradually enabled via A/B testing or server‑side feature flags. Microsoft’s documentation and Windows Insider notes emphasize this gradual activation model; consequently, even after installing KB5065789, some users may not see the change immediately. Microsoft plans to include the preview fixes in the October Patch Tuesday cumulative releases as well.

---

How to get the features now — step‑by‑step​

There are two paths: the supported route (install the preview update and opt in to early feature flights) and the power‑user route (use third‑party tooling to force‑enable features that are currently gated). The supported path is recommended for most users; the second route carries risk and should be used only by experienced users who understand the implications.

• Supported (recommended) method
• Open Settings > Windows Update.
• Toggle on Get the latest updates as soon as they are available (this opt‑in exposes optional preview releases and feature flights).
• In Optional updates available, locate and install KB5065789 (September 29, 2025 preview / October patch preview).
• After installation and a reboot, open Settings > Time & language > Date & time and enable Show time in Notification Center if the option is present.
• Verify behavior on a secondary display by clicking the date/time area on the secondary taskbar. If the Notification Center or calendar flyout appears, the change is active.
• Power‑user (ViveTool) method — caution advised
• Some Insider and preview features are still hidden behind feature IDs used in Microsoft’s controlled rollouts. Community tools such as ViveTool (open source) can toggle these feature flags, but using them bypasses Microsoft’s controlled activation and may cause unexpected behavior.
• Commonly reported ViveTool usage to expose the Notification Center clock includes commands like:
• vivetool /enable /id:42651849
• (If the first ID doesn’t surface the feature, users have reported success with /id:48433719 as an additional toggle.)
• After enabling, restart explorer.exe or reboot, then check Settings > Date & time to toggle Show time in Notification Center.
• Important caveat: using ViveTool modifies hidden feature flags and is not supported by Microsoft; it can complicate troubleshooting or update rollbacks. Back up data and use a test device where possible.

---

Why this matters: practical and UX implications​

• Multi‑monitor users win back a small but meaningful time‑saver: no more hunting for primary display focus when checking notifications or the calendar. For professionals using full‑screen apps, trading between screens, or working with reference screens, the restored behavior reduces friction and cursor travel time.
• The return of the calendar clock — particularly the option to show seconds — matters for roles that need precise timing (e.g., broadcasters, real‑time trading desks, time‑sensitive testing). Previously those users relied on third‑party tools or kept a separate clock utility pinned to the desktop.
• The change illustrates Microsoft’s incremental approach to restoring or reintroducing legacy behaviors where user feedback is strong. It’s a reminder that some UI design choices made at initial release were intentional but continue to be tunable based on cumulative feedback.

---

Enterprise and IT admin considerations​

• KB5065789 is a preview (non‑security) update intended for testing and validation. Enterprises should not deploy optional preview updates en masse without proper QA, because preview packages can include experimental features or be tied to enabling server‑side flags that aren’t yet fully validated in corporate environments. Microsoft’s documentation explicitly marks these releases as preview and indicates that they roll into the formal Patch Tuesday cumulative releases. IT pros should treat KB5065789 as an optional test release and wait for the targeted Patch Tuesday build for broad deployment.
• The “Get the latest updates as soon as they are available” toggle can cause devices to receive out‑of‑band or experimental updates. For managed devices, administrators should avoid toggling this for production systems and instead validate changes in a test ring first.
• If enterprises depend on specific multi‑monitor behaviors or have custom tooling that interacts with the taskbar or Notification Center, testing is essential. Small UI changes can ripple into automation tools, remote‑control software, or custom shell extensions.

---

Risks, known issues, and cautions​

• Preview updates are optional and sometimes buggy. Microsoft-run forums and Q&A threads show users encountering installation or post‑update issues with preview builds. If you’re not troubleshooting‑savvy, skip preview installs until the changes reach the regular cumulative update channel.
• Using ViveTool to force enable hidden features is a community technique, not an official Microsoft support path. ViveTool modifies internal feature flags and can complicate future updates or support calls. Use it only on test machines and understand how to undo changes (vivetool /disable /id:<ID> or a full reset).
• Feature rollout variability: even after installing KB5065789, the Notification Center clock or multi‑monitor behavior may still be disabled for your device because Microsoft activates features server‑side and ramps them gradually. Do not assume that installing the KB will immediately enable everything for all machines.
• Minor UI regressions or accessibility regressions could surface; Microsoft’s gradual approach intends to catch these, but early adopters may encounter stray issues. Testing with assistive technologies is recommended if devices are used by people with accessibility needs.

---

Alternatives and complementary tools​

If the native options still don’t meet a user’s needs — or if they prefer more customization than Microsoft offers — there is a thriving ecosystem of taskbar and tray mods and utilities:

• Windhawk mods: Windhawk hosts a popular Taskbar Clock Customization mod that can show custom formats, news, weather, and performance metrics like CPU and RAM in the clock area; it’s widely used by enthusiasts seeking deeper customization than Windows natively provides. Windhawk is a lightweight mod framework and its taskbar clock mod specifically lists features for news feeds, weather, and performance metrics. Users should evaluate the stability and review the mod’s source code before installing.
• HWiNFO, Core Temp, and similar utilities: these well‑established system‑monitoring tools can push sensor values (temperatures, loads) to the system tray. They’re a safer path to see CPU/GPU metrics in the tray without modifying Windows internals. HWiNFO supports adding sensor readings directly to the tray area.
• Rainmeter and third‑party skins: for users who want rich desktop displays with clocks, news, and telemetry, Rainmeter remains the go‑to. It provides powerful, networked widgets that can sit alongside the taskbar.

---

Technical notes and verification​

• Microsoft’s support page for the September 29, 2025 preview documents KB5065789 as the optional non‑security release for Windows 11 versions 24H2 and 25H2, and lists the build numbers associated with the preview release. That page is the authoritative KB entry for the update.
• Independent reporting from outlet coverage and Windows Insider announcements documented the change in multi‑monitor Notification Center behavior in preview and early Beta/Dev builds prior to the KB’s publication, corroborating the timeline that the feature was tested in Insiders and then included in the preview KB.
• Multiple how‑to and technical blogs tested and published the specific Settings toggle name and guidance to enable the calendar flyout clock — commonly quoted as Show time in Notification Center under Settings > Time & language > Date & time. Those guides also reported the setting is off by default and that the feature is gated and may require opt‑in or a feature‑flag unlock on some devices.
• Community documentation and Insider posts verify the ViveTool IDs commonly quoted for earlier Insider builds (for example, id:42651849 and id:48433719 to expose the flyout clock). Note that feature IDs can change between builds and over time as Microsoft iterates — so these IDs should be treated as ephemeral and may not apply to every release. Proceed with caution and cross‑check latest Insider guides if using ViveTool.

---

Practical troubleshooting checklist​

• If you installed KB5065789 but don’t see the feature:
• Confirm the KB actually installed (Settings > Windows Update > Update history).
• Ensure Get the latest updates as soon as they are available was toggled on prior to installing the preview; some preview content is gated to that opt‑in.
• Reboot after installation; some features require explorer.exe restart or a full reboot.
• If the setting is still missing, wait a few days — Microsoft’s feature rollouts are often controlled server‑side.
• For power users testing ViveTool, enable the commonly reported IDs, reboot, then check Settings > Date & time. If issues arise, disable the IDs or uninstall the preview and roll back to the last stable configuration.

---

The broader picture: product design, listening to feedback, and small UX wins​

This tiny but visible reversal — returning a calendar flyout clock and restoring Notification Center access on secondary displays — is an instructive case study in product design and community feedback. Microsoft’s initial Windows 11 taskbar choices embraced a minimalist, curated approach, but the persistence of community demand for a few legacy behaviors shows that small affordances can have outsized practical value.
The release also exposes the tradeoffs Microsoft faces: balancing a stable, unified design language with the need for configurability and power‑user preferences. The company’s current strategy — release a reimagined design, then selectively restore high‑value legacy affordances — appears to be the path forward. For end users, these changes are welcome and demonstrate Microsoft continues to iterate thoughtfully on the Windows 11 experience.

---

Conclusion​

KB5065789’s reintroduction of secondary‑display Notification Center access and the calendar flyout clock is a small but meaningful restoration of lost functionality that directly benefits multi‑monitor users and anyone who values a quick, glanceable clock. The features are packaged in a preview update and will be rolled into the formal October Patch Tuesday servicing, but Microsoft’s gradual activation model means not every device will see the behavior instantly. For most users, the safest path is to install the preview only on test machines or wait for the cumulative release; advanced users may force visibility with ViveTool or choose mature third‑party mods such as Windhawk or sensor utilities like HWiNFO when they need deeper customization. This is an incremental, pragmatic win for Windows 11 usability — a reminder that sometimes the smallest features deliver the biggest daily benefits.

---

Source: Neowin A long-requested taskbar feature finally makes it to Windows 11

 

[ChatGPT]

Microsoft has quietly restored a small but widely requested taskbar behavior: you can now open the Notification Center and calendar flyout from a secondary display in Windows 11, and the calendar flyout can optionally show a larger clock with seconds — delivered as part of the non‑security preview update KB5065789 for Windows 11 versions 24H2 and 25H2.

Background​

For users who run multi‑monitor setups, the Windows 11 taskbar has been a frequent point of friction. In earlier Windows 11 builds the taskbar on secondary displays showed the date and time but did not open the Notification Center or calendar flyout when clicked — a behavior that forced users to move the cursor to the primary display to see notifications, respond to toasts, or get a larger clock view. Windows 10 did not have this limitation, and the inconsistency became one of the longer‑running usability complaints about the Windows 11 redesign.
Microsoft packaged this change in the September 29, 2025 non‑security preview identified as KB5065789 (OS builds 26200.6725 and 26100.6725 for version 25H2 and 24H2 respectively). The update is delivered as an optional preview (C/D‑release) and uses a gradual, staged rollout model; feature activation may also be controlled server‑side, so not every machine will see the change instantly after installing the package.

---

What exactly changed in KB5065789​

Notification Center on secondary displays — parity restored​

• Clicking the date/time area in the taskbar on a secondary monitor now opens the Notification Center and calendar flyout just like on the primary display.
• This fixes the awkward, non‑interactive date/time shown on secondary taskbars and restores parity across displays for a basic system interaction.

This is primarily a user‑experience fix, but its practical benefits are immediate for anyone who keeps a multi‑monitor desktop: no more wiping a hand across your ergonomic mouse and returning to the primary display just to glance at notifications. Independent coverage and Microsoft’s KB notes confirm this behavior was included in preview builds and folded into the preview KB.

Calendar flyout clock with seconds — an opt‑in restoration​

• The calendar flyout now optionally displays a larger clock with seconds above the date and calendar grid, returning a visual that many users preferred from Windows 10.
• This clock is off by default; users must enable it in Settings under Time & language > Date & time by toggling the new Show time in Notification Center option.

This restores a glanceable, high‑precision time view for scenarios where seconds matter (broadcasting, testing, time‑sensitive operations) while keeping the cleaner taskbar appearance for everyone else. The setting path and toggle name appear in documentation and hands‑on reporting for the preview.

---

Verification and rollout: how this is being delivered​

Microsoft uses staggered delivery for preview and feature flights. KB5065789 was published as the September 29, 2025 preview update and appears in the Optional updates area of Windows Update when you opt in to early preview content. The support page explicitly describes the update as a preview (non‑security) release for Windows 11 24H2 and 25H2, and the change log and highlights document the quality fixes and small feature roll‑outs included.
Practical steps to receive the preview and check feature status:

• Open Settings > Windows Update.
• Toggle on Get the latest updates as soon as they are available to enable preview/optional releases.
• Look for Optional updates available and install KB5065789 (September 29, 2025 preview).
• Reboot, then open Settings > Time & language > Date & time and toggle Show time in Notification Center if present.
• Verify secondary display behavior by clicking the date/time in the secondary taskbar. If the Notification Center or calendar flyout appears, the feature is active.

Bear in mind Microsoft’s staged activation model: even after installing the preview package, features may remain gated and roll out progressively. If you don’t see the change immediately, check Update history to confirm KB5065789 installed and allow several days for server‑side flags to propagate.

---

Why this matters — practical value and UX reasoning​

Small interface inconsistencies are easy to dismiss, but they compound in productivity environments. For multi‑monitor users, the inability to open the Notification Center from anywhere but the primary display was a daily friction point: checking a missed meeting reminder, dismissing a toast, or glancing at the full calendar required an extra mouse movement. Restoring tap/click parity:

• Reduces micro‑interruptions and context switches.
• Improves accessibility for users who rely on keyboard and pointing device workflows across displays.
• Returns a long‑missed convenience (the larger clock) without forcing everyone to show seconds in the taskbar.

From a product design standpoint, this move shows Microsoft listening to persistent community feedback and selectively restoring legacy affordances that deliver practical value without undoing Windows 11’s overall visual direction.

---

Power users: options, caveats, and advanced forcing methods​

Some preview features are still gate‑kept by server flags or feature IDs. The community has identified ViveTool IDs used historically to force these features, and power users sometimes rely on this open‑source utility to expose hidden functionality. Common caveats:

• Feature IDs can change between builds and over time; commands that worked in one Insider flight may not work later.
• ViveTool usage bypasses Microsoft’s staged activation and can cause instability or unsupported states.
• Use ViveTool only on test machines, not in production or domain‑joined workstations without acceptance testing.

If you elect to try ViveTool, make sure you understand the risk, record any changes you make, and be comfortable rolling back updates if necessary. Community guides have mentioned specific IDs for the Notification Center clock in prior flights, but treat these as ephemeral and verify against the latest Insider notes before execution.
Alternative, safer routes for tray telemetry and telemetry‑style features (CPU/GPU in the clock area):

• Use established system‑monitoring tools (HWiNFO, Core Temp) that can push sensor values to the system tray.
• Consider Rainmeter or desktop widgets for richer, customizable on‑screen telemetry that doesn’t touch system internals.
• Use maintained Explorer shell mods (ExplorerPatcher, StartIsBack clones) with caution — these can break with OS updates and rely on reverse‑engineering the shell.

---

Administrative considerations and deployment guidance​

For IT administrators and enterprise environments, even small UI changes deserve cautious handling. KB5065789 is a preview, non‑security release; deploy as follows:

• Pilot the update on a representative hardware set, including multi‑monitor setups and any machines running critical apps that interact with shell or notification APIs.
• Validate update installation and confirm post‑install behavior: Notification Center access on secondary displays, calendar clock toggle presence, and any other KB fixes that intersect with your environment.
• Maintain recovery planning: back up BitLocker keys, confirm recovery media, and update deployment images if you roll the preview into broader test rings.
• Consider deferring preview installs on production builds; wait for the cumulative October Patch Tuesday roll‑up if you prefer fully supported cumulative packaging.

Microsoft’s documentation emphasizes gradual rollout and staged activation; your estate may see feature differences across units during a preview phase. Plan for that variance and include it in your change control and communications to end users.

---

Risks, compatibility issues, and things to watch​

While this update is small and primarily UX focused, there are a few risks and compatibility considerations:

• Server‑side gating: Microsoft may enable features slowly; inconsistent behavior across endpoints can create helpdesk noise.
• Shell‑mod interference: Third‑party tools that modify the shell or system tray may conflict with the updated behavior, causing unexpected outcomes.
• Driver/overlay interactions: Multi‑monitor setups often rely on GPU drivers and multi‑display drivers; the KB includes fixes for some Hyper‑V and multi‑display gaming performance scenarios but administrators should validate graphics drivers and overlays after installing preview packages.
• ViveTool and forced flags: Forcing hidden features can leave machines in unsupported states and expose instability. Treat those actions as forensic and experimental.

If you experience problems after installing a preview package, Microsoft’s guidance is to uninstall the LCU using DISM if necessary and rely on documented rollback procedures; however, note that combined SSU+LCU packages may complicate uninstall paths, so test rollback procedures before broad deployment.

---

Practical troubleshooting checklist​

If you installed KB5065789 and don’t see the calendar clock or secondary Notification Center behavior:

• Confirm installation: Settings > Windows Update > Update history to check for KB5065789.
• Confirm preview opt‑in: Ensure Get the latest updates as soon as they are available was toggled before installation.
• Reboot: Some changes require a full restart or an explorer.exe restart to appear.
• Wait: Microsoft often enables staged features via server flags. Allow 24–72 hours post‑install for flags to propagate.
• Safe forcing (advanced): If you understand the risks, verify the current community‑reported ViveTool IDs and test on a non‑production device only. IDs and behavior can change between builds — treat them as experimental.

---

The broader picture: small changes, big signals​

Restoring the Notification Center to secondary displays and offering an opt‑in seconds clock is modest in engineering scope, but significant in message. It signals:

• Microsoft is willing to selectively restore high‑value legacy behaviors that materially improve everyday workflows.
• The company continues to use staged feature flights and previews to validate changes across the diverse Windows hardware and software ecosystem.
• Small UX fixes can reduce friction for power users, and Microsoft’s iterative approach shows responsiveness to persistent user feedback.

From a product strategy angle, this is a pragmatic balancing act: keep the cleaner Windows 11 aesthetic while offering toggles and targeted restorations that preserve productivity for power users.

---

What users should do now​

• Casual/home users: Wait for the cumulative October release to get the feature in a broadly rolled‑out, fully tested package. If you are curious and comfortable with optional previews, opt in and install KB5065789 on a secondary or test device.
• Power users: Test the preview on a non‑critical machine; consider ViveTool only as a last resort and be prepared to roll back.
• IT admins: Pilot the preview within a controlled ring, validate key business applications and shell interactions, and update deployment/runbooks to account for potential UI differences during the staged rollout.

---

Bottom line​

KB5065789 restores a small but meaningful convenience to Windows 11: Notification Center and calendar flyout accessibility on secondary displays and an opt‑in calendar clock with seconds. The change reflects Microsoft responding to a persistent usability complaint and delivering a practical fix via a preview update and staged activation. For multitasking professionals and multi‑monitor enthusiasts, this is a welcome daily productivity win — simple, unobtrusive, and exactly the kind of incremental improvement that pays dividends in everyday use.

---

(If you applied the preview and want a short checklist to confirm and troubleshoot these exact changes on your hardware, follow the five‑step "How to receive the preview and check feature status" list above and use the practical troubleshooting checklist if the behavior doesn’t appear.)

---

Source: Neowin A long-requested taskbar feature finally makes it to Windows 11

 

[ChatGPT]

Windows 11’s long-standing multi-monitor friction — the inability to open the Notification Center from a secondary display — has finally been addressed in Microsoft’s September 2025 preview update, KB5065789, which also restores an opt‑in, larger clock (including seconds) inside the Notification Center’s calendar flyout.

Background​

For many power users, the smallest UI details have outsized effects on daily productivity. After the Windows 11 taskbar redesign in 2021, several small conveniences from Windows 10 were removed or altered — among them the ability to open the Notification Center (calendar and notifications flyout) by clicking the clock on any connected display. Instead, the system required interaction on the primary display, forcing repeated cursor travel for multi‑monitor workflows. This behavior became a frequent complaint on community forums and Insider channels, driving the development and testing of a fix over several preview builds.
Microsoft packaged the change in a non‑security preview (C/D‑release) update, KB5065789, published as an optional preview on September 29, 2025. The package targets Windows 11 versions 24H2 and 25H2 and is being distributed via Microsoft’s staged rollout model, which includes server‑side gating and gradual activation. That means the code can arrive on a device but the feature may remain disabled until Microsoft flips a remote flag.

---

What changed in KB5065789​

Notification Center on secondary displays: parity restored​

The main usability fix is straightforward: clicking the date/time area in the system tray on a secondary monitor now opens the Notification Center and calendar flyout the same way it does on the primary screen. This restores functional parity across displays and removes an often‑complained about impediment for multi‑monitor users. Early Insider reports and hands‑on coverage confirmed the behavior in Dev/Beta flights before the preview package was released to a broader test audience.
Why this matters:

• Reduces unnecessary cursor travel and micro‑interruptions for users working across multiple screens.
• Improves accessibility and ergonomics for setups where the primary display is not the user’s focus.
• Aligns Windows 11 behavior more closely with the intuitive experience users had in Windows 10.

Full Notification Center clock with seconds (opt‑in)​

KB5065789 also introduces a toggle in Settings to show the larger, Windows 10‑style clock (including seconds) in the expanded Notification Center flyout. The toggle is found at Settings > Time & language > Date & time > Show time in Notification Center and is off by default. When enabled, the calendar flyout displays a more prominent time readout (HH:MM:SS) above the date and calendar grid, and the flyout can be collapsed for a minimal view with notifications above.
Practical use cases for the seconds display include:

• Time‑sensitive work such as broadcasting, testing and measuring script runtimes.
• Synchronization checks where second‑level granularity helps verify timing behavior.
• Users who prefer a glanceable, larger clock without enabling seconds visibly in the taskbar itself.

---

Hands‑on: how this changes daily workflows​

Small UX reversals like these can feel trivial in isolation, but they compound in real workflows. Multi‑monitor users often operate in full‑screen or reference modes on the secondary display and rely on glanceable information without breaking flow.

• With Notification Center opening on the active (secondary) screen, calendared reminders, toasts, and actionable notifications can be reviewed or dismissed without returning to the primary display. This reduces interruptions and maintains momentum during focused work sessions.
• The larger Notification Center clock is useful when seconds matter but the taskbar must remain visually minimal. It’s an elegant compromise: a subtle taskbar, plus an on‑demand detailed clock in the Notification Center.

Practical example:

• Compose or review a document on the secondary monitor.
• Click the secondary taskbar clock to open the Notification Center there.
• Dismiss a reminder or start a Focus session without moving the workflow back to the primary display.

This flow is now possible without third‑party workarounds that many users previously relied on.

---

How to get the features today​

Supported (recommended) route​

• Open Settings > Windows Update.
• Toggle on Get the latest updates as soon as they are available to opt into preview/optional releases.
• Install the optional preview identified as KB5065789 (published September 29, 2025).
• Reboot the device.
• Confirm the toggle Settings > Time & language > Date & time > Show time in Notification Center is available and enable it if desired.
• Verify by clicking the date/time on a secondary display; the Notification Center or calendar flyout should appear.

Note: Because Microsoft uses staged rollouts and server‑side flags, the feature may not activate on every machine immediately after installing the preview even when the package is present. Allow 24–72 hours for server flags to propagate, and check Update history to confirm that the preview LCU successfully installed.

Power‑user route (advanced, unsupported)​

Community tooling such as ViveTool can toggle hidden feature flags in Insider and preview builds. Experienced users have reported ViveTool IDs that previously surfaced the Notification Center clock or related features, but these IDs are ephemeral and can change between builds. Using ViveTool bypasses Microsoft’s staged testing and is not supported; it may complicate troubleshooting or update rollbacks. Only use such tools on non‑critical test machines after backing up system state.
Cautionary points:

• ViveTool usage may leave a machine in an unsupported state.
• Feature IDs change and community‑published IDs may not work for newer builds.
• Forced flags can interact poorly with enterprise policies or shell‑mod utilities.

---

Technical verification and rollout model​

KB5065789 is described in Microsoft’s support notes as a non‑security preview for Windows 11 24H2 and 25H2. The preview was published on September 29, 2025 and is intended as an optional test build ahead of inclusion in the mainstream October patch cycle. Microsoft’s staged rollout model means the update is visible in Optional updates for devices opted into early releases, but individual features can be gated server‑side or enabled gradually via A/B testing. This is consistent with the company’s recent approach: ship the code, then activate the feature selectively to gather telemetry and reduce wide‑scale disruption.
Build numbers quoted in community coverage for the preview and associated Insider flights are in the 26xxx range for 25H2 and 24H2 channel variants. Some community posts reference specific OS builds tied to the preview (for example, builds 26200.6725 and 26100.6725 were noted in early hands‑on reporting), but those build identifiers can vary by channel and date as Microsoft iterates. Treat build numbers as useful signals but verify against Windows Update > Update history after installing.

---

Enterprise and IT admin considerations​

While this update is primarily a UX refinement, enterprise teams should exercise standard caution with preview, optional, or staged updates.

• Pilot first: Deploy KB5065789 within a controlled test ring that represents the range of hardware, GPU drivers, shell extensions, and multi‑monitor configurations used in the organization. Validate remote‑control tools, custom shell extensions, and any automation that interacts with the system tray or notifications APIs.
• Avoid enabling preview opt‑in broadly on production devices. The toggle “Get the latest updates as soon as they are available” can surface out‑of‑band content and experimental feature code.
• Expect variance: Microsoft’s server‑side gating means different devices in the same estate can behave differently post‑install. Update runbooks and helpdesk guidance accordingly.
• Rollback readiness: Test rollback procedures for the combined SSU+LCU packaging; uninstalling preview packages or rolling back feature flags can be more cumbersome than standard cumulative updates. Document steps and test them before a broad pilot.

---

Risks, caveats, and known limitations​

• Server‑side gating: Because features may be enabled remotely, administrators and end users may see inconsistent behavior across devices, creating potential helpdesk noise.
• Shell‑mod conflicts: Third‑party tools that alter the taskbar, system tray, or Explorer shell (custom launchers, ExplorerPatcher, StartIsBack, Rainmeter skins that reposition UI elements) may conflict with the updated behavior. Test these interactions specifically.
• Driver interactions: Multi‑monitor behavior can be affected by GPU drivers and manufacturer display utilities. Confirm driver compatibility, especially on older hardware.
• ViveTool ephemeral IDs: Community‑reported feature‑flag IDs are useful investigative leads but are not authoritative. IDs can change between Insider flights and are not supported for production systems; treat them as experimental and verify with current Insider documentation before attempting.
• No security fixes in preview: This preview is explicitly non‑security. Do not treat it as a security patch and prioritize it only if the functional changes are necessary for workflows or testing.

---

Why Microsoft restored these behaviors (analysis)​

Restoring the Notification Center’s multi‑display interactivity and reintroducing an optional seconds clock are examples of pragmatic product design: Microsoft is preserving Windows 11’s visual minimalism while selectively restoring legacy affordances that have clear productivity upside. The company is balancing a unified design language with the option to tailor the OS for power users.
Key strategic observations:

• Listening to feedback: The changes show responsiveness to persistent community requests rather than wholesale design reversals.
• Incrementalism: Microsoft’s staged activation model lets the company collect telemetry and opt users into restorations without forcing a universal rollback to older UX paradigms.
• User segmentation: By making the seconds clock opt‑in, Microsoft satisfies users who need precise timing while keeping the default taskbar clean for the majority.

This approach reduces design churn while acknowledging that small features can have a disproportionate effect on daily productivity for certain user groups.

---

Recommendations for users​

• Home/power users who depend on multi‑monitor ergonomics: Install the preview on a test device if the secondary Notification Center behavior or the seconds clock materially improves workflow. Otherwise, wait for the cumulative October roll‑up for broader, more stable delivery.
• IT administrators: Pilot KB5065789 across a representative test ring that includes machines with shell mods, GPU vendor utilities, and multi‑monitor setups. Update helpdesk documentation to explain staged rollouts and the possible need to wait for server flags to propagate.
• Power users tempted by ViveTool: Use ViveTool only on non‑critical devices and after taking a full backup. Verify any community‑published feature IDs against current Insider build notes because IDs may have changed.

---

Practical troubleshooting checklist​

If the feature doesn’t appear after installing KB5065789:

• Confirm the preview installed: Settings > Windows Update > Update history.
• Ensure the device had Get the latest updates as soon as they are available turned on prior to attempting to install optional previews.
• Reboot the device fully (not just restart explorer.exe).
• Allow time: wait 24–72 hours for server‑side flags to propagate.
• If comfortable and knowledgeable, consult current Insider documentation before attempting advanced feature‑flag tools like ViveTool.

---

Conclusion​

KB5065789 represents a thoughtful, incremental restoration of two widely requested behaviors in Windows 11: opening the Notification Center from secondary displays and displaying a larger, opt‑in clock with seconds in the calendar flyout. Neither change is flashy, but both address real daily friction for multi‑monitor users and those who depend on second‑level timing. Microsoft’s staged rollout and preview packaging mean adoption should be deliberate: test first, expect variance, and avoid forcing feature flags on production systems.
These fixes illustrate a broader pattern in Windows development: the platform continues to evolve via a mix of ambitious new features and small, pragmatic restorations that preserve user productivity without abandoning a modern visual direction. The result is a more flexible Windows 11 that can remain clean by default while giving power users the tools they need when they want them.

---

Source: Windows Latest Windows 11's Notification Center opens on secondary display, gets a clock and more