Microsoft has dropped a September 2025 Patch Tuesday update that weighs as much as a small operating system. KB5065426—a mandatory cumulative update for Windows 11 24H2—pushes build numbers to 26100.6584 and lands with offline .msu files topping 3.8 GB. The payload is so large because it packs on-device AI models designed for Copilot+ PCs, yet it ships to every machine regardless of hardware. The upside? A long-requested full clock returns to the taskbar calendar flyout, Recall gets a new homepage, and Click to Do learns to teach.
The update surfaced on September 9, 2025, through Windows Update and the Microsoft Update Catalog. It brings a mix of visible UI polish, deeper AI scaffolding, and a storage footprint that has already triggered fresh deployment conversations in IT circles. Here is exactly what KB5065426 delivers, what it means for your machine, and how to handle the new multi-gigabyte reality.
Taskbar Calendar Gets the Full Clock Back
The most immediately gratifying change is the restored clock in the calendar flyout. Click the date and time on the taskbar, and you now see a large, clean time readout—nearly identical to the one Windows 10 users have enjoyed for years. For those who want it, a setting under “Adjust date & time” can also show seconds inside the flyout. The return addresses a complaint that has dogged Windows 11 since launch and delivers a small but genuine productivity win. No registry hacks, no third-party tools required.
Recall Homepage and Click to Do Tutorial
Copilot+ devices equipped with an NPU gain a new Recall “Home” experience. The page aggregates recent snapshots, top apps, and visited websites, making it easier to resume tasks from an hour or a day ago. Recall remains strictly opt-in and hardware-gated, but the Home page is automatically available after enabling the feature.
Alongside Recall, Click to Do receives an interactive, re-launchable tutorial. Users who dismissed the original walkthrough can now reopen it from the app’s “More options” menu. The guided flow demystifies the text-and-image assistant actions, which range from summarizing on-screen content to reverse image search—all processed locally on the NPU.
System Permission Prompts Go Full-Screen
Microsoft has redesigned how Windows asks for sensitive hardware access. When an app requests location, camera, or microphone, the consent dialog now appears as a full-screen prompt with the rest of the display dimmed. The change makes it significantly harder to accidentally click through a permission pop-up. While subtle, it tightens privacy hygiene and aligns with similar patterns on other platforms.
File Explorer Gets Cleaner Context Menus and AI Actions
File Explorer receives a visual divider below quick actions in the right-click menu, an attempt to organize an interface that still stretches across half the screen. More importantly, context menus now surface AI‑powered image actions—background removal, Bing Visual Search—that previously required launching separate apps. These actions are staged and can depend on Copilot entitlements or hardware support. On work and school accounts, the recommended section in File Explorer also shows colleague profile cards when hovering over a person’s icon.
Emoji 16.0, Lock Screen Widgets, and More Polish
Post-KB5065426, Windows 11 24H2 can render Emoji 16.0 characters, though the emoji panel itself does not yet include them. The lock screen widget experience gains drag-to-reorder customization and supports third-party widgets from the Microsoft Store, including a Phone Link widget that surfaces recent messages or notifications from iOS and Android.
Windows Hello sports a faster, cuter authentication animation that appears across lock screen sign-in, passkey prompts, and the Microsoft Store. Task Manager standardizes CPU metrics: the Processes tab and Performance tab now report identical workloads, aligning with third-party tools and the Game Bar monitor.
Settings gets an AI-powered search answer generator on Copilot+ PCs. Type a natural-language query like “how do I make my mouse cursor bigger?” and the NPU processes the request locally, returning a direct answer plus a toggle to adjust the setting immediately. A new privacy section under “Text and image generation” lists apps that have requested access to AI features. Windows Activation dialogs and other system prompts now appear in a more modern, coherent UI style.
The 4GB Elephant: Why the Offline Installer Is So Large
The Microsoft Update Catalog lists ARM64 offline installers at 3,685.4 MB and x64 clients at 3,811.1 MB. Those figures are unprecedented for a monthly cumulative update. The root cause is the inclusion of on-device generative AI models that power Copilot features on qualifying hardware. Microsoft ships these models inside the same .msu packages used by all architectures, regardless of whether the target PC supports them. While the models are not applied to unsupported devices, their presence inflates the download for everyone.
This packaging decision simplifies Microsoft’s servicing pipeline—one payload, feature-gated later—but it creates tangible side effects. Home users on metered connections face multi-gigabyte downloads. IT administrators must re-plan bandwidth and deployment windows. Machines with limited storage or slow I/O may churn for longer during installation. For large environments, peer caching (Delivery Optimization) and pre-populated distribution points become far more important.
SSD Corruption Fears: What Really Happened
A wave of user reports in August 2025 linked an earlier Windows 11 patch to SSD failures, with drives disappearing or corrupting data. Independent investigation subsequently pointed toward pre-release firmware on certain Phison-based SSDs, not the Windows update itself. Microsoft confirmed its internal testing found no connection between the August security update and storage drive failures. Production firmware versions were not implicated at the same rate. Nonetheless, the incident underscores a critical pre-patch step: verify that SSD firmware is a stable, manufacturer-recommended release. For KB5065426, there is no evidence that the update corrupts drives, but the lesson stands. Keep backups current and follow vendor guidance before rolling out any major cumulative patch.
Enterprise Implications: Bandwidth, Gating, and Policy
The checkpoint cumulative servicing model used by Windows 11 means offline installers may bundle both the servicing stack and the latest cumulative update. Administrators should follow Microsoft’s documented order when applying .msu files to images, and plan for gigabyte-scale transfers across distribution points.
Feature-gating adds another layer of variability. Two identical machines on Build 26100.6584 may display different AI features based on server-side flags, hardware capability (NPU), or user entitlement. Pilot rings must include representative hardware—Copilot+ Arm devices, standard x64 laptops, virtual machines—to catch differences before broad deployment. Helpdesk scripts should account for UI variations, such as the new clock, permission dialogs, and File Explorer menu changes, so that visible differences are not misdiagnosed as regressions.
Recall, despite being opt-in, raises compliance questions in regulated sectors. Organizations should assess whether snapshot functionality is appropriate on corporate devices, document any disablement procedures (using verified DISM commands after checking the exact feature name), and update privacy disclosures. Group Policy and MDM controls for Recall and other AI features should be validated in a representative test environment before enforcement.
A Thoughtful Update Worth a Careful Rollout
KB5065426 is not an emergency patch, but it is one of those updates that demands attention for its operational weight. For everyday users, the restored taskbar clock and smoothed-out File Explorer interactions provide immediate, visible relief. For those on Copilot+ hardware, the Recall homepage and Click to Do tutorial make AI assistants more approachable.
IT staff, however, inherit fresh complexity: a nearly 4GB offline installer, a firmware awareness obligation, and a fleet that will behave inconsistently even after a uniform patch level. The safest path forward is a measured, pilot-driven deployment: update firmware proactively, stage packages locally, and lean on Windows Update for automatic delivery to unmanaged devices. KB5065426 exemplifies Microsoft’s blended UI/AI trajectory—polishing the familiar while loading the platform with model-heavy capabilities that, for better or worse, every machine now carries.