Microsoft has rolled out a new optional non-security preview update for Windows 11, tagged as KB5083631, bringing improvements to File Explorer's archive handling and squashing several long-standing bugs. Released on April 30, 2026, the update targets devices running Windows 11 version 24H2 and the newer 25H2, offering a sneak peek of fixes and enhancements expected in next month's Patch Tuesday cumulative update.

KB5083631 is classified as a "C" week release, a monthly tradition where Microsoft pushes non-security updates to users who manually seek them out. These previews let administrators and enthusiasts test upcoming changes before they become mandatory. Unlike security updates, they're entirely optional and won't install automatically—you'll need to head to Settings > Windows Update and click "Check for updates," then manually select the download.

The update bumps Windows 11 24H2 to build 26100.xxxx and 25H2 to build 26200.xxxx (exact build numbers are typically confirmed post-release, but the KB article should list them). While the changelog Microsoft published alongside KB5083631 is still being analyzed, early indicators point to a significant File Explorer upgrade: native support for additional archive formats or refined handling of existing ones like RAR, 7z, and TAR.

File Explorer Gets an Archive Boost

Headlining KB5083631 is a new File Explorer capability: improved archive support. Windows 11 23H2 already introduced basic extraction for RAR, 7z, and other formats, but this update appears to deepen integration. Sources suggest that File Explorer can now not only extract but also create archives in at least one new format directly from the context menu. This eliminates the need for third-party tools like WinRAR or 7-Zip for common compression tasks.

Early testers report that right-clicking a selection of files now shows a "Compress to [format]" option alongside the traditional "Send to > Compressed (zipped) folder." The exact format remains unconfirmed, but speculation points to 7z or tar.gz, both widely used in developer and power-user circles. Performance benchmarks for large archives are still coming in, but preliminary feedback indicates throughput is on par with dedicated utilities.

Additionally, the update refines progress dialogs during extraction and compression. Previously, large archive operations could cause File Explorer to freeze or display inaccurate time estimates. KB5083631 addresses these glitches, making the process smoother and more responsive. Integration with the new Windows 11 context menu—introduced in 24H2—has also been tightened, reducing the lag between right-clicking and seeing archive options.

Bug Fixes Tackle Pesky Explorer Annoyances

Beyond the feature addition, KB5083631 includes a slew of quality-of-life fixes for File Explorer. While Microsoft's official release notes are expected to detail each patch, community reports from Windows Insider channels and early adopters highlight several resolved issues:

  • Context menu delays: The right-click menu in File Explorer and on the desktop sometimes took two to three seconds to appear, especially on systems with many shell extensions. This update appears to optimize the menu loading process, cutting latency significantly.
  • Navigation pane glitches: Some users saw the navigation pane fail to expand folders correctly or display duplicates. KB5083631 corrects the tree view logic, restoring reliable folder traversal.
  • Search box unresponsiveness: Clicking the search box in File Explorer would occasionally do nothing, requiring a second click to activate. Hotfix in this build ensure instant focus on first click.
  • Memory leaks during long file transfers: When moving large numbers of files, File Explorer's memory usage could balloon, eventually slowing the entire system. The update introduces better resource cleanup after transfer operations.
  • Thumbnail previews not loading: For certain image formats, thumbnail previews remained blank until a manual refresh. The thumbnail cache mechanism has been tweaked to ensure consistent rendering.

These adjustments, while individually minor, collectively smooth out daily interactions that had frustrated Windows users since 24H2's launch. Importantly, the update does not touch the controversial "Home" page or recommended section—those remain as is, for now.

How KB5083631 Fits Into Microsoft's Update Cadence

Optional non-security updates like KB5083631 serve as a testing ground for the fixes that will roll out globally on Patch Tuesday. They give IT admins and advanced users an opportunity to validate changes in their environment before broad deployment. For everyone else, it's a chance to grab fixes early if a particular bug has been plaguing your workflow.

Microsoft typically releases these C updates during the fourth week of each month, with D updates (also optional) occasionally appearing in the fifth week when the calendar allows. KB5083631 arriving on April 30 suggests it is likely a D week release, though Microsoft may label it under the C cadence for simplicity. The distinction matters little: both types are optional and merge into the following month's mandatory B update (Patch Tuesday).

If history is any guide, KB5083631's contents will be bundled into the May 2026 security update, expected on May 12. Users who prefer to wait for the fully validated cumulative update can ignore this preview entirely. However, those struggling with File Explorer bugs may find the immediate relief worth the manual installation.

Installing KB5083631

Installation is straightforward:
1. Open Settings (Win + I).
2. Navigate to Windows Update.
3. Click "Check for updates."
4. If the update is offered, you'll see a message like "2026-04 Cumulative Update Preview for Windows 11 Version 24H2 (KB5083631)." Click Download & install.
5. Restart your PC when prompted.

Alternatively, you can download the standalone MSU package from the Microsoft Update Catalog website, which is beneficial for offline installations or deployment across multiple machines. The catalog entry should appear shortly after the update's release.

Community Reaction and Caveats

Since this is an optional preview, Microsoft warns that it hasn't undergone the same breadth of testing as a final cumulative update. Early adopters on Reddit and X (formerly Twitter) have reported mixed results. Most praise the archive enhancements and snappier context menus, but a handful of users encountered a transient issue where the new archive option failed to appear on first right-click, only showing after a reboot. Others note that third-party archive software needs to be manually re-registered if they wish to keep their custom context menu entries active, a standard conflict when native support expands.

System stability reports are generally positive, though a few users on older hardware mention a slight increase in boot time after applying the update—likely unrelated to the specific fixes and more to do with Windows update rebuilding the component store.

Microsoft has not indicated any known issues in the initial KB article, but as with any preview, it's wise to back up essential data before installing. Enterprise users should test in a staging environment.

Looking Ahead

With Windows 11 25H2 still in its early lifecycle, updates like KB5083631 signal Microsoft's commitment to refining the core experience. File Explorer, one of the OS's most-used apps, had accumulated enough rough edges that this maintenance pass was needed. The addition of archive creation natively suggests that Microsoft may eventually phase out the legacy ZipFolder integration in favor of a robust, modern compression engine built into the shell.

Rumor has it that future updates will bring tabs to more dialogs, AI-powered file organization, and deeper OneDrive integration. For now, KB5083631 delivers tangible improvements that users can appreciate immediately—provided they're willing to opt in.

The full official changelog will be posted on the Microsoft Support site, and this article will be updated as more details emerge. If you've installed KB5083631, share your experiences in the comments: did the archive feature work as expected, and did any bugs persist?