Microsoft has temporarily paused the rollout of the experimental tabbed-folder behavior in File Explorer as part of the Windows 11 25H2 preview (delivered in builds such as 26220.7262 / KB5070303), while also reconfiguring several AI-driven File Explorer actions and disabling Image Object Selection for Insiders until reliability and privacy concerns are addressed.
Background / Overview
Windows 11’s 25H2 preview stream is being delivered as a series of
enablement-style cumulative updates and small preview packages. Microsoft packages many potential features inside the same binaries and then uses server-side flags, hardware gating, and Controlled Feature Rollout (CFR) to switch features on or off for subsets of Insiders. That means the visible experience on a machine depends not only on the installed build but also on entitlement, region, account type, and Microsoft’s telemetry-driven gate logic.
The recent preview flight that contains these adjustments—reported in community tracking as Build 26220.7262 and published to Insiders as KB5070303—packages accessibility improvements, UI polish, and a raft of small but visible UX changes. At the same time, the release explicitly marks several AI-enabled surfaces and integrations as being
reconfigured or
paused while Microsoft stabilizes the backend and rollout logic.
What Microsoft shipped in this preview (quick summary)
The preview update contains many small but consequential items. Highlights called out in the release notes and community summaries include:
- Accessibility upgrades — HD voice support for Narrator and Magnifier, and an early phase of math-reading support in Narrator (notably for Microsoft Word scenarios).
- AI and agent controls — a new Settings toggle labeled for experimental agentic features, giving Insiders explicit control over exposing agentic behaviors in Windows.
- Click to Do and Copilot UI refinements — redesign of the Click to Do context menu and expanded on-screen actions for images and tables. Some actions are being reconfigured while backend services are migrated.
- File Explorer polish and guarded features — people icons returned to the Activity column for some Insiders; however, several cloud integration points (StorageProvider APIs and Recommendation surfaces) and the new tabbed-folder experiment have been temporarily paused.
- Image Object Selection temporarily disabled — Microsoft has turned off Image Object Selection in Dev and Beta channels to refine the experience before wider exposure.
- Teaching tips, Tutorial mode and onboarding — smoother transitions, a new Launch Tutorial button, and clearer first-run guidance.
- Haptic pen improvements — support for subtle tactile feedback in supported pens when interacting with window controls or snap affordances.
- Administrator Protection paused — a previewed privilege-elevation hardening mechanism is not being presented to Insiders until further adjustments are completed.
Each of these bullets represents a small UX or security-focused change; several are explicitly staged or temporarily withdrawn pending reliability validation.
File Explorer: what changed, what was paused
Tabbed folders rollback — the short version
The tidy, browser-style behavior that would open newly launched folders as tabs inside a single File Explorer window (rather than spawning separate windows) has been paused during this flight. Newly opened folders will revert to the traditional window-per-folder behavior until Microsoft resolves the underlying reliability issues. The change is deliberate: Microsoft says the tabbed-folder experiment is being held while the system that powers AI actions and related features is reconfigured.
This rollback is not a simple UX tweak; it reflects a conservative approach to avoid exposing users to regressions where the presence of tabs introduced instability or inconsistent behavior across contexts such as shortcuts, external apps, and shell integrations. Community and Microsoft notes emphasize that CFR and server-side gating mean the binary may already include the tab code — but the visible behavior is controlled centrally, and Microsoft simply paused the exposure.
AI actions and Copilot summaries: CFR reconfiguration
File Explorer’s AI actions — including Copilot summary actions and image-based actions surfaced in context menus or hover surfaces — are being reconfigured as part of a Controlled Feature Rollout. As the backend services and configuration change, Insiders may temporarily see fewer image actions and disabled Copilot summary options in Explorer until Microsoft finishes the reconfiguration and phases the features back in.
This is a server-side gating and telemetry optimization: Microsoft adjusts which devices see which features to contain risk while iterating quickly. The practical effect for end users is intermittent availability of AI features in Explorer during the preview.
Image Object Selection: turned off in Dev & Beta
Image Object Selection — a capability that allows the system to identify and operate on objects inside images (for example, isolating a person or an object) — has been temporarily disabled for Dev and Beta Insiders. Microsoft described this as a short-term rollback to refine the experience and backend handling. Expect it to return after additional quality work.
People icons, StorageProvider APIs and Recommended files
A smaller, non-AI but highly useful change — re-enabling people icons in the Activity column of File Explorer Home — has been reintroduced to some Insiders to help identify last editors of shared files. At the same time, Microsoft has paused the StorageProvider APIs (third-party cloud integrations) and the Recommended files surface while it validates cross-cloud sync reliability, privacy behavior, and telemetry. This selective rollback is designed to reduce potential data-surface mismatch issues and provide enterprise-friendly controls.
Accessibility, Narrator, and input-device work
Accessibility continues to be a visible priority in the 25H2 preview line. The update brings
HD voice support to Narrator and Magnifier and the first phase of
structured math reading in Narrator for Microsoft 365 Word documents — a meaningful advance for blind and low‑vision users who rely on accurate, semantically organized math output rather than a flat character stream. These features are flagged as initial phases and are expected to expand to additional scenarios over time.
On the input side, the update adds
haptic feedback for supported pens. When hovering close to close buttons or when snapping windows, users with compatible pens will feel subtle tactile cues — a small but tangible accessibility and discoverability improvement for pen-enabled hardware.
Administrator Protection and security-focused features: paused
The preview included an item called
Administrator Protection — a previewed security hardening around elevation and admin operations intended to reduce persistent elevated contexts and shrink the attack surface for privilege escalation. Microsoft has paused the rollout of Administrator Protection in this flight while it makes adjustments, so Insiders will not see the feature until Microsoft completes the necessary validation. This pause reflects the higher risk tolerance required for security changes: before exposing a feature that alters elevation semantics, the company prefers to refine policy, compatibility, and management controls.
Why Microsoft paused these items — analysis
Microsoft’s stated approach to these pauses is conservative and telemetry-driven; a few plausible, evidence-backed reasons explain the decision:
- Controlled Feature Rollouts (CFR) and gating complexity. Many features are shipped in binaries and enabled selectively. When telemetry or user feedback surfaces instability or unexpected behavior, Microsoft will flip the flag to pause exposure while preserving other fixes. This lets the company minimize the blast radius.
- Privacy, regulatory and enterprise governance. The Recommended files surface and StorageProvider APIs touch cloud content and identity metadata. Early preview behavior differed by account type and region (for example, Entra ID vs. personal Microsoft accounts, or EEA restrictions). Those differences suggest Microsoft needs more time to reconcile consent, data residency, and enterprise controls before a wider rollout.
- Performance and reliability at scale. Features that require background cloud queries, thumbnail rendering, or complex selection logic can create UI-thread stalls, increased network I/O, or unexpected interaction with third-party shell extensions. The pauses reduce the risk of widespread regressions on diverse hardware and management configurations. Community and Microsoft notes point to explorer responsiveness problems as historically linked to cloud integrations and synchronous shell operations.
- Security posture and interaction with other hardenings. Microsoft tightened preview-pane and Mark‑of‑the‑Web behaviors in a prior security update. Introducing richer thumbnails and third‑party preview handlers simultaneously has the potential to re‑expose sensitive content or interact badly with new security checks; pausing gives Microsoft time to reconcile both code paths.
These reasons are rooted in public release notes and community-tracked changelogs; Microsoft has not published a detailed engineering post‑mortem for every paused feature, so some causal inferences remain plausible but not fully verified. Where precise root-cause details are not available, treat the explanation as reasoned analysis rather than definitive fact.
Practical impact: who is affected and how
- Windows Insiders (Dev/Beta): Expect variable availability. If you rely on the new tabbed-folder behavior or image-based AI actions, you may see them disappear or reappear depending on Microsoft’s server-side gating. Use test hardware for previews rather than primary production machines.
- Power users and enthusiasts: The tabbed Explorer experience remains obtainable via third‑party tools and registry/ViVeTool toggles in some cases, but enabling experimental flags risks instability and is unsupported for production environments. If you value stability, avoid enabling experimental toggles on your daily driver.
- Enterprises and admins: The paused StorageProvider APIs and Recommendation surfaces mean cloud-integrated workflows may not behave consistently during rollout. Admins should pilot updates in a representative ring, validate Group Policy and CSP mappings (for example, HideRecommendedSection), and update change-control and rollback plans to include these preview packages.
- Accessibility-dependent users: The accessibility features included (HD voices, math reading) are promising and worth testing in controlled environments, but they are still in early phases and may not yet meet production accessibility QA expectations across every scenario.
Recommended actions and mitigations
- For Insiders on Dev/Beta channels:
- Pause updates on machines you rely on for daily work before the next preview flight unless you maintain a robust backup and recovery plan.
- Use the Feedback Hub (WIN + F) to report reproducible problems and attach logs. This telemetry is how Microsoft decides when to re-enable features.
- For enthusiasts who want to test tabbed folders:
- Prefer a non-production VM or spare device. Beware that forcing enablement via community tools (ViVeTool) can produce unsupported states and should be used cautiously.
- For IT and enterprise admins:
- Pilot the build in a representative ring that includes common third‑party shell extensions, cloud sync clients (OneDrive, third-party providers), and your provisioning images (including multi-session images).
- Update documentation and support playbooks to include rollback steps (Uninstall updates via Settings → Update history) and ensure BitLocker keys, images, and recovery ISOs are readily available.
- For users who experienced regressions in File Explorer:
- A fast recovery step is restarting the Explorer process (Task Manager → Windows Explorer → Restart). If the update proves disruptive, uninstall the preview package and wait for Microsoft to release a stabilized version.
Strengths, risks, and an editorial appraisal
Strengths
- Microsoft’s iterative enablement model allows the company to ship binaries quickly and iterate based on real-world telemetry, accelerating feature development without requiring monolithic OS releases. This model makes it possible to refine features such as Click to Do, Narrator improvements, and haptic pen feedback rapidly.
- Pausing problematic features is the pragmatic choice for preserving overall system stability. With File Explorer being central to productivity, halting a tabbed experience that introduces instability is the responsible move for a platform vendor.
Risks and trade-offs
- The CFR model creates inconsistent user experiences: two machines on the same build can show different features. That variability complicates testing matrices and increases helpdesk noise during pilot deployments. Enterprises should plan for this non-determinism.
- Data surface and privacy concerns are real when exposing richer cloud-integrated surfaces (Recommended files, StorageProvider APIs). Without carefully defined permission models and regional controls, these features risk exposing metadata or confusing users about the true location and sync state of files. Microsoft’s temporary pull suggests this is being taken seriously; administrators should remain cautious.
- Security-related features (Administrator Protection) deserve thorough vetting. Pausing an elevation-model change is sensible, but extended delays can leave the user base waiting for improved hardened semantics. Vendors and enterprise ISVs need clarity on the final model before making adjustments to deployment or management tooling.
What remains unverifiable
- Microsoft’s public notes and community tracks make clear that features are paused while reconfiguration occurs, but the company has not published low-level code diffs or a detailed timeline for full re-enablement. Any precise prediction about when tabbed-folder behavior, Image Object Selection, or Administrator Protection will return would be speculative. Treat stated timelines as tentative until Microsoft updates Flight Hub or the official Insider blog with a re‑enable date.
Final takeaway
The temporary halt to the tabbed-folder experiment and the reconfiguration of File Explorer’s AI and image features represent a conservative, telemetry-driven response from Microsoft during a rapid cycle of AI-enabled UX innovation. Insiders will continue to see a shifting set of behaviors as Microsoft refines these experiences, and enterprises should treat preview builds as test artifacts rather than production-ready packages. The manifest advances — better Narrator voices, math reading, haptic pen cues, Click to Do refinements — show Microsoft is pursuing pragmatic polish while balancing stability, privacy, and manageability.
For anyone planning to test or adopt these preview builds, the recommended approach is clear: deploy in controlled pilot rings, keep a reliable rollback plan, evaluate cloud integration and security implications, and use the Feedback Hub to help Microsoft prioritize fixes and refinements. The tabbed File Explorer experience remains an attractive productivity goal, but it will return only when Microsoft is confident the feature behaves reliably across the fragmented ecosystem of accounts, regions, and third‑party integrations that make Windows complex and powerful.
Source: Windows Report
Microsoft Temporarily Halts Roll Out of Tabbed Folders in File Explorer With KB5070303