Microsoft’s KB5067036 Release Preview lands as a pragmatic mix of polish, AI hooks, and reliability fixes — most immediately visible in a new Recommended files strip inside File Explorer Home, new StorageProvider APIs for cloud integrations, and a bundle of bug fixes that address long‑reported Explorer regressions.
KB5067036 is a non‑security, Release Preview update for Windows 11 that updates servicing binaries for both the 24H2 and 25H2 servicing lanes while exposing a set of user‑facing features through staged, server‑side enablement. Microsoft published the preview to Insiders and Release Preview participants as builds for the two servicing branches; the package has appeared under OS builds 26100.xxxx (24H2) and 26200.xxxx (25H2) with slightly different build revisions during the rollout window.
The release is intentionally split between:
Key behaviours:
Benefits:
Positives:
Action plan summary:
Conclusion: For power users and administrators willing to do the legwork, KB5067036 is worth testing now — it fixes long‑standing Explorer problems and brings genuinely useful discovery features to the desktop. For conservative production environments, the prudent path remains staged pilot validation, policies to control Copilot sharing and third‑party StorageProvider use, and clear communication to users about what the Recommended files surface will show and how to opt out.
Source: Windows Report KB5067036: Windows 11 File Explorer Adds Recommended Files and Fixes Bugs
Background / Overview
KB5067036 is a non‑security, Release Preview update for Windows 11 that updates servicing binaries for both the 24H2 and 25H2 servicing lanes while exposing a set of user‑facing features through staged, server‑side enablement. Microsoft published the preview to Insiders and Release Preview participants as builds for the two servicing branches; the package has appeared under OS builds 26100.xxxx (24H2) and 26200.xxxx (25H2) with slightly different build revisions during the rollout window.The release is intentionally split between:
- immediate fixes and binary updates that install when the MSU is applied, and
- gradual feature activations that Microsoft flips on for subsets of devices using server flags and enablement packages.
What changed in File Explorer (practical summary)
Recommended files in File Explorer Home — what it is
File Explorer Home now includes a Recommended section that surfaces files you frequently use, recently downloaded, or added to the File Explorer Gallery. This appears by default for personal Microsoft accounts and local accounts. If you prefer the previous behavior, the Recommended section can be turned off from File Explorer Folder Options; disabling it restores the classic Quick Access/pinned folders area.Key behaviours:
- Up to three recommended items can surface in the Home area (count may vary by build/enablement).
- Hovering over a recommended item can reveal quick actions (for example, Open file location and Ask Copilot in Microsoft account scenarios).
- The logic that decides what to recommend runs locally, but when signed with a Microsoft account certain flows may consult cloud signals — something to bear in mind for privacy-conscious users.
StorageProvider APIs — why developers should care
Microsoft added StorageProvider APIs that allow third‑party cloud providers to integrate suggested files directly into File Explorer Home. That opens a path for competitors or enterprise storage providers to provide OneDrive‑style suggested items inside the native Explorer surface instead of forcing customers into a separate client UI. Developers can register providers so the system can query for suggested files on the user’s behalf.Benefits:
- Reduced context switching between cloud portals and the native file manager.
- A consistent UX for cloud‑backed files in File Explorer Home.
- Opportunity for cloud providers to surface enterprise‑relevant signals (recent shares, team documents) directly to the OS.
- Any third‑party provider hooked into Explorer increases the attack surface that touches the file manager. Administrators should validate providers and vet permissions before broadly enabling integrations.
The reliability fixes that matter
KB5067036 includes a focused set of quality fixes for several painful Explorer regressions that had been reported by users and testers. The most notable fixes are:- Context menu flicker: the right‑click context menu previously could toggle between the compact modern menu and the legacy “Show more options” on successive right clicks; this has been fixed.
- Folder view reset: opening a folder from another app (for example, launching Downloads from a browser) no longer resets your custom view settings (sorting, icon size, grouping).
- Explorer body non‑responsiveness: the File Explorer window body sometimes stopped responding to mouse clicks after invoking the context menu; this has been resolved.
- Large archive extraction failure: extracting very large archives (community testing highlighted failures with archives around 1.5 GB) that previously generated “Catastrophic Error” (0x8000FFFF) should now succeed.
- Explorer becoming unresponsive when opening Home: this reliability issue has been addressed to reduce hangs and freezes.
Start menu tweaks and other UI changes (brief)
KB5067036 also bundles a Start menu refresh that consolidates app discovery into a single, vertically scrollable surface and introduces view modes such as Category and Grid. The Start menu remembers the last selected view and adapts to screen size. Phone Link is surfaced more prominently, and small visual tweaks to the taskbar and battery icons were implemented to improve glanceability. These Start changes are visible in Release Preview notes and community hands‑on reports, but — again — are staged so they may not appear immediately after installation.Crucial verification and cross‑checks
To validate the most load‑bearing claims in public reporting:- Microsoft’s Release Preview notes list KB5067036 under the preview builds for the two servicing branches (manifested as 26100.xxxx and 26200.xxxx builds), confirming the package and staged nature of the rollout.
- Independent community reporting and hands‑on coverage confirm the presence of the Recommended files feature, the StorageProvider APIs, and the listed Explorer fixes — corroborating Microsoft’s notes and the Windows Report summary.
Strengths — why this update is useful
- Practical productivity gain: surfacing recent and frequently used files directly on File Explorer’s Home removes repetitive navigation steps and is a clear time‑saver for knowledge workers, help desk staff, creators, and anyone who reopens files repeatedly.
- Developer opportunity: StorageProvider APIs level the playing field for cloud storage vendors to integrate with native Explorer UX, potentially reducing the long‑standing OneDrive monopoly on recommended file surfaces.
- Real reliability work: the update fixes multiple regressions that were causing tangible disruptions (context menu flicker, view resets, catastrophic extraction errors). For many users, those fixes alone justify installing the preview in pilot rings.
- Feature control: Microsoft exposed an explicit toggle to disable Recommended files, restoring the classic Quick Access view for users or admins who want to opt out.
Risks, privacy considerations, and enterprise governance
Privacy and data flow
The Recommended files engine is designed to work locally, but certain flows — especially when signed into a personal Microsoft account — may consult cloud signals to enhance suggestions. Ask Copilot and other AI actions can surface summaries or perform tasks that may involve sending file contents or window images to Copilot services. For regulated environments or data‑sensitive organizations, that behavior increases the need for explicit governance, DLP controls, and user training.Fragmentation and support complexity
Because many features are gated by hardware (Copilot+ NPUs), licensing (Microsoft 365/Copilot entitlements), account type (personal Microsoft vs Entra ID), and region, IT teams should expect inconsistent user experiences across a heterogeneous fleet. This fragmentation complicates support, documentation, and user education.New attack vectors from integrations
StorageProvider APIs let third‑party cloud providers participate in Explorer Home. While this is useful, it also broadens the attack surface within Explorer: a compromised provider or a buggy integration could enable privilege escalation, unwanted data exposure, or performance regressions. Administrators should vet providers, validate permissions, and consider allowing only trusted providers via enterprise policy.How to try KB5067036 and how to opt out of Recommended files
If you want to test KB5067036 in a controlled fashion:- Enroll a test device in the Windows Insider Program (Release Preview ring).
- Open Settings → Windows Update → Check for updates and install the optional preview labeled KB5067036.
- Reboot and wait 24–72 hours for staged features to appear; verify OS build in Settings → System → About.
- Open File Explorer.
- Select View → Options (Folder Options).
- In Folder Options, uncheck the Recommended section so Quick Access/pinned folders display instead.
- Open Settings → Personalization → Taskbar → Taskbar behaviors.
- Disable any “Share any window from my taskbar” or related Copilot sharing options, and use MDM/GPO controls in enterprise images as appropriate.
Recommendations for IT and enterprise teams
- Pilot first: validate KB5067036 on a representative set of hardware and user personas. Because feature enablement is staged, test both the binary behavior (fixes) and the server‑activated features (Recommended files, Start redesign) on the same devices.
- Inventory Copilot exposure: identify which user groups will have Copilot access, which devices are Copilot+ capable, and which users sign in with personal Microsoft accounts vs enterprise Entra IDs. That helps you assess data egress risks and DLP applicability.
- Vet cloud providers: if you intend to allow third‑party StorageProvider integrations, require vendor security reviews, least‑privilege access, and signed attestations about data handling. Maintain a whitelist of approved providers.
- Update policy controls: ensure Group Policy and Intune profiles include settings to disable Recommended Files or Copilot sharing where regulation or policy dictates. Document these controls for support teams and end users.
- Prepare user guidance: craft short playbooks for end users that explain how to disable recommendations, how to use Ask Copilot responsibly, and when not to share sensitive files or windows.
A critical look: balancing productivity with privacy and manageability
KB5067036 is emblematic of Microsoft’s current approach to Windows: ship the platform code broadly, then progressively enable contextual AI features for users that meet hardware, licensing, and regional conditions. The design is strong from a productivity perspective — Recommended files and Ask Copilot reduce friction at the point of work — but it shifts the governance burden to IT and end users.Positives:
- Tangible fixes for long‑standing Explorer issues.
- Developer‑friendly APIs that allow cloud vendors to better integrate into OS UX.
- User controls to disable features that some users or admins won’t want.
- Feature fragmentation across devices and accounts complicates support.
- New sharing affordances create additional data‑exposure surfaces.
- Third‑party integrations raise practical security and reliability questions.
Final assessment and actionable next steps
KB5067036 is not a flash update chasing hype; it’s a functional preview that blends usability refinements (Recommended files, Start surface tweaks), developer enablement (StorageProvider APIs), and real reliability work (Explorer fixes including the 0x8000FFFF archive extraction issue). For anyone who has been asking for fewer Explorer headaches, this preview delivers measurable improvements while also delivering a forward push toward ambient, context‑aware Copilot interactions inside the OS.Action plan summary:
- Test KB5067036 in a controlled Release Preview ring for representative hardware and user profiles.
- Review and update DLP and Copilot sharing policies before enabling Copilot or StorageProvider integrations at scale.
- Vet any third‑party StorageProviders and maintain a whitelist for enterprise images.
- Prepare clear user guidance for disabling Recommended files and Copilot sharing if required by policy.
Conclusion: For power users and administrators willing to do the legwork, KB5067036 is worth testing now — it fixes long‑standing Explorer problems and brings genuinely useful discovery features to the desktop. For conservative production environments, the prudent path remains staged pilot validation, policies to control Copilot sharing and third‑party StorageProvider use, and clear communication to users about what the Recommended files surface will show and how to opt out.
Source: Windows Report KB5067036: Windows 11 File Explorer Adds Recommended Files and Fixes Bugs
