Microsoft shipped the KB5083631 optional non-security preview update on April 30, 2026, targeting Windows 11 versions 24H2 and 25H2 with a trio of long‑awaited fixes. File Explorer stability, the infamous FAT32 file size headache, and a stubborn Delivery Optimization memory leak all get addressed in this cumulative release. The patch lands as a C‑week preview, meaning it’s not pushed through Windows Update automatically — but it signals what will eventually become mandatory with the next Patch Tuesday.

What’s in KB5083631?

The update bumps the OS build to 26100.4825 (for version 24H2) and 26445.3930 (for version 25H2), according to Microsoft’s support document released alongside the rollout. It is classified as a C‑release, part of the regular non‑security update cadence that lets administrators and enthusiasts test incoming fixes before they’re bundled into the monthly cumulative security update. Apart from the highlighted reliability work, KB5083631 also incorporates all the fixes from the previous month’s optional update, KB5076624.

Microsoft’s change log is unusually crisp for a preview release. It lists three headline items:

  • File Explorer reliability improvements that address several scenarios where the shell would hang or crash during common operations.
  • A resolution for the long‑standing problem where copying files larger than 4 GB to FAT32‑formatted drives would silently fail or produce cryptic errors.
  • A memory‑management correction for the Delivery Optimization service, which was gradually consuming increasing amounts of RAM over time, especially on machines that handle large update downloads or peer‑to‑peer sharing.

File Explorer finally gets some attention

File Explorer glitches have been a thorn in the side of Windows 11 users since the OS launched. Reddit threads, Feedback Hub entries, and the Windows Forum have all documented a litany of annoyances: the navigation pane randomly resetting, the right‑click context menu loading with a delay, tabs duplicating or vanishing, and the entire process eating CPU cycles after the Desktop Window Manager restarted. The KB5083631 notes specifically mention that the update “addresses an issue where File Explorer stops responding when you use the Ctrl+Z undo operation in certain folders” and “fixes a race condition that could cause the window frame to hang after waking from sleep.”

Early adopters in the Windows Insider community report smoother interactions. One tester on the Windows Forum described the difference as “night and day — my Explorer windows used to freeze for three seconds every time I opened a network share, and that’s completely gone.” Another noted that the Start menu’s recommended files section, which relies on the same shell infrastructure, now populates faster. While the update doesn’t introduce new visual features, the reliability under the hood could make daily workflows significantly less frustrating.

Taming the 4 GB FAT32 barrier

FAT32 remains widely used on USB flash drives, SD cards, and external hard disks. Its maximum file size of 4 GB has been a known architectural limit for decades. However, Windows 11’s handling of that limit has been inconsistent and often unhelpful. Attempting to copy a file larger than 4 GB to a FAT32 volume would sometimes trigger a vague “Catastrophic failure” error, or the copy operation would appear to succeed while only writing a truncated file — a silent data loss scenario. The problem bit hard particularly when users tried to move ISO images, large video files, or database archives onto common removable media.

Microsoft confirms that KB5083631 introduces a new “pre‑copy check” that proactively blocks the operation with a clear, user‑friendly dialog. The message reads: “This file is too large for the destination’s file system. This drive uses FAT32, which supports files up to 4 GB in size. Try saving to an NTFS or exFAT drive instead.” The copy itself is stopped before any partial data is written, preventing corruption. Additionally, the command‑line robocopy tool now returns a dedicated exit code (16) when it encounters this condition, so scripting environments can handle it gracefully.

This change is a quality‑of‑life improvement rather than a fundamental filesystem update — FAT32 itself isn’t being expanded — but it aligns Windows with what third‑party formatting utilities have been doing for years. It eliminates a source of confusion for less technical users and closes one of the most upvoted Feedback Hub requests ever, which had gathered over 20,000 votes since 2021.

Plugging the Delivery Optimization memory leak

Delivery Optimization (DO) is the background service that downloads Windows updates, Microsoft Store apps, and other content, optionally using peer‑to‑peer sharing to reduce bandwidth. Since Windows 10, admins have observed that DO’s working set can balloon over time. In extreme cases, the Service Host process (svchost.exe) hosting DO was reported to consume more than 2 GB of RAM, especially on machines that act as update caches for an organization or that participate actively in the delivery network.

KB5083631 refactors the internal memory allocation routines of Delivery Optimization. Microsoft says it “resolved a leak where temporary buffers used for chunk validation were not released after a transfer session completed.” The fix particularly benefits devices with 8 GB or less of RAM, where the memory pressure from DO could trigger excessive paging and slow down the entire system. Community feedback indicates that after installing the update, idle memory usage for the DO service drops back to its expected baseline of 50–80 MB within minutes of a download finishing, even on heavily utilized peers.

This patch also tweaks the service’s CPU scheduling priority when the machine is on battery power, further reducing background drain. For users who had resorted to disabling Delivery Optimization entirely to avoid the leak, this update offers a reason to turn it back on and reclaim the bandwidth‑saving benefits without the performance tax.

How to install KB5083631

Because this is a C‑release preview, it will not download automatically. You must manually fetch it through Windows Update by opening Settings > Windows Update, optionally selecting “Check for updates,” and then finding the “Download and install” link under the optional updates section. Alternatively, you can download the standalone MSU package from the Microsoft Update Catalog and install it offline.

Microsoft recommends that consumers wait for the full Patch Tuesday rollout later in May 2026 unless they are experiencing one of the specific issues addressed. Enterprises and IT admins, however, should test early to validate compatibility with line‑of‑business applications. The update does not include any security fixes, so there is no urgency for general deployment.

Known issues and workarounds

No update ships without some caveats. Microsoft’s dashboard for KB5083631 lists two known problems at launch:

  • On a small number of devices with certain Realtek audio codecs, the sound may be muted after resuming from hibernation. A restart restores audio, and a driver update from the manufacturer is expected soon.
  • The Photos app may fail to launch if the “Open at login” option was enabled before the update. A fix is to reset the app through Settings > Apps > Installed apps > Photos > Advanced options > Reset.

Neither issue has a widespread footprint, and both have straightforward manual workarounds. Microsoft promises to address them in the cumulative update that will supersede KB5083631.

Community reaction and early performance feedback

The Windows Forum thread tracking this update has been unexpectedly positive. Users who installed KB5083631 within the first 48 hours praised the File Explorer fixes, with several noting that drag‑and‑drop operations between folders are noticeably snappier. One power user who runs a lab of twenty test machines commented, “The FAT32 dialog change alone saves me from explaining the 4 GB limit to my team twice a month.”

System stability metrics from the Insider Dev Channel and Beta Channel, where these changes were validated before broad release, show a 12% reduction in explorer.exe crashes compared to the previous month’s builds. While such telemetry must be taken with a grain of salt, it aligns with the subjective reports of a smoother UI experience.

Performance benchmarks run on a Ryzen 5 8640U laptop with 16 GB of RAM showed that the Delivery Optimization fix reduced total commit charge by roughly 300 MB after four hours of mixed update and Store activity. That’s a modest but meaningful improvement for devices that often hover near their memory limit.

What comes next?

The fixes in KB5083631 will be folded into the mandatory May 2026 Patch Tuesday update, likely on May 13, 2026. At that point, they will reach every unmanaged Windows 11 PC that receives automatic updates. Security improvements and possibly broader non‑security enhancements will also appear in that package. If you’re running the Enterprise or Education edition and rely on Windows Update for Business, you can defer these fixes for a maximum of 30 days from the mandatory rollout date.

Microsoft has not indicated that KB5083631 introduces any new diagnostic features or telemetry collection. The release aligns with the company’s recent focus on “polishing the fundamentals” — a mantra echoed by Windows chief Pavan Davuluri in a blog post discussing the roadmap for Windows 11 versions beyond 25H2.

For now, KB5083631 exemplifies the type of update that rarely makes headlines but directly improves the day‑to‑day experience of millions of users. Fixing a decades‑old FAT32 usability papercut, stopping a memory leak that quietly degraded performance, and hardening File Explorer might not be glamorous, but it’s the kind of engineering work that defines the maturity of an operating system.