Windows 11 Release Preview KB5067036: Start Menu Redesign and On‑Device AI Upgrades

  • Thread Author
Today’s Release Preview drop for Windows 11 — cumulative update KB5067036 delivering Builds 26100.7015 (24H2) and 26200.7015 (25H2) — is a focused but consequential update: it stitches in a broad sweep of user-facing polish, expands on-device AI capabilities for Copilot+ hardware, and patches a long list of stability and compatibility issues that IT teams should know about before moving to broader pilots. The package is being distributed via the Release Preview channel and continues Microsoft’s enablement‑package approach that stages code across the servicing branch and flips features on gradually for target devices.

A Windows-style desktop on a sleek laptop, displaying a left app list and a “Share with Copilot” tile.Background / Overview​

Microsoft is using the same servicing model it has applied across the past year: binaries are delivered throughout the servicing branch and features are enabled later using small, low-impact enablement packages. That’s why you’ll see identical or near-identical binaries across Windows 11 24H2 and 25H2 lines while Microsoft controls who gets which visible feature through server-side flags and staged rollouts. This update arrives in the Release Preview ring as a validation / pilot milestone — intended for managed testing and early production pilots rather than broad, unmanaged rollouts.
What makes KB5067036 notable is not a single blockbuster change but rather the combination of:
  • A visible Start menu redesign that will change how users launch apps.
  • Expanded on‑device AI features (Voice Access “Fluid Dictation”, Click to Do improvements) targeted initially at Copilot+ PCs.
  • Deeper Copilot integration in File Explorer and the Taskbar that encourages sharing UI content with Microsoft Copilot.
  • Numerous bug fixes across File Explorer, input/pen, graphics, remote credential scenarios, and Windows Update reliability.
Below is a feature-by-feature breakdown, verification of significant technical claims, and a frank evaluation of benefits, risks, and recommended next steps for IT admins and power users.

What’s in the release (headline items)​

Gradual rollout (features you may or may not see immediately)​

  • Redesigned Start menu with a single, vertically scrollable surface and a new “All” section that supports three views (Category, Grid, List). The menu adapts responsively to screen size and remembers your last selected view. Phone Link is integrated into Start via a small mobile device button.
  • Voice Access — Fluid Dictation: a new default dictation mode that uses on‑device small language models (SLMs) to correct grammar, punctuation, and remove filler words in real time. It is enabled by default on Copilot+ PCs in English locales and is disabled in secure fields. Voice Access also gains Japanese language support and an adjustable delay setting before executing voice commands.
  • Click to Do enhancements: typeable prompt box for Copilot, translations for on‑screen text, unit conversions, multiple selection modes (Freeform, Rectangle, Ctrl+Click), table detection with “Convert to table with Excel” (Copilot+ hardware gated, Microsoft 365 required), and live persona cards for Microsoft 365. Some features are region‑gated (EEA/China exclusions) and some are hardware- and licensing-gated for Copilot+ devices.
  • File Explorer: Recommended files in Home now available for personal and local accounts (toggleable), hover commands like “Open file location” and “Ask Copilot”, and new StorageProvider APIs for cloud providers to integrate suggested files. Some parts of this rollout are not yet available in the EEA.
  • Taskbar: refreshed battery icons (colored states + optional percentage) and a new “Share with Copilot” button under taskbar window thumbnails so Copilot Vision can scan and analyze window contents (user-configurable). The lock screen also adopts the new battery icon treatment.
  • Various setup, login, and administration improvements: ability to name the default user folder during OOBE (via a SetDefaultUserFolder.cmd workaround documented in the release notes), performance improvements for taskbar loading after sleep, and the new Administrator Protection Preview (off by default; requires OMA-URI or Group Policy to enable).

Normal rollout (wide fixes landing with the update)​

  • Fixes for Remote Credential Guard failures in cross-version scenarios, an ACCESS_DENIED resolution for remote password changes, media playback fixes for protected content after earlier updates, and many File Explorer and graphics/display fixes to address unresponsive dialogs, incorrect context-menu behavior, or rendering artifacts.

Deep dive: the redesigned Start menu​

What changed​

The new Start menu is intentionally larger and more flexible:
  • A single scrollable canvas where All apps are presented at the top level rather than tucked behind a page.
  • Three views for All apps: Category (groups apps by type and surfaces frequently used ones), Grid (alphabetical tiles), and the classic List. The Start menu remembers your last chosen view.
  • Responsive layout: larger displays can show more columns of pins/recommendations/categories; pinned and recommended areas expand or collapse depending on content.
  • A Phone Link mobile button (next to Search) collapses or expands phone content directly within Start.

Verification of technical specifics​

Independent coverage and community previews corroborate Microsoft’s description. Early tester reports and multiple tech outlets confirm:
  • The scrollable “All” top-level change and the Category/Grid views exist in preview builds.
  • Responsive column counts and the default pinned/recommended behavior were part of the documented preview guidance and validated by community reporting.

Analysis — benefits and risks​

Benefits:
  • Faster discovery for users with many apps.
  • Cleaner, less intrusive “Recommended” defaults with explicit controls in Settings to hide recommendations.
  • Better use of large displays and more immediate access to pinned apps.
Risks / points to watch:
  • The Category view is system-generated and currently lacks user control — you cannot edit or create buckets yet. That can frustrate power users and complicate enterprise determinism in managed environments.
  • Staged rollouts mean inconsistent visibility across endpoints; two systems on the same build may show different Start behavior depending on Microsoft’s server-side flags. This complicates documentation and training for help desk teams.
  • Accessibility and automation scripts that relied on the previous Start layout may need updates; IT should validate assistive workflows and automated UI tools.
Recommendation:
  • Add Start layout validation to user-acceptance test plans for pilots.
  • Validate accessibility workflows (screen readers, keyboard navigation).
  • Use Settings > Personalization > Start toggles to enforce recommended-feeds behavior in pilot groups.

Deep dive: Voice Access — Fluid Dictation (and Japanese support)​

What it is​

Fluid Dictation is a real-time dictation mode inside Voice Access that applies on‑device small language models (SLMs) to provide punctuation, grammar corrections, and filler-word removal as you speak. Because the processing is on‑device, Microsoft emphasizes low latency and improved privacy compared with cloud-based transcription. The feature ships enabled by default on Copilot+ PCs in English locales and is intentionally disabled in secure fields like password inputs. Voice Access also gains Japanese support and a configurable “wait time before acting.”

Verification and cross-check​

Independent coverage and community testing match Microsoft’s claims: the experience runs on-device for Copilot+ hardware and is available in the latest Insider flights; documentation and forum threads explain how users can toggle Fluid Dictation.

Analysis — benefits and risks​

Benefits:
  • Faster, cleaner dictation sessions requiring fewer manual edits.
  • On-device inference reduces latency and the amount of data that must be routed to cloud services.
Risks:
  • Hardware gating to Copilot+ PCs creates fragmentation: many users on legacy or non‑NPU hardware won’t see the feature.
  • On-device SLMs reduce but do not eliminate privacy risk; cloud services may still be invoked if you execute a Copilot cloud action from a local session — users and admins must understand when content leaves the device.
  • Language and locale coverage is currently incomplete; voice access expansion is incremental.
Recommendation:
  • For public or shared workstations, update acceptable use and privacy guidance to explain what on-device AI does and when cloud-based actions might occur.
  • Pilot with Copilot+ hardware if you intend to rely on Fluid Dictation for production workflows.

Deep dive: Click to Do and Copilot integration​

New capabilities​

Click to Do continues to evolve from a screenshot-and-action utility into a robust, contextual Copilot gateway:
  • Prompt box for typed prompts that send selected on-screen content to Copilot.
  • On-screen translation: when selected text differs from the Windows display language, a translation suggestion appears and translated text can be routed into Copilot.
  • Unit conversions available inline (length, area, volume, temperature, speed).
  • Selection modes: Freeform, Rectangle, and Ctrl+Click for mixed-type selections.
  • Table detection: highlight simple tables and send to Excel via “Convert to table with Excel” (currently Copilot+ Snapdragon-first; AMD/Intel support coming; requires latest Excel and Microsoft 365 subscription).
  • Live Persona Cards and visual cues to light up items while launching Click to Do.
  • Additional regional gating: many features aren’t available yet in the EEA or China.

Verification and cross-checks​

Windows Insider documentation and independent outlets (Windows Central) report the same Click to Do features and clearly state the hardware/licensing/regional constraints. This aligns with the staged Copilot+ rollout plan.

Analysis — benefits and risks​

Benefits:
  • Very useful productivity shortcuts (translate, convert tables to Excel, summarize).
  • Many operations are processed on-device for privacy and speed until you explicitly use cloud-backed Copilot features.
Risks:
  • Licensing and hardware gating: the “Convert to table with Excel” action requires a Microsoft 365 subscription and specific Copilot+ hardware today, creating inconsistent end-user experiences.
  • Region restrictions: EEA/China exclusions mean Copilot-linked features may be disabled for large swathes of enterprise users subject to local regulations or enterprise policies.
  • Data control: Click to Do makes it easy to capture on-screen content and send it to Copilot; organizations must decide acceptable boundaries for sharing proprietary content into Copilot (even if prompts are local-first, cloud queries may be optional).
Recommendation:
  • Update acceptable-use guidance that clarifies when screen captures may be routed to cloud services.
  • For sensitive environments, consider group policies or MDM controls to restrict Click to Do or Copilot share actions.
  • Test table detection accuracy with real-world documents during pilot; it’s early-preview and may not be perfect.

File Explorer, Taskbar, and Copilot — deeper integration​

The update pushes Copilot deeper into the shell:
  • File Explorer Home shows recommended files for local and personal Microsoft accounts (toggleable).
  • Hovering over files surfaces actions like “Ask Copilot” and “Open file location” (sign-in with Microsoft account required).
  • Taskbar thumbnail previews now show a “Share with Copilot” button that launches Copilot Vision to analyze and offer insights about the application window (user setting to opt out available).
Analysis:
  • These integrations make Copilot a native productivity assistant, but they also raise privacy and governance questions for enterprise environments. IT teams should determine whether they will permit taskbar-level content sharing and ensure policies exist to prevent inadvertent disclosure of confidential information.
Recommendation:
  • Use the Taskbar behaviors settings and MDM policies to control Copilot sharing options in managed devices.
  • Educate users on the practical differences between on-device analysis and cloud-augmented Copilot interactions.

Enterprise and IT-focused changes​

Administrator Protection Preview​

A defensive feature to protect free-floating admin rights by offering just-in-time admin elevation workflows. This feature is off by default and must be enabled via OMA-URI (Intune) or Group Policy. It’s a positive step toward reducing persistent admin exposure, but rollouts should be tested in lab environments before enabling in production.

Servicing and deployment implications​

The enablement-package model continues to make upgrades lighter (often one restart for version flips). However:
  • Removal/deprecation of legacy tooling (examples earlier in the year included PowerShell 2.0 and WMIC) means compatibility tests are essential for scripts and legacy management tools.
  • Validate third-party agent compatibility (AV, backup, management) and firmware/drivers, especially for Copilot+ hardware which may need vendor-supplied BIOS/driver updates.
Practical IT checklist (recommended):
  • Build a pilot ring on non-critical hardware (VMs or lab devices).
  • Confirm image tooling and scripts do not rely on deprecated components (WMIC, PowerShell v2).
  • Validate Remote Credential Guard and domain authentication workflows after installing the update.
  • Test device-specific Copilot features only on hardware that meets the Copilot+ certification profile.

Quality, bug fixes, and reliability​

KB5067036 delivers a long list of fixes that address practical issues reported by Insiders:
  • File Explorer context-menu toggling, large archive extraction failures, and File Explorer unresponsiveness are fixed.
  • Taskbar thumbnail selection focus issues and the lock-screen battery indicator rendering are addressed.
  • Voice/pen input problems related to microsoft.ink.dll exceptions and some video/game rendering problems have been patched.
  • Windows Update reliability fixes include addressing “Update and shutdown” not shutting down and Windows Update error 0x800f0983 installation failures.
These are material fixes for users who experienced recent regressions. Administrators should review the fixed issues list against tickets and telemetry in their environment and include verification for those specific scenarios in pilot testing.

Privacy, governance, and regulatory caveats​

Several features explicitly exclude the European Economic Area (EEA) and China at rollout, and Microsoft calls out regional limits for Click to Do’s translation and some File Explorer Copilot features. The EEA exclusion is significant for enterprises operating in or serving European users — compliance teams should be looped in to assess how Copilot integration and screen-capture features intersect with data protection and transfer considerations.
Key governance points:
  • On‑device models (SLMs) reduce cloud exposure but do not eliminate it; user actions that invoke Copilot cloud capabilities will route data externally.
  • Microsoft account vs. Entra ID behaviors differ — some Copilot/Explorer features are available only to Microsoft account users today; Entra ID support is indicated for future updates. Validate account types and MDM policies in pilot groups.

Practical recommendations — for administrators and advanced users​

  • Pilot strategy:
  • Start with a small set of Copilot+ devices (if you plan to use on-device AI features) and a broader set of general Windows 11 devices to validate baseline fixes.
  • Include user personas that rely on the Start menu and File Explorer heavily (help desk, design, developers) in pilot testing.
  • Security & governance:
  • Update acceptable-use policies to explicitly cover Click to Do and Copilot interactions.
  • Consider MDM policies to control or disable Click to Do, taskbar “Share with Copilot,” and File Explorer “Ask Copilot” where warranted.
  • Compatibility:
  • Validate scripts and management utilities against the deprecation list (legacy PowerShell/WMIC).
  • Confirm backup/agent compatibility and driver/firmware readiness for Copilot+ hardware.
  • Training:
  • Document new Start menu behaviors and provide short “how to” guidance for staff (how to switch between Category/Grid/List; how to hide Recommended content).
  • Provide privacy guidance on when capturing screen content with Click to Do is appropriate.
  • Troubleshooting:
  • If encountering update installation failures, refer to the Windows Update reliability fixes and test Windows Update on a few devices first before wide deployment.

Strengths, trade-offs, and final assessment​

Strengths:
  • The release is thoughtful: it blends important reliability fixes with incremental, productivity‑focused feature rollouts.
  • On‑device AI improvements (Fluid Dictation, some Click to Do actions) are meaningful for latency-sensitive workloads and reduce immediate cloud dependency.
  • The Start menu redesign directly addresses long-standing user complaints and gives users more control over recommended content.
Trade‑offs and risks:
  • Hardware and licensing gating (Copilot+ and Microsoft 365) will fragment the user experience across organizations.
  • Region-based gating (EEA / China) introduces compliance and training complexity for multinational organizations.
  • Server-side feature flags make rollout behavior unpredictable; two identical endpoints may behave differently, complicating support documentation.
Final assessment:
KB5067036 is an important incremental update for Windows 11: it smooths a number of pain points and pushes Win11’s Copilot-era features further into everyday workflows. For organizations, the release is worth piloting promptly — but not in production — while IT teams validate compatibility, privacy posture, and user training. Businesses that rely on consistent, deterministic UI behavior should take particular care with the staged Start menu changes and Copilot integrations.

This release is available now to Insiders in the Release Preview Channel; teams planning evaluation should check Settings > Windows Update on representative devices, follow staged pilot guidance, and treat the enablement package model as the reason feature exposure may vary across machines.

Source: Microsoft - Windows Insiders Blog Releasing Windows 11 Builds 26100.7015 and 26200.7015 to the Release Preview Channel
 

Microsoft has pushed a substantial Release Preview update to Windows 11 Insiders — KB5067036 — delivering a redesigned Start menu, on-device AI improvements for voice access, deeper Copilot integrations (Click to Do and Copilot Vision), File Explorer Home enhancements, Taskbar and battery icon refinements, and a raft of stability fixes and enterprise-facing changes. The update arrives as two builds — Build 26200.7015 (25H2) and Build 26100.7015 (24H2) — and is currently rolling out gradually to Release Preview channel participants for testing before broader distribution.

A translucent, Windows-style app launcher panel with Microsoft icons floating on a blue background.Background​

Microsoft’s Windows Insider program has long used the Release Preview channel to stage optional, lower-risk changes that will be folded into wider cumulative releases. KB5067036 follows that pattern: it’s a preview-class update meant to let administrators, enthusiasts, and testers validate user-facing UI changes and underlying reliability fixes ahead of inclusion in a public cumulative update. The official Windows Insider changelog lists the new features under a “gradual rollout” and a “normal rollout” section, a distinction that explains why not every Insider will see all changes immediately.
Windows’ Start menu has been a focal point of iterative redesigns across 2024–2025 development cycles. The Start changes in KB5067036 represent one of the most visible and structural shifts since Windows 11’s launch: Microsoft is consolidating app discovery, expanding customization, and teasing tighter Phone Link and Copilot interactions that nudge the Start experience toward a hybrid productivity hub. Multiple independent outlets and community previews have documented similar Start experiments earlier in the Insider channels, confirming that this rollout is the culmination of work visible in Dev and Beta builds earlier in the year.

What’s in KB5067036: Quick highlights​

  • New Start menu: A single scrollable surface with an “All” apps section, multiple views (Category and Grid), responsive layout, and Phone Link integration.
  • Voice Access — Fluid Dictation: On-device small language models (SLMs) enable real-time grammar, punctuation, and filler-word handling; available by default on Copilot+ PCs in English locales. Japanese language support and a configurable delay for command execution were added.
  • Click to Do / Copilot enhancements: Prompt box for typed Copilot prompts, on-screen text translation, unit conversions, multi-selection modes, table detection with “Convert to table with Excel,” Live Persona Cards, and visual cues. Some experiences are hardware- and region-gated (Copilot+ PC hardware, EEA/China exclusions).
  • File Explorer Home: Recommended files available to personal/local Microsoft accounts, hover commands (Open file location / Ask Copilot), and StorageProvider APIs for cloud providers to offer suggested files.
  • Taskbar & Lock screen: Colored battery icons with charging/low indicators, optional battery percentage in the tray and lock screen; thumbnail previews for open apps now include a “Share with Copilot” button.
  • Reliability and security fixes: Improvements to Windows Update reliability, Remote Credential Guard, display/graphics glitches, input/pen APIs, and Open/Save dialogs. Administrator Protection Preview is also available for enterprise testing.
The changelog published by the Windows Insider team is the authoritative reference for what Microsoft has shipped to the Release Preview channel. Independent press and community reports confirm the same set of features and further document early impressions from testers.

Deep dive: The redesigned Start menu​

What changed, concretely​

The Start menu redesign shifts away from the two-pane Pinned + Recommended layout toward a single vertically scrollable canvas with a top-level “All” section. Users can now choose between:
  • Category view: Groups apps by category and surfaces frequently used apps.
  • Grid view: An alphabetical, tile-like grid that gives more horizontal spacing.
  • List view (classic): Preserved for compatibility with existing workflows.
The menu remembers the last selected view and adapts layout density for larger displays — showing more pinned apps, recommendations, and categories when space allows. A small Phone Link button beside the search field provides quick collapsed/expanded access to connected phone content. These are deliberate moves to prioritize discoverability and reduce clicks for app access.

Why it matters​

The rework addresses two persistent requests from power users and long-time Windows customers: the desire for a unified app surface (as in Windows 10’s more flexible Start) and the ability to opt out of “Recommended” content that some find noisy. By giving users multiple views and remembering preferences, Microsoft is trying to make Start more predictable and faster to navigate. Early hands-on reports indicate the redesign is not a radical visual departure, but a practical rearrangement to reduce friction when launching apps.

Limitations and rollout notes​

The Start redesign is part of the update’s gradual rollout, so not every Release Preview device will immediately see it. Administrators testing through the Release Preview channel should expect phased exposure. Also, the Phone Link integration and some Copilot-driven hints remain region-restricted (EEA availability is explicitly delayed into 2025 for some features), so behavior may vary by locale and device.

Voice Access and Fluid Dictation: On-device SLMs​

Fluid Dictation represents one of the more technically interesting additions in KB5067036. Microsoft says the feature uses on-device small language models (SLMs) to perform grammar and punctuation corrections and to reduce filler words in real time — a move that emphasizes privacy (local processing) and responsiveness. Fluid Dictation is enabled by default in Voice Access on Copilot+ PCs for English locales. The update also adds Japanese language support for Voice Access and allows users to configure a delay before voice commands execute.
This approach mirrors larger industry trends: offloading core AI inference to device-local models for latency and privacy while preserving cloud capability for heavier workloads. For users who need a reliable, low-latency dictation experience without sending every keystroke to the cloud, on-device SLMs are a positive step. That said, the feature set is gated to specific hardware tiers (Copilot+ and Copilot-enabled devices) and locales, so broad availability will come over time.

Click to Do and Copilot integrations: practical AI in the OS​

Click to Do has been substantially extended in this update, further binding Windows UI selection with Copilot capabilities:
  • Type and send custom prompts from a prompt box directly to Copilot; suggested prompts are provided locally and currently support English, Spanish, and French.
  • On-screen text translation flows content selected in-app to Copilot for translation, then presents the result inside the Copilot app; region restrictions apply (EEA/China excluded initially).
  • Unit conversions via inline tooltips for numbers and units; selections surface conversion options in the context menu.
  • Object selection modes (Freeform, Rectangle, Ctrl+Click) and table detection with a “Convert to table with Excel” action — currently available on Snapdragon Copilot+ PCs, with AMD/Intel support coming later. A Microsoft 365 subscription and the latest Excel are required for the Convert to table flow.
These capabilities indicate Microsoft’s push to make Copilot not just a separate app but a contextual assistant that operates across OS surfaces. The hardware and subscription gating is important: some of the more advanced flows (table conversion, Copilot Vision scans) are limited by device AI capabilities and Microsoft 365 licensing. Administrators and users should budget for compatibility and licensing when evaluating Copilot-driven workflows.

File Explorer Home: Suggested files and hover commands​

File Explorer Home receives practical upgrades: personal and local accounts can now see Recommended files (frequently used, recently downloaded, or gallery items), and a hover UI exposes commands like Open file location and Ask Copilot for quick context actions. Microsoft also opened StorageProvider APIs so cloud providers can integrate suggestions directly into File Explorer Home.
These changes reflect Windows’ trajectory toward blending local file management with intelligent suggestions and cloud integration. There are administrative and privacy knobs: users can disable the Recommended section in File Explorer Folder Options, and in enterprise settings the rollout to work/school (Entra ID) accounts is staged for later updates. Note that region rollout restrictions apply in some cases.

Taskbar, battery icons, and Copilot Vision sharing​

KB5067036 updates several small-but-visible pieces of system chrome:
  • Battery icons are now colored to represent state (green while charging/healthy; yellow at ≤20%) and include an optional battery percentage toggle in Settings > Power & battery. The lock screen also displays the improved battery visuals.
  • Taskbar previews show a new “Share with Copilot” button under thumbnail previews of open app windows. Activating this invokes Copilot Vision to analyze app contents for insights (user can disable this via Taskbar behaviors setting).
These changes are cosmetic but meaningful for usability and privacy: colored icons improve at-a-glance battery awareness, while the Copilot sharing affordance raises immediate privacy considerations because it enables visual scanning of window contents. Microsoft exposes controls to opt out, but organizations should review policy and training guidance before broadly enabling window-sharing features in managed environments.

Enterprise and security notes​

  • Administrator Protection Preview: This preview feature aims to protect “free-floating” admin rights by providing just-in-time elevation while preserving core admin ability when needed. It is off by default and must be enabled via OMA-URI in Intune or Group Policy.
  • Windows Update fixes: The update addresses cases where “Update and shutdown” did not properly shut down the machine after installing updates and resolves installation failures tied to error 0x800f0983 in previous updates. However, community reports show that some cumulative updates in October 2025 experienced widespread install failures across diverse hardware, and administrators should plan staged rollouts and recovery paths.
For enterprise fleets, the salient points are clear: test the preview on representative hardware, validate Copilot/Click-to-Do network and licensing dependencies, and ensure administrative controls (Intune/GPO) are in place before enabling features that surface organization-sensitive data to on-device or cloud-assisted AI.

Known issues and troubleshooting (what testing found so far)​

Several community and official threads describe installation and post-update problems with recent cumulative updates; while KB5067036 targets preview testing, admins should be aware of the following trends:
  • Install failures (0x800f0983 and variants): Reports linked to October baseline/hotpatch updates show some devices failing to install earlier cumulative updates, with standard recovery steps (DISM / SFC, update component reset) occasionally insufficient. Microsoft’s Q&A and community forums contain multiple recovery walkthroughs. Administrators should keep rescue ISOs and offline recovery plans available when validating updates in production-like environments.
  • Behavioral regressions: Taskbar rendering and search/component regressions have appeared in earlier October builds; KB5067036 contains fixes for some display stutters and graphics issues, but comprehensive verification against enterprise apps (browser-based web apps, GPU-accelerated content, productivity suites) is recommended.
  • Hardware and regional gating: Copilot+ experiences, Convert to table with Excel, and some Click to Do features are gated by CPU/SoC and region (EEA/China exclusions). Feature availability can be inconsistent across a mixed fleet; hard gating means administrators may not be able to “turn on” certain features without hardware refreshes or licensing changes.
Recommended pre-deployment checks:
  • Validate recovery process (bootable ISO, system image restore) before mass rollout.
  • Test representative hardware with on-device AI features to confirm Copilot+ behaviors and driver interactions.
  • Confirm Microsoft 365 licensing is in place for Copilot/Excel conversions where required.
  • Verify privacy controls and GPO/Intune policies for Copilot data-sharing features.

How to get KB5067036 and what to expect​

If you’re enrolled in the Release Preview channel, go to Settings > Windows Update and click Check for updates; KB5067036 should appear as an optional Release Preview update. Microsoft also provides standalone MSU/catalog packages for manual installation, but manual installs sometimes require prior servicing stack or prerequisite updates. The Release Preview blog post includes the official build/version numbers: Build 26200.7015 for 25H2 and Build 26100.7015 for 24H2.
A few practical notes:
  • Expect a staggered, phased rollout for many features — not everything will appear immediately.
  • The update is intended for validation and testing; it’s not a mandatory security release. Organizations should test in pilot rings before broad deployment.

Risk assessment and recommendations​

KB5067036 bundles visible UI changes and AI-enabled integrations that deliver genuine user productivity gains, but they also introduce surface area for compatibility issues and privacy considerations.
Strengths:
  • Improved productivity flows: Start redesign and Click to Do/Copilot integrations reduce friction in app discovery and in-context actions.
  • On-device AI for privacy and latency: Fluid Dictation’s SLM approach balances responsiveness and local privacy for dictation tasks.
  • Developer hooks: StorageProvider APIs and other platform additions give developers routes to integrate cloud suggestions and AI features into Explorer-level experiences.
Risks and mitigations:
  • Installation regressions: Recent cumulative update months have seen install failures across diverse hardware. Mitigate by staging updates, having recovery ISOs, and validating disk/servicing health before upgrade.
  • Hardware/licensing gating: Copilot+ and Convert-to-Excel features are limited by hardware and subscription. Maintain an inventory and test matrix to determine which devices will gain full value.
  • Privacy/organizational exposure: “Share with Copilot” and Copilot Vision scan capabilities can surface sensitive window contents. Enforce policy, disable sharing where necessary, and educate users on the opt-out controls.

Final analysis: what this update signals for Windows 11’s direction​

KB5067036 reads like a microcosm of Microsoft’s current Windows strategy: integrate practical AI into everyday OS interactions, preserve and modernize core UX patterns (Start and Explorer), and gate higher-value experiences behind hardware tiers and subscriptions. The Start menu redesign is the most consumer-visible change and an intentional nudging back to a more discoverable, consolidated app surface. Meanwhile, Click to Do and Copilot integrations move the OS toward being an assistant-first environment where context-aware actions are surfaced at the point of selection.
For enterprise IT teams, the update emphasizes two priorities: cautious, staged testing because of past cumulative update installation variability, and proactive governance around AI-enabled features to control data flow and user opt-in. For consumers and enthusiasts, the update unlocks smoother dictation, more practical Copilot features, and a Start menu that feels less split and more navigable.
In short, KB5067036 is both evolutionary UI work and an accelerant for AI-first workflows in Windows. Insiders and admins should test thoughtfully — confirm recoverability, validate hardware and licensing gates, and treat the new Copilot sharing affordances as policy-controlled features rather than defaults.

Conclusion
KB5067036 (Builds 26100.7015 and 26200.7015) is a consequential Release Preview update: it packages a visible Start menu overhaul, richer in-context AI via Click to Do and Copilot, improved Voice Access with on-device SLMs, practical File Explorer suggestions, and numerous reliability fixes. The rollout is intentionally phased and constrained by hardware, licensing, and regional limitations; administrators should conduct measured testing while end users enrolled in Release Preview can expect to see incremental changes as Microsoft expands availability. The update underlines Microsoft’s continuing strategy to weave local and cloud AI capabilities tightly into the OS while balancing performance, privacy, and enterprise manageability.

Source: Neowin KB5067036: Windows 11 gets redesigned Start menu and more new features in Release Preview
 

Blue-themed Windows 11 File Explorer layout showing Home, Recommended, and Quick access panels.
Microsoft’s Release Preview drop KB5067036 quietly folds a set of intelligent, user-facing improvements into Windows 11 — most notably a Recommended Files section in File Explorer Home and an “Ask Copilot” hover command — while also opening StorageProvider APIs for third‑party cloud integration and shipping a long list of practical reliability fixes for File Explorer and related UI surfaces.

Background​

Windows 11’s October Release Preview package (KB5067036) arrives as two build flavors: Build 26100.7015 for version 24H2 and Build 26200.7015 for version 25H2. These builds are distributed through the Release Preview channel and are explicitly structured as a gradual, staged rollout: many UI and Copilot-enabled experiences are toggled server‑side and will appear for Insiders and devices at different times.
The update continues Microsoft’s pattern of shipping platform binaries broadly while gating higher‑value experiences (Copilot actions, on‑device AI features, region restrictions) behind enablement flags, hardware checks, and licensing entitlements. That delivery model explains why two identical machines on the same build may show different behavior depending on Microsoft’s server‑side rollout state.

What’s new in File Explorer (practical summary)​

Recommended Files on File Explorer Home​

  • File Explorer Home now includes a Recommended Files section that surfaces items you frequently use, recently downloaded, or added to your File Explorer Gallery. This appears for personal Microsoft accounts and local accounts by default. Users who prefer the previous layout can disable the Recommended section via Folder Options; doing so restores the pinned Quick Access view.
  • Why it matters: Recommended Files brings a discovery layer to Explorer’s front page, reducing friction for frequent tasks like reopening recent documents or returning to a download. For users who rely on quick access to a handful of files, this can shave time; for privacy‑conscious environments it increases the need for policy and awareness.

Hover commands: “Open file location” and “Ask Copilot”​

  • When you hover over files on File Explorer Home, a small fast‑action strip now appears with commands such as Open file location and Ask Copilot. The “Ask Copilot” action lets you request a summary or insight from Copilot without opening the document itself. At present this hover-Copilot capability requires signing in with a Microsoft account; Microsoft has stated support for work and school (Entra ID) accounts will arrive in a future update.
  • Practical limits: the Copilot summarization and AI actions are subject to hardware and licensing gating for some advanced flows (e.g., Copilot+ device capabilities and Microsoft 365 Copilot entitlements) and are regionally limited at initial rollout. Keep in mind that “Ask Copilot” can invoke cloud processing depending on the specific flow.

StorageProvider APIs for cloud providers​

  • Microsoft has opened StorageProvider APIs enabling third‑party cloud services to surface suggested files directly inside File Explorer Home. This means OneDrive‑like experiences can be implemented by other cloud vendors to show suggested/recent content in the same Recommended area. Developers can register a provider so the system can query for suggested files on behalf of the user.
  • Impact: for enterprises using alternative cloud storage providers, the APIs provide a path to integrate cloud‑native recommendations into the native Explorer surface — useful for reducing context switching and improving visibility into cloud assets.

Verified technical specifics (what I checked)​

  1. Build numbers and channel: KB5067036 corresponds to Builds 26100.7015 (24H2) and 26200.7015 (25H2) and is published to the Release Preview channel.
  2. Recommended Files and Folder Options toggle: The release notes explicitly document Recommended files appearing in File Explorer Home for personal and local accounts, and confirm a Folder Options toggle to disable the Recommended section (replacing it with Quick Access).
  3. Hover UI and account gating: The hover UI exposing Open file location and Ask Copilot appears in the Release Preview notes and is limited today to Microsoft account sign‑ins; Entra ID support is slated for a future update.
  4. StorageProvider APIs: The update calls out the new StorageProvider APIs for cloud providers to participate in file suggestions.
These claims are corroborated by independent community reporting and forum breakdowns of the release (early hands‑on coverage and forum threads summarizing the changelog), which match Microsoft’s published notes.
Where a claim can change over time (for example, which account types or regions currently see which features), the release notes emphasize staged rollouts and regional exclusions — those are gating conditions that must be verified on any device expecting the feature.

What this means for everyday users​

  • Faster access: The Recommended Files panel reduces friction for commonly repeated tasks. Users who live in File Explorer (help desk staff, writers, designers) will notice less context switching when reopening active work items.
  • Instant insights without opening files: The “Ask Copilot” hover action is a clear productivity play — quick summarization and question‑answering on a document can save time. Expect it to be particularly useful for triaging long reports or extracting basic metadata from documents.
  • Personalization and control: Microsoft preserves a user opt‑out in Folder Options, which is important for privacy-minded users or those who prefer a static Quick Access layout. The toggle also helps power users who want the old deterministic behavior.
  • Account and region limits: If you use a work/school account today, you may not see the new hover Copilot commands until Entra ID support rolls out. Users in the EEA and China are likely to encounter region-based delays for some Copilot‑backed experiences.

Enterprise and admin considerations​

Privacy, data flow, and governance​

  • Copilot actions can be performed either on‑device (when hardware supports local models) or via cloud services — the exact path depends on the Copilot flow, device capabilities, and the specific operation. Organizations should treat the new hover and taskbar sharing features as potential data egress points and evaluate policy controls accordingly.
  • The taskbar preview “Share with Copilot” and hover “Ask Copilot” flows require explicit user action, but admins should still plan for acceptable use policies that cover when users may send window content or files to Copilot for analysis. Group Policy and Intune controls can be used to limit or disable Copilot sharing behaviors in managed fleets.

Deployment guidance (recommended pre‑pilot checklist)​

  1. Build a small pilot ring (5–10% of fleet) covering representative hardware, including any Copilot+ certified devices and standard endpoints.
  2. Validate Windows Update and deployment tooling can deliver KB5067036 and any prerequisite servicing updates.
  3. Test the Folder Options toggle and document user guidance for disabling Recommended Files.
  4. Verify that any endpoint DLP (data loss prevention) tooling properly intercepts or blocks Copilot upload flows where required.
  5. For devices intended to use on‑device SLM/ Copilot+ features, verify drivers, firmware, and vendor BIOS are up to date and compatible.

Licensing and feature access​

  • Some Copilot features (table extraction into Excel, some advanced summarization) require a Microsoft 365 subscription and, in some cases, explicit Copilot licensing, so IT should inventory entitlements before enabling related flows in production.

Bug fixes and reliability improvements included in KB5067036​

Microsoft bundles a substantial set of fixes with this release. Notable explorer- and UI-related fixes include:
  • Resolved File Explorer freezing when opening Home and cases where File Explorer became unresponsive.
  • Fixed context menu flicker that toggled between compact and legacy “Show more options” on each right‑click.
  • Resolved catastrophic extraction failures for very large archives (example cited: >1.5 GB) that previously failed with error 0x8000FFFF.
  • Fixes for taskbar thumbnail preview behavior and battery icon updates (colored states and an optional percentage display).
These reliability items are important for both consumer and enterprise users; if your environment has been hit by any of these regressions, prioritize the update in your pilot testing.

Privacy and security trade‑offs — a critical look​

  • Data visibility vs productivity: The integration of Copilot into file discovery and hover actions provides clear productivity benefits, but it raises legitimate privacy questions when Copilot actions involve sending document content to cloud services. Microsoft’s documentation emphasizes explicit user initiation for visual sharing but does not remove the need for policy review in regulated environments. Organizations should assume that some Copilot flows will route data externally unless configured otherwise.
  • Region and account gating reduce immediate risk exposure in markets where regulation is strict, but they also complicate administrative policy: different policies may be necessary for cross‑border teams due to staggered feature availability.
  • On‑device SLMs: When features run locally on Copilot+ hardware, latency and privacy improve; however, these hardware‑gated experiences are not universal. Relying on local models at scale requires qualifying and procuring compatible hardware, which may be impractical for some organizations.

How to try or opt out (concise user steps)​

  1. If you’re in the Release Preview channel, go to Settings → Windows Update → Check for updates; KB5067036 should appear as an optional Release Preview update.
  2. To disable Recommended Files: Open File Explorer → View → Options (Folder Options) → uncheck the Recommended section so Quick Access displays instead.
  3. If you do not want Copilot sharing affordances: Settings → Personalization → Taskbar → Taskbar behaviors → disable “Share any window from my taskbar” (or use MDM policies for enterprise control).

How the File Explorer changes fit into Microsoft’s larger strategy​

KB5067036 is not just a File Explorer polish pack — it’s part of a broader push to make Copilot an ambient assistant embedded across the OS: Click to Do enhancements, taskbar “Share with Copilot,” Start menu redesign, and on‑device SLMs all reflect a cohesive direction toward contextual AI surfacing at the point of action. This architectural approach emphasizes smaller, contextual surfaces (Explorer, taskbar previews, selection tool) rather than a single monolithic Copilot app.
From a product perspective, integrating recommendations and AI actions into Explorer is a logical next step: files are the most common objects users interact with, and adding summarization, visual edits, and semantic discovery there reduces app switching and improves workflows.
From a governance perspective, it increases the number of places where potentially sensitive content can be acted on by an AI — so policy, training, and MDM controls must evolve as these surfaces proliferate.

Strengths, weaknesses, and final assessment​

Strengths​

  • Practical productivity wins: Recommended Files and hover Copilot actions remove friction for common tasks.
  • Developer enablement: StorageProvider APIs open a path for cloud providers to integrate suggestions into Explorer Home, improving parity with OneDrive experiences.
  • Sound reliability work: The pack fixes several recurring File Explorer bugs and Windows Update reliability issues that matter to real users.

Weaknesses / Risks​

  • Fragmentation risk: Hardware, licensing, and region gating will create uneven experiences across a fleet, complicating support and documentation.
  • Privacy surface area: New Copilot triggers and taskbar sharing introduce potential data egress points; enterprises must align policy and technical controls.
  • Staged rollout unpredictability: Server‑side toggles mean the presence of a feature in a build is not a guarantee of visibility — complicating pilots and user training.
Final assessment: KB5067036 is a thoughtful incremental update that blends useful productivity features with meaningful quality fixes. It’s a sensible candidate for early pilot rings, provided organizations treat Copilot interactions as policy‑sensitive and validate the update against their compliance and DLP posture before wide deployment.

Closing recommendations (actionable)​

  • For consumers: Install KB5067036 in the Release Preview ring if you want early access to Recommended Files and Copilot hover actions; disable the Recommended section in Folder Options if you prefer the classic Quick Access experience.
  • For IT administrators:
    1. Pilot KB5067036 on a small, representative set of devices and document feature visibility differences.
    2. Verify DLP and endpoint monitoring for Copilot upload flows.
    3. Prepare user guidance: how to disable Recommended Files, how to use Ask Copilot responsibly, and when to avoid sending screen or file content to Copilot.
  • For developers and cloud providers: Evaluate the StorageProvider APIs to see whether integrating suggested files into Explorer Home can deliver value for your customers; ensure your provider respects the user’s privacy and consent model.
KB5067036 is another step toward a Windows 11 that surfaces AI where users already work. The practical gains are real, but they come with new governance and deployment complexity that organizations must consciously manage.

Source: Windows Report Windows 11's File Explorer Gets Recommended Files and Copilot Integration with KB5067036 Update
 

Microsoft’s latest Release Preview drop for Windows 11 — published as KB5067036 and delivered as Builds 26100.7015 (24H2) and 26200.7015 (25H2) — introduces a redesigned, more adaptive Start menu alongside a suite of on-device AI refinements, deeper Phone Link integration, and several Copilot/Click-to-Do enhancements that together aim to make app discovery faster and the desktop experience feel more personal and intelligent.

Windows 11-style start menu with pinned apps and a Phone Link panel on the right.Background​

Microsoft released the KB5067036 preview to Insiders in the Release Preview Channel as a staged rollout, meaning the new experiences are enabled gradually and may not appear on every Release Preview machine immediately. The package contains identical servicing binaries for both Windows 11 version 24H2 and 25H2, with feature exposure controlled by server-side flags and enablement packages rather than large, monolithic installers. That delivery model explains why some devices already surface the new Start design while others remain on the older layout.
This update is notable because it bundles visible UI changes (the Start redesign and Phone Link embedding) with platform-level improvements (on-device small language models for Voice Access, File Explorer enhancements, and taskbar refinements). The combination of UI, AI, and reliability fixes makes KB5067036 useful both for daily users seeking polish and for IT teams preparing pilots.

What changed: the redesigned Start menu​

The Start menu is no longer the simple two‑pane Pinned + Recommended surface it was in earlier Windows 11 releases. Microsoft moved to a single, vertically scrollable canvas with a top-level All section, and added three distinct views for browsing apps: Category, Grid, and the classic List. The change aims to reduce clicks and context-switching when launching apps.

Scrollable “All” surface​

Instead of navigating away to a separate All apps page, the new Start exposes every installed app on the main surface through vertical scrolling. For people with many installed applications, this reduces friction: fewer clicks, more visible entries at a glance, and a single mental model for launching apps. Independent hands‑on coverage and Microsoft’s changelog both describe this shift as a practical step toward faster app discovery.

Category view, Grid view, and List view​

  • Category view: Automatically groups apps by function — Productivity, Games, Creativity, Communication, etc. — and surfaces frequently used apps within each bucket. Categories are generated when there are enough apps to form a group (typically three or more).
  • Grid view: Presents apps in an alphabetized, denser tile grid for faster horizontal scanning. This view trades vertical scrolling for horizontal density.
  • List (classic) view: Preserved for compatibility and users who prefer the traditional alphabetical list.
The Start menu remembers the last view you selected, so the experience persists across sessions and feels more predictable over time. That small UX detail matters for power users who switch a lot between workflows.

Responsive layout and pin/recommendation behavior​

The new Start adjusts to screen size and DPI. On larger monitors, Microsoft’s preview notes show defaults such as up to 8 columns of pinned apps, 6 recommendations, and 4 category columns; smaller screens reduce those defaults (for example, 6 pinned columns and fewer recommendation slots). Sections like Pinned and Recommended will expand or collapse based on content, and a “Show all pins by default” toggle lets users surface every pinned item immediately without extra clicks. These numeric layout claims are documented in the Insider changelog and echoed by independent reporting.

Phone Link integration inside Start​

A small mobile‑device button placed next to the Start search field toggles a collapsible Phone Link pane, exposing basics such as phone battery, messages, calls, notifications, and photos directly adjacent to Start. The integration is designed for quick glances and lightweight cross‑device flows, and for many users it will reduce the need to open the full Phone Link app. Microsoft notes the feature is rolling out in most markets now and will reach the European Economic Area (EEA) later in 2025.

On-device AI: Voice Access and Fluid Dictation​

KB5067036 includes a significant accessibility and productivity improvement under Voice Access: Fluid Dictation, which uses on‑device small language models (SLMs) to perform grammar correction, punctuation insertion, and filler‑word reduction in near real‑time. That approach reduces latency and keeps more processing local to the PC, which benefits privacy-conscious users and scenarios where low lag is important. Fluid Dictation is enabled by default on Copilot+ PCs in English locales and is disabled in secure fields (passwords, PINs). The update also adds Japanese support for Voice Access and a configurable delay setting before executing voice commands.
This move reflects a broader industry shift toward running smaller, task‑specific AI models on-device while reserving larger cloud models for heavier tasks. For users who frequently rely on dictation (content creators, mobility‑impaired users), Fluid Dictation can offer a more natural typing-by-voice experience without constant cloud round trips.

Click to Do, Copilot integration, and File Explorer changes​

KB5067036 deepens Copilot’s presence in routine workflows through Click to Do enhancements and File Explorer Home integrations.

Click to Do expansion​

Click to Do now includes:
  • Table detection with the ability to “Convert to table with Excel” (requires Microsoft Excel and, for some flows, a Microsoft 365 subscription).
  • Live Persona Cards from Microsoft 365 shown inside Click to Do for organizational emails.
  • Visual cues that highlight items such as emails and tables when Click to Do is invoked.
  • A prompt box for typed Copilot prompts and suggested prompts in multiple languages (initially English, Spanish, and French).
Some Click to Do features are hardware‑ or region‑gated — notably, the best on‑device performance is reserved for Copilot+ hardware with NPU acceleration, while broader support for AMD/Intel Copilot+ devices is rolling out. Additionally, a few flows are initially blocked in certain regions (EEA, China) or require licensing entitlements. Administrators should treat Click to Do as a feature that may or may not appear depending on enablement flags and device capabilities.

File Explorer Home — recommended files and hover commands​

File Explorer Home now surfaces Recommended files for personal and local accounts, and hovering over files reveals quick actions like Open file location and Ask Copilot. Ask Copilot can summarize or extract insights without opening the file, but advanced summarization may invoke cloud services and can be subject to hardware and licensing checks. StorageProvider APIs are also available so third‑party cloud providers can surface suggested files directly in File Explorer Home. These additions aim to reduce friction when returning to recent work but raise privacy and governance questions for enterprise environments.

Taskbar, system tray, and other UI refinements​

KB5067036 also tweaks smaller but visible UI elements:
  • Battery icon improvements: color-coded icons (green for charging, yellow when ≤20%), simplified overlays, and a user‑toggle to show battery percentage in the system tray and on the lock screen.
  • Taskbar thumbnail previews of open apps now include a Share with Copilot button beneath the preview. Selecting it allows Copilot Vision to analyze the window’s visible content; this behavior is optional and can be disabled.
These touches are incremental but meaningful: the battery tweaks immediately improve glanceability on laptops, and the taskbar Copilot sharing button lowers the barrier to content‑aware assistance when users want it.

Why this matters — benefits for everyday users and power users​

  • Faster app discovery: The single, scrollable Start and the new views (Category/Grid/List) help users find apps with fewer clicks. For heavy app users, category grouping can reduce search time, while grid/list provide predictable alphabetic access.
  • More personalization and control: New Settings toggles let users hide Recommended content, display all pins by default, and choose the All apps view that fits their workflow. That restores configurability that many users requested after earlier Windows 11 Start designs.
  • Quieter, faster voice interaction: On-device Fluid Dictation reduces latency and avoids sending all dictation data to the cloud by default on supported hardware. This is a real improvement for dictation quality and privacy.
  • Seamless cross-device flows: Phone Link inside Start provides quick visibility into phone status and messages without launching a dedicated app, making small cross‑device tasks faster.

Risks, trade-offs, and enterprise considerations​

While the update offers clear usability gains, several non‑trivial trade-offs and risks must be weighed by IT professionals and privacy teams.

Fragmented experience due to gating​

Microsoft’s staged rollout model, hardware gating (Copilot+ vs. mainstream PCs), and regional exclusions (EEA/China timing differences) will create a fragmented UI and feature landscape across enterprise fleets. Two identical machines—including identical images—may show different behavior depending on server-side flags, complicating support documentation and user training. Organizations should pilot widely but cautiously.

Privacy and data governance​

Features such as Recommended files, Ask Copilot, and Click to Do that summarize content or surface suggested prompts potentially touch sensitive data. While some on-device capabilities exist, other flows invoke cloud services and require Microsoft account sign-in or specific licensing. Administrators should:
  • Update acceptable‑use and data‑handling policies to cover Copilot and Click to Do interactions.
  • Use MDM and Group Policy to disable or limit features that surface sensitive content.
  • Pilot with user personas that frequently use Start, File Explorer, and Copilot in daily workflows (help desk, finance, design, legal).

Predictability and automation​

The automatic category grouping and responsive layout may break test automation or scripts that rely on deterministic Start coordinates or element names. Enterprises that use scripted UI automation should verify workflows and consider fallbacks. The lack of manual category editing also reduces administrative control for deterministic deployments.

Licensing and hardware restrictions​

Several of the most compelling experiences (high‑quality local AI inference, advanced Click to Do conversions, Copilot summarization) are gated behind Copilot+ hardware and/or Microsoft 365 entitlements. This can create inconsistent experiences across users and raises licensing questions for teams that expect uniform capability. Evaluate which workflows truly need these premium behaviors before committing to enterprise-wide enablement.

Practical deployment guidance for IT teams​

  • Pilot strategy:
  • Deploy KB5067036 to a representative pilot group using the Release Preview Channel and monitor feature exposure across devices.
  • Include diverse personas (developers, designers, legal, help desk) to catch edge cases early.
  • Policy and MDM:
  • Identify and test policy controls for Phone Link, Click to Do, Ask Copilot, and features that surface recent or recommended files.
  • Prepare guidance on which Copilot features can be enabled in production based on data sensitivity and regulatory needs.
  • Training and documentation:
  • Prepare short user-facing notes on how to switch Start views (Category/Grid/List), how to hide Recommended content, and how to manage Phone Link integration.
  • Update support scripts to account for responsive Start layout differences across display sizes.
  • Automation validation:
  • Re-run UI automation and imaging tests against machines with different feature flags enabled to ensure scripts remain robust.
  • Licensing assessments:
  • Map which Copilot+ or Microsoft 365 entitlements are required for advanced Click to Do and Copilot flows, and estimate incremental licensing costs if broader rollout is desired.

Hands‑on impressions and design critique​

The Start redesign is an evolution rather than a radical reinvention. It addresses the single most persistent complaint about the modern Windows Start: the inefficient recommendation-centric layout that pushed app access behind multiple clicks. Restoring a single, scrollable surface with multiple browsing modes is a pragmatic move that benefits both casual and power users.
Category view, while handy, raises predictability concerns. Automatic grouping is convenient for discovery but can be frustrating when categories are algorithmically assigned and cannot be renamed or overridden. Power users and admins who demand deterministic UIs may find this limitation inconvenient until Microsoft exposes more manual controls.
Phone Link in Start is a welcome convenience, but embedding cross‑device features into a widely visible OS surface increases the attack surface for accidental data exposure if misconfigured. The toggleability of the pane and the incremental rollout are prudent mitigations; still, organizations with strict data governance should treat Phone Link as a feature to evaluate carefully.
Finally, the combination of on‑device SLMs for dictation and cloud-backed Copilot actions shows Microsoft’s hybrid approach to AI in the OS: keep latency-sensitive tasks local, escalate heavier work to the cloud. That balance improves everyday performance and privacy but comes with fragmentation costs across devices.

Quick reference: what to test in a pilot​

  • Start menu behavior: confirm presence of All views, test category grouping logic, and validate the “remember last view” behavior across restarts.
  • Phone Link toggle: verify toggle, collapsed/expanded behavior, and privacy settings for message/photo access.
  • Voice Access: evaluate Fluid Dictation latency and accuracy on Copilot+ devices and measure behavior in secure fields.
  • Click to Do flows: test table detection, Convert to Excel, and Live Persona Cards for required app versions and licensing.
  • File Explorer Home: test Recommended files visibility, hover actions (Ask Copilot), and StorageProvider API integrations for enterprise cloud providers.
  • Automation and accessibility: run UI automation and accessibility checks with the new Start layout and ensure compliance for assistive tech workflows.

Conclusion​

KB5067036 is a thoughtful Release Preview milestone that stitches together a visible Start menu redesign, deeper Phone Link and Copilot interactions, and real on‑device AI improvements for Voice Access. The changes respond directly to long‑standing user feedback about Start’s discoverability and recommendation noise, while also advancing Microsoft’s hybrid on-device/cloud AI strategy. For individual users the result is a more customizable, faster Start experience; for enterprises the update is a useful but careful step that requires piloting, policy review, and consideration of hardware and licensing constraints. Pilot broadly, document impacts, and treat feature exposure as variable until Microsoft completes the staged rollout and clarifies enterprise controls.

Source: Windows Report Windows 11 Start Menu Gets Smarter and More Personal With KB5067036 Preview
 

Microsoft’s Release Preview drop KB5067036 (Builds 26100.7015 for 24H2 and 26200.7015 for 25H2) brings a concentrated set of user-facing improvements — chief among them a new, on-device “Fluid Dictation” mode inside Voice Access — and a broader set of Start menu, File Explorer, and Copilot integrations that nudge voice and AI deeper into everyday Windows workflows.

Windows desktop with Notepad text, a start menu, and a Copilot widget on screen.Background / Overview​

Microsoft published KB5067036 to Windows Insiders in the Release Preview channel on October 21, 2025, calling out a mixture of features that will roll out gradually and a number of quality fixes and reliability patches. The release is packaged as two builds (26100.7015 and 26200.7015) that map to Windows 11, versions 24H2 and 25H2 respectively.
This update follows months of incremental Insider flights testing on-device AI experiences, Copilot integrations, and accessibility improvements. The headline items in KB5067036 include:
  • Fluid Dictation inside Voice Access: a next-generation dictation mode using on-device small language models (SLMs) to perform real‑time punctuation, grammar fixes, and filler-word suppression.
  • Start menu redesign: a single, scrollable “All” apps section with category and grid views and a Phone Link quick-access button beside Search.
  • File Explorer Home enhancements: recommended files available to local and Microsoft accounts, hover quick-actions like “Open file location” and “Ask Copilot,” and new StorageProvider APIs for third-party cloud integrations.
The rest of this article verifies the technical claims, analyzes benefits and risks for consumers and IT, provides practical enabling steps, and offers advice for deployment and troubleshooting.

What is Fluid Dictation — the technical picture​

A practical evolution of Voice Access​

Fluid Dictation is presented as a mode within Voice Access that converts spoken input into more polished text as you speak, rather than producing a raw token stream that requires heavy post-dictation editing. The feature inserts punctuation, normalizes light grammar, and suppresses common filler phrases (for example, “um” and “uh”) in real time. Microsoft describes the capability as on by default for supported devices running this update.

On-device small language models (SLMs)​

The distinguishing technical claim is that Fluid Dictation is powered by on‑device small language models (SLMs) that run locally on qualifying hardware (so-called Copilot+ PCs). Running SLMs locally reduces round-trip latency to cloud services and is framed as a privacy-forward design because audio and intermediate representations can remain on the device. That said, the implementation is a local-first architecture; Microsoft notes that cloud augmentation or fallback may still be used for languages or scenarios where on-device models aren’t available. This hybrid reality is important when evaluating privacy and behavior.

How it integrates with the OS​

Fluid Dictation works across most editable text inputs in Windows (Notepad, Word, chat windows, web form fields), but it disables itself in secure fields such as password and PIN inputs to prevent accidental leakage. Users can toggle Fluid Dictation via Settings > Accessibility > Voice Access, or by voice command (“Turn on Fluid Dictation”). Microsoft has enabled the feature by default on eligible Copilot+ PCs in English locales during this rollout.

Availability, hardware gating, and language support​

Copilot+ hardware gate​

A central deployment pattern for Microsoft’s recent on-device AI features is hardware gating. The richest Fluid Dictation experience is targeted at Copilot+ PCs — machines with NPUs and vendor drivers certified to run local models efficiently. That means users with older hardware or devices without the qualifying neural accelerators may not see Fluid Dictation even after installing KB5067036. This gating was deliberately used across recent Insider flights and continues with this Release Preview update.

Language coverage and additional international support​

At initial rollout Fluid Dictation is documented as available in English locales only. The KB also adds full Japanese voice navigation support to Voice Access — enabling Japanese users to navigate, dictate, and interact with Windows via speech. Microsoft’s notes indicate language expansion may follow but provide no concrete timeline; that uncertainty is worth flagging for organizations that require determinism in language support.

Start menu and Phone Link enhancements — what changes for daily use​

KB5067036 also refreshes the Start menu UI with a consolidated, scrollable All apps surface and new Category and Grid views that remember your last selected view. The update’s Start menu includes a small Phone Link integration button placed next to Search, making it easier to surface content from a paired phone. This is a visible, high-impact UX change for users who rely on Start for app discovery and quick actions.
File Explorer receives complementary updates — recommendations surfaced on Home (available to both Microsoft and local accounts) and hover actions such as “Ask Copilot” tied to an integrated Copilot experience. These changes make a more proactive, AI-augmented desktop experience possible without leaving File Explorer.

Benefits: why Fluid Dictation matters​

  • Faster composition — Real-time punctuation and filler removal significantly reduces cleanup time after dictation, turning spoken drafts into near-ready prose.
  • Accessibility uplift — For users with mobility or dexterity challenges, fewer manual edits are a direct reduction in cognitive and physical friction.
  • Lower latency and perceived responsiveness — Local model inference reduces round-trip delays, delivering immediate text corrections for a smoother interaction.
  • Improved privacy posture (local-first) — On-device SLM inference reduces the default need to stream raw audio to cloud services; for many scenarios this limits exposure of sensitive speech data.

Risks, caveats, and technical trade-offs​

1) Hardware and driver dependency​

The Copilot+ gating means that the experience is uneven across the ecosystem. Organizations and users should not assume universal availability; device capability and OEM driver maturity are decisive. If your fleet contains a mix of devices, the feature set and performance will vary.

2) Model-size vs. capability trade-off​

SLMs optimized for on‑device runtimes intentionally trade breadth and world knowledge for low latency and compact footprint. That makes them excellent at punctuation, filler filtering, and light normalization — but they may miscorrect or fail to capture nuance that a cloud-scale model could handle. Users should expect occasional miscorrections, especially with names, industry terms, or long, nested sentences.

3) Privacy nuance — local-first does not mean cloud‑free​

Microsoft frames Fluid Dictation as local-first, but documentation and community analysis indicate cloud augmentation or fallback is still possible in scenarios where on-device models are absent or inadequate. Enterprises that require strict data residency guarantees or auditable cloud-use policies must validate configuration (especially Online Speech Recognition and telemetry settings) and verify whether any audio or derived data is being sent off-device in their environment. Treat explicit claims that "nothing ever goes to the cloud" with caution unless validated by enterprise telemetry, vendor documentation, or contractual guarantees.

4) Stability and preview‑channel risk​

KB5067036 is distributed to the Release Preview channel as a pilot. Some fixes are included, but preview builds can still surface regressions or driver-related issues — examples in recent Insider notes included hibernation bugchecks and audio driver problems documented in prior flights. IT pilot programs should treat this update as a controlled test rather than a broad-production push.

Cross‑verification of key claims​

  • Build numbers, KB identifier, and Release Preview timing: verified against Microsoft’s Windows Insider blog announcement for Builds 26100.7015 and 26200.7015 (KB5067036).
  • Fluid Dictation behavior (punctuation, filler removal, on-device SLMs, disabled in secure fields): confirmed by Microsoft’s announcement and independently reported by mainstream Windows coverage outlets.
  • Start menu redesign and Phone Link integration: verified in the official release notes and corroborated by independent reporting on the update’s UI changes.
When possible, these claims were cross-checked with at least two independent sources (Microsoft’s official notes and reputable coverage/community summaries) to ensure accuracy and to surface known caveats.

Practical steps — enable, test, and control Fluid Dictation​

Follow these steps to evaluate Fluid Dictation on a test device:
  • Update to the Release Preview build (KB5067036) via Settings > Windows Update. Confirm you’re on Build 26100.7015 (24H2) or 26200.7015 (25H2).
  • Verify your device is recognized as a Copilot+ PC if you expect on-device SLM support. Check OEM documentation and NPU driver availability.
  • Open Settings > Accessibility > Speech and launch Voice Access. Complete first-time setup, including microphone selection.
  • Toggle Fluid Dictation in the Voice Access flyout or say “Turn on Fluid Dictation.” Test dictation across apps (Notepad, Word, chat windows) and note behavior in secure fields (which should be disabled).
  • For enterprise pilots, record telemetry (network traces, telemetry logs) to validate whether any cloud fallback occurs in your environment. Confirm Online Speech Recognition settings (Privacy & security → Speech) and policy controls.

Deployment guidance for IT and power users​

  • Run a targeted pilot on representative Copilot+ hardware first. Do not assume uniform rollout across a mixed-device fleet.
  • Review speech and telemetry settings and communicate clear guidance to users about the privacy posture of on-device features. If your compliance rules prohibit any cloud audio processing, validate behavior with packet captures and Microsoft support.
  • Train helpdesk staff on Voice Access commands and Fluid Dictation behavior (how punctuation insertion works, how filler suppression behaves, and how to toggle the feature). Provide fallback typing workflows for users on unsupported devices.
  • Keep OEM drivers (camera, NPU, audio) up to date — many Copilot+ experiences rely on vendor-supplied updates and staged driver rollouts.

Troubleshooting and optimization tips​

  • Use a high-quality microphone/headset in noisy environments; built-in laptop microphones are more prone to background noise and can reduce accuracy.
  • Ensure the speech language and input language match. Mismatches can cause Win + H or Voice Access to misbehave. Download any required language packs before testing.
  • If Fluid Dictation produces odd corrections, try disabling it and switching to classic dictation modes to compare outputs; report consistent miscorrections via Feedback Hub.

Deeper privacy analysis — what to ask and verify​

Microsoft’s messaging emphasizes local-first processing, but there are several practical questions organizations should verify:
  • Does the feature ever fallback to cloud-based processing for certain utterances, languages, or failure modes? If so, under what conditions? Verify through policy settings and telemetry.
  • Are model updates pushed from Microsoft to client devices, and do those updates require network connectivity? Understand update cadence and whether model downloads are large.
  • What telemetry (if any) accompanies Fluid Dictation usage by default, and can it be disabled centrally via MDM/GPO? Confirm enterprise-level controls before enabling broadly.
If strict data residency or regulatory compliance is required, organizations should treat Fluid Dictation as an enabled feature only after explicit validation of on-device-only behavior for the languages and scenarios they plan to use.

Limitations and lingering unknowns​

  • Language roadmap is unspecified. Microsoft’s initial rollout focuses on English for Fluid Dictation; expansion timelines to other languages remain tentative and should not be assumed.
  • Model capability gaps. SLMs can correct punctuation and remove filler words well, but they are not a substitute for cloud-scale understanding or heavy editorial corrections. Expect occasional context losses or miscorrections.
  • Feature exposure is staged. Because KB5067036 is rolling out features gradually, some users on the same build may see different behavior depending on feature flags and telemetry-driven gating. Plan pilots with that variability in mind.

Final assessment — who benefits and when to adopt​

Fluid Dictation is a meaningful, practical step forward for speech-driven composition on Windows. It lowers friction for long-form dictation, benefits accessibility, and demonstrates the value of local inference for low-latency, privacy-conscious interactions. However, it is also explicitly tied to Microsoft’s Copilot+ hardware strategy and staged rollouts; the best candidates for early adoption are:
  • Individual power users on Copilot+ PCs who dictate frequently and want less manual editing.
  • Accessibility-focused pilots (organizations supporting employees with mobility or dexterity challenges) who can reap immediate productivity gains.
  • IT teams and device managers who can run controlled pilots, validate telemetry and cloud-fallback behavior, and coordinate OEM driver updates across fleets.
For general production deployment across heterogeneous device fleets, wait for wider availability (post-preview) and for explicit enterprise controls/documentation about telemetry and cloud fallback behaviors.

How to turn it on — quick reference​

  • Settings > Accessibility > Speech > Voice Access → Open Voice Access.
  • Use the settings flyout in the Voice Access bar to toggle Fluid Dictation, or speak “Turn on Fluid Dictation.”
  • Configure the new Wait time before acting setting under Voice Access to reduce accidental command execution during dictation.

Microsoft’s KB5067036 is not a single, dramatic platform overhaul — it’s a purposeful collection of incremental improvements that together signal where Windows is heading: a more voice- and AI-first OS that favors local inference when possible and ties richer experiences to Copilot+ hardware. The Fluid Dictation upgrade is the clearest practical win in this update: it reduces friction for dictation, improves accessibility, and demonstrates the benefits of on-device SLMs. That promise is tempered by hardware gating, model trade-offs, and the need for careful pilot testing in enterprise environments. For those running or managing Copilot+ devices, KB5067036 is worth testing immediately; for everyone else, it’s a strong signal of imminent capabilities that will arrive more broadly in the months ahead.

Source: Windows Report KB5067036 Update Brings Fluid Dictation to Voice Access in Windows 11 24H2 & 25H2
 

Laptop screen showing a Windows-style Start menu with app icons on a blue background.
Microsoft is moving a significant set of Windows 11 refinements out of the experimental labs and into the Release Preview channel: a redesigned Start menu, Taskbar polish (including a new, color-coded battery icon and the ability to show battery percentage), File Explorer upgrades with a Recommended feed and Copilot hooks, plus a raft of accessibility and on-device AI improvements. The build now in Release Preview packages these changes as a staged feature drop that Microsoft plans to flip on for broader audiences soon — but the rollout will be phased, region- and hardware-gated in places, and still subject to the usual caveats of staged updates.

Background / Overview​

Since Windows 11’s launch, Microsoft has adopted a more iterative, staged approach to major changes: ship binaries through servicing updates, then activate features via enablement packages or server-side gating. That means a headline change (like a Start menu redesign) can already exist on many devices and be activated when Microsoft deems telemetry and quality metrics acceptable. The current feature drop—visible now in the Windows Insider Release Preview channel—follows that pattern and is intended to be a low-friction activation for devices already on Windows 11 24H2 and 25H2.
This staged model has practical benefits for IT and consumers: smaller downloads, single‑restart upgrades, and faster rollback paths. It also creates a mixed reality for testers and early adopters: some systems will see the new UI elements immediately, while others keep the old experience until Microsoft rolls them out more widely. Expect variability during the first weeks of public rollout.

What’s shipping in this feature drop — quick checklist​

  • Redesigned Start menu: single-scroll surface, new “All” section with Category and Grid views, responsive layout, Phone Link side panel.
  • Taskbar updates: larger, color-coded battery icons; optional battery percentage in the system tray and lock screen; animated window thumbnail previews with a “Share with Copilot” action.
  • File Explorer: Recommended files feed in Home, hover actions (Open file location / Ask Copilot), StorageProvider APIs for cloud suggestions.
  • Accessibility & on-device AI: Fluid Dictation in Voice Access, expanded language support, Click to Do enhancements and Copilot integration (some features are Copilot+ hardware- or region-gated).
  • Reliability fixes: Windows Update reliability, Display and Input fixes, Open/Save dialog and File Explorer stability patches.
Each of these items is detailed in the Release Preview changelog Microsoft published alongside the build; independent hands‑on reports from major outlets confirm the core functionality in preview builds.

Redesigned Start menu: what changed, and why it matters​

A single, scrollable Start surface​

The new Start collapses what was previously a split experience into one vertically scrollable canvas. Pinned apps, Recommended content, and the “All” apps area are all accessible with a single scroll, removing page boundaries and reducing clicks. The goal is simple: faster discoverability for installed apps and recent content. Early impressions from testers show the one-surface model speeds app discovery on large, high‑resolution displays, though reactions vary for users with smaller screens or those who preferred the visual separation of the older layout.

Category, Grid, and List views​

Microsoft is giving the All apps list more than one personality:
  • Category view groups apps into topical buckets (e.g., Productivity, Games, Creativity) and highlights frequently used apps.
  • Grid view lays apps out alphabetically in a tile-like horizontal grid for wider scanning.
  • List view preserves the classic alphabetical list for users who prefer it.
The Start menu remembers your last chosen view and adapts layout density by screen size — larger displays will show more pinned icons, categories, and recommendations. That responsiveness is aimed at power users with many pinned apps and at multi-monitor setups. These view options address a long‑standing complaint about Windows 11’s original Start menu: lack of flexibility and discoverability.

Phone Link integration​

A small but strategic addition: a Phone Link button beside Search expands a collapsible side panel showing phone content — recent photos, messages, notifications, quick access to reply, and even phone-screen mirroring. This tightens the cross-device story Microsoft has been building and turns Start into a hub that surfaces relevant mobile content alongside your PC apps. Expect Phone Link features to be regionally phased; Microsoft has indicated some EEA rollouts will come later.

Customization and privacy​

Crucially, Microsoft added clear toggles under Settings > Personalization > Start so users can hide the Recommended feed entirely, show more pinned items by default, or switch between the new views. This pushback against overly promotional or predictive UX nudges is a significant usability win for users who prefer a classic app launcher with minimal recommendations. That said, the categorization is automatic and not user-editable in the first wave — a notable limitation for admins and power users seeking deterministic layouts.

Taskbar updates: battery visibility, previews, and Copilot tie-ins​

New battery icon & percentage​

The Taskbar battery icon has been refreshed with color-coded states — green for charging/healthy, yellow at or below 20% (energy-saver state), and red for critical — and a simplified overlay that no longer obscures the percentage bar. Microsoft also added an option to show battery percentage directly next to the Taskbar icon (Settings > Power & battery → Battery Percentage). The same icons extend to the lock screen. This is a long-requested usability fix for laptop users who wanted real-time numeric feedback without opening Quick Settings.
A cautionary note: the battery percentage feature and the colored icons have previously been trialed and temporarily pulled for fixes in earlier previews. Expect a phased rollout and occasional toggles for insiders as Microsoft tunes UX and telemetry. Community threads showed some users losing the new icon during interim rollbacks.

Animated previews and “Share with Copilot”​

Window thumbnail previews on hover gain more fluid animations, restoring a behavior many users recall from earlier Windows generations. More provocative is the addition of a “Share with Copilot” button under the thumbnail preview. Clicking that triggers Copilot Vision to scan the visible content of that window and offer contextual assistance or follow-up actions. Microsoft lets you disable this at Settings > Personalization > Taskbar > Taskbar behaviors with “Share any window from my taskbar.” While powerful for productivity and quick answers, this tight integration raises immediate questions about user intent and consent: sharing content with Copilot is opt‑in by default, but the feature’s placement under a familiar hover preview risks accidental activation.

File Explorer: recommended files, Copilot actions, and developer hooks​

Recommended feed and hover actions​

File Explorer Home gains a Recommended feed for personal Microsoft accounts and local users: recently opened or downloaded files, activity on shared files, and items surfaced by system heuristics. Hovering over an item provides quick actions like Open file location and Ask Copilot. The feed can be disabled from File Explorer Folder Options; when off, pinned Quick Access folders reappear. These UX moves aim to reduce hunting for recently used documents and to make Copilot a first‑class helper in everyday file tasks.

StorageProvider APIs​

Microsoft exposed StorageProvider APIs so cloud providers can integrate suggested file signals into File Explorer Home, enabling third‑party cloud clients to participate in the Recommended experience. This is a notable developer-friendly change: cloud storage ecosystems can now offer richer on‑device discovery without custom shell extensions.

Region and account gating​

A practical but inconvenient trade-off: some features in File Explorer’s Copilot and Recommended area are gated by account type (personal Microsoft accounts first; enterprise Entra ID support planned later) and by region (EEA exclusions for certain AI experiences at first). Enterprises and privacy-conscious users should review policies and opt-out options during initial rollout.

Copilot, Click to Do, and on‑device AI: features and hardware gates​

Click to Do and Copilot integration​

Click to Do gains new capabilities: a typed prompt box that sends selected on-screen content to Copilot, on-screen text translation, unit conversions, freeform selection modes, table detection and “Convert to table with Excel,” and Live Persona Cards for Microsoft 365 users. Some of these features are region-restricted (EEA, China) or hardware-restricted to Copilot+ PCs. These interactions increasingly treat Copilot as a context-aware assistant rather than a detached chat window.

Fluid Dictation and Voice Access​

Voice Access gets Fluid Dictation, an on‑device feature powered by small language models (SLMs) that improves real‑time grammar, punctuation, and filler‑word handling. It runs locally on Copilot+ PCs for privacy and latency advantages and is enabled by default in supported locales. The app also adds Japanese support and configurable wait times before executing voice commands. These additions are important for accessibility and for users who rely on voice-driven workflows.

Copilot+ PC hardware requirements​

A recurring caveat: several advanced on‑device features are gated to Copilot+ PCs, devices equipped with high‑performance NPUs that meet Microsoft’s 40+ TOPS specification. Microsoft’s Copilot+ documentation and hardware guides confirm the 40‑TOPS threshold and list qualifying silicon and devices; independent coverage (Tom’s Hardware, WIRED) explains the rationale and hardware realities. In short: if your device lacks a qualifying NPU, you’ll still get many UI and cloud‑based Copilot features, but the fastest, lowest‑latency on‑device experiences — and certain exclusive features such as fastest Click to Do tooling and enhanced Recall — will be limited or absent.

Security, privacy, and enterprise considerations​

  • Data handling and consent: Copilot Vision’s “Share with Copilot” is enabled by default in previews but can be turned off. Admins should understand defaults for telemetry, sharing, and local processing when deploying widely. The placement of Copilot toggles inside System Settings and the Taskbar behaviors panel gives admins reasonable policy surfaces to control exposure.
  • Regional regulations: Microsoft explicitly notes some Copilot experiences and AI-powered features will not initially be available in the EEA and China — a reflection of regulatory and product‑compliance complexity. Enterprises operating internationally should expect staggered availability and validate behavior in targeted geographies.
  • Manageability: The update will be delivered as an enablement package for many devices (24H2 → 25H2 model), minimizing downtime; enterprise policies and OMA‑URI/Intune options exist to enable or disable certain previews (Administrator Protection Preview, app management). IT teams should test these builds in a lab before wide deployment.

Risks, limitations, and friction points​

1. Phased rollout and inconsistency​

Staged activation means inconsistent end-user experiences across a mixed estate. Some users will have the new Start while others do not, complicating documentation, training, and support. Enterprises must plan for mixed UI states for weeks after the initial GA activation.

2. Hardware gating and perceived fragmentation​

Features tied to Copilot+ NPUs (40+ TOPS) create a two‑tier Windows experience. While performance gains on NPU‑equipped devices can be real, the split raises questions about fairness and upgrade economics: not every user or business can justify new devices simply to get the best Windows features. This is a strategic trade-off as Microsoft leans into on‑device AI.

3. Privacy and accidental sharing​

“Share with Copilot” in the Taskbar preview is conveniently placed but risks accidental activation. Microsoft provides settings to disable sharing, but discoverability and clear consent UI matter. Organizations handling sensitive data should enforce policy controls early.

4. Regional exclusions and regulatory uncertainty​

EEA and China exclusions for certain Copilot features mean EU customers and administrators must verify availability and compliance before relying on Copilot-dependent workflows. These rollouts may be delayed or require different privacy guardrails in each market.

5. Changing visuals and muscle-memory loss​

Visual changes — a new Start surface, modified taskbar clock, and shifted context menus — require re-training. Users who’ve developed workflow muscle memory may find temporary productivity hits. IT teams should plan targeted communications and short “what’s changed” guides for frontline staff.

Practical advice for enthusiasts, IT pros, and admins​

  1. Join the Release Preview Channel only on non‑critical devices if you want early access; phase testing across a small pilot group.
  2. Document the toggles: Start Personalization settings, Taskbar behaviors (particularly the Copilot sharing toggle), and File Explorer Folder Options (to disable Recommended) for helpdesk scripts.
  3. For enterprises: map Copilot+ feature dependency in your app catalog. If teams rely on fast on‑device AI, plan hardware refresh cycles around Copilot+ qualification (40+ TOPS NPUs) or remain on cloud Copilot options.
  4. Test Print/Display and input scenarios thoroughly: recent previews included fixes for stuck-on-screen content and pen/ink regressions; ensure these areas are validated in your test pass.
  5. Communicate region availability to overseas branches; some Copilot and Click to Do experiences are being phased into the EEA and China later than other markets.

Why this matters for Windows 11’s future​

This feature drop is emblematic of three broader forces shaping Windows today:
  • Polish over pivot: Microsoft is shipping fewer headline revolutions and more iterative refinements that target daily friction — Start discoverability, a readable battery icon, and File Explorer ergonomics. These are small changes with outsized daily impact.
  • AI at the interface: Copilot is migrating from a sidebar to an ambient, contextual assistant woven into Start, Explorer, Taskbar previews, and Click to Do. The strategy is to make assistance immediate and task-focused rather than a separate workflow. The risk is complexity and the need for careful consent design.
  • Hardware differentiation: By gating the sharpest on‑device experiences to Copilot+ PCs, Microsoft is signaling that future Windows features will increasingly leverage local NPUs. That pushes the hardware ecosystem forward but fragments the feature set along device capability lines.

Final take​

The Release Preview staging of this Windows 11 feature drop marks a meaningful, pragmatic step forward: the Start menu redesign addresses longstanding discoverability complaints, Taskbar tweaks improve everyday battery visibility and interactivity, File Explorer gets sensible discovery upgrades, and on‑device AI features move the platform toward lower-latency, private processing. Those wins come with clear caveats: phased rollouts, regional gating, hardware‑dependent features, and new consent surfaces around Copilot. For consumers, the update will feel like solid polish and quality‑of‑life progress; for IT teams, it’s a call to plan pilot deployments and policy guardrails.
Microsoft’s Release Preview changelog and independent hands‑on coverage confirm the major elements described here — but timing and availability remain phased and region-/hardware‑dependent. Expect the rollout to broaden in the coming weeks if telemetry and feedback are positive, and prepare for mixed experiences during the transition.

(Technical changelog details and the Release Preview build notes are embedded in Microsoft’s Release Preview announcement and in multiple preview reports; readers deploying this across fleets should consult the official Release Preview build notes and internal test results for the precise list of fixes and known issues before broad rollout.)

Source: Windows Central Microsoft prepares major Windows 11 feature drop with new Start menu, Taskbar updates, and more | New features expected to roll out next month
 

Microsoft has started rolling the redesigned Start menu and a raft of on-device AI features to Windows Insiders on the Release Preview Channel via update KB5067036, bringing the new Start UX, colored battery icons, Copilot Vision taskbar sharing, File Explorer enhancements, and Copilot+‑only features to testers ahead of a broader public rollout.

Windows-style app grid on a monitor with a Share with Copilot card.Background​

The Start menu refresh is the most visible element of a larger, multi-stage evolution of Windows 11’s interface and on-device AI capabilities. Microsoft first surfaced pieces of the new Start experience in Dev/Beta previews earlier in the Insider program cycle and has been iterating the design across Canary, Dev, Beta, and now Release Preview rings before a general release. This phased approach matches Microsoft’s recent update cadence for major UI and AI changes, which includes gating certain experiences by hardware (Copilot+ PC) and region (EEA exclusions).
The official Release Preview announcement names the builds and describes the features: Build 26100.7015 for Windows 11 version 24H2 and Build 26200.7015 for version 25H2. Those builds are distributed under KB5067036 and contain both the redesigned Start menu and a set of other visible and behind‑the‑scenes changes.

What’s new in KB5067036 — at a glance​

  • Redesigned Start menu with a top-level, scrollable “All” surface and three viewing modes (Category, Grid, List). The menu adapts to screen size and remembers your last selected view. A Phone Link button sits next to Search to expand/collapse phone content.
  • Colored battery icons on taskbar and lock screen with an option to show battery percentage in the system tray. Green indicates charging/healthy, yellow signals ≤20% energy‑saving state, and red is critical.
  • Copilot Vision integration in the taskbar, adding a “Share with Copilot” button to taskbar window thumbnails so Copilot Vision can analyze a window’s visible content (user‑controllable in Taskbar settings).
  • File Explorer improvements, including Recommended files in File Explorer Home for personal and local accounts (with regional exceptions), hover‑commands like Open file location and Ask Copilot, and StorageProvider APIs for cloud suggestions.
  • Voice Access — Fluid Dictation (Copilot+ PCs): real‑time grammar, punctuation, and filler‑word correction using on‑device small language models; enabled by default on supported Copilot+ hardware in English locales.
  • Click to Do improvements (Copilot+ PCs): on‑screen translation, unit conversions, table detection with “Convert to table with Excel,” Freeform selection mode, typed prompt box for Copilot, and more. Some features are hardware and licensing gated and may require Microsoft 365 in commercial scenarios.
These are visible, functional changes rather than purely cosmetic tweaks; Microsoft frames the release as both usability and AI integration updates intended to make discovery and content actions easier across the OS.

Deep dive: the redesigned Start menu​

What changed, exactly​

The Start menu moves from the compact two‑pane Pinned + Recommended layout to a single vertically scrollable canvas with a prominent “All” section at the top. Within that top level you can select between:
  • Category view (default): groups apps by functional buckets and surfaces frequently used items.
  • Grid view: an alphabetical, tile-like grid with more horizontal spacing for faster scanning.
  • List view: a classic alphabetical list for users who prefer the old flow.
The UI is responsive: on larger screens Microsoft has demonstrated layouts that can show up to eight columns of pinned apps, multiple recommendation slots, and several category columns to reduce clicks and make app discovery faster. The menu also remembers your last chosen view so the experience persists across sessions.

Why this matters for everyday users​

A scrollable, single-surface Start reduces friction for users who install many apps and previously had to jump into the “All apps” page. The Category view aims to surface apps by purpose (e.g., productivity, entertainment), which accelerates access for people who rely on category mental models. The Phone Link integration further folds phone notifications and quick actions into the Start surface, which streamlines cross‑device workflows for those who pair their phone with Windows.

Considerations for power users​

  • The loss of the ultra‑compact three‑row pin area some users preferred may be a tradeoff for discoverability on big displays.
  • The added density on large monitors is welcome, but the new UI may require a short relearning period — particularly for keyboard‑centric users who depended on the legacy layout.
  • The Start menu still allows hiding Recommended content, preserving an escape hatch for users who prefer a minimalist layout.

Taskbar changes and battery UI updates​

Colored battery icons and battery percentage​

The system tray’s battery icon now uses color to communicate state at a glance: green for charging/healthy, yellow for energy‑saving or ≤20%, and red for critically low. Microsoft also introduced a Settings toggle to show battery percentage next to the icon: go to Settings > System > Power & battery and toggle Battery Percentage. The lock screen will adopt the same visual treatment. These are small UX changes, but they address long‑standing user requests to make battery state more immediately readable and to optionally display the percentage without expanding quick settings.

Why it matters​

Color‑coding increases “at a glance” comprehension for non-technical users and reduces the number of clicks required to check battery health. The optional percentage is pragmatic — many users wanted a persistent readout without needing to hover or open a flyout. For enterprise fleets, admins should note whether new color semantics align with internal documentation or training materials to avoid confusion.

Copilot Vision in the taskbar — capabilities and privacy implications​

How the integration works​

Hovering over an open app icon now surfaces a thumbnail preview that includes a Share with Copilot button. Selecting that button invokes Copilot Vision to scan the visible contents of that window and offer context-aware actions, such as summarization, extraction, translation, or follow-up Copilot prompts. Microsoft provides a user‑facing opt‑out: the behavior can be disabled under Settings > Personalization > Taskbar > Taskbar behaviors using the “Share any window from my taskbar” checkbox.

Strengths​

  • Makes Copilot Vision accessible without full-screen screen‑share or separate upload steps.
  • Faster path from seeing content to acting on it (translate, summarize, extract data).
  • Integrates visual AI into desktop workflows in a way that mirrors common user behaviors (hover → preview → action).

Risks and governance​

  • Invoking Copilot Vision performs a local or cloud‑assisted analysis of a window’s contents, which raises immediate privacy and data governance flags for sensitive or regulated content.
  • Although Microsoft exposes a toggle to disable automatic sharing, the affordance is highly discoverable and may be enabled by default on some personal devices. Organizations should evaluate the feature for compliance with internal data‑loss prevention (DLP) policies.
  • Admins in managed environments should consider Group Policy, Intune, or OMA‑URI controls to centrally disable the capability until a reviewed policy and user training are in place.

File Explorer: recommendations, Copilot actions, and storage provider hooks​

What changed​

File Explorer Home now surfaces Recommended files to personal Microsoft accounts and local accounts in supported regions; the feature is toggleable for users who prefer not to see suggested items. Hovering over a file in File Explorer Home can surface new quick actions, including Open file location and Ask Copilot, and Microsoft has introduced StorageProvider APIs so third‑party cloud providers can integrate their own suggested files and recommendations. Some parts of this rollout are excluded or delayed in the European Economic Area and other regions.

Practical benefits​

  • Faster access to recently relevant documents and automatic surfacing of likely next files.
  • Contextual Copilot actions reduce friction for quick tasks like locating the source of a document or asking Copilot to summarize an item without opening a separate app.

Caveats​

  • The recommendation surface raises questions about local vs. cloud telemetry and whether suggestions are based on local metadata or cloud indexing — organizations with strict data residency needs should audit the behavior.
  • Regional exclusions mean administrators and users in the EEA should expect a delayed experience compared with other markets.

Voice Access — Fluid Dictation and Click to Do (Copilot+ hardware gating)​

Fluid Dictation (Voice Access)​

On Copilot+ devices, Windows Voice Access receives a Fluid Dictation mode that uses on‑device small language models to correct grammar and punctuation and remove filler words in real time. The feature is enabled by default in English locales on Copilot+ PCs and has secure‑field exceptions (it’s disabled in secure password fields). Japanese language support and a delay setting for voice command execution were also added. For users who depend on dictation for accessibility, this is a meaningful quality-of-life update.

Click to Do enhancements​

Click to Do, the on‑screen selection capture that invites Copilot actions, now supports:
  • On‑screen translation and unit conversion (length, area, volume, height, temperature, speed).
  • Table detection with “Convert to table with Excel” (functionality may require Copilot+ hardware and Microsoft 365 in commercial scenarios).
  • Multiple selection modes including Freeform selection.
  • A typeable prompt box to refine Copilot queries before sending captured content.
These capabilities are clearly aimed at turning ephemeral screen captures into structured, actionable data.

Hardware and licensing gating​

Many of the most advanced Click to Do actions are gated to Copilot+ PCs or to users with Microsoft 365 Copilot licenses, especially for Excel conversion and certain advanced persona features. Enterprises should verify device inventories and licensing before planning a departmental rollout.

Deployment timeline and who sees what — clarifying the dates​

Microsoft’s Release Preview blog entry for KB5067036 documenting Builds 26100.7015 and 26200.7015 was published on October 21, 2025, and details the features rolling out to Release Preview Insiders. Earlier hands‑on coverage and Dev‑channel previews demonstrating the Start menu redesign began surfacing during June 2025. Reports that suggested an October/November 2024 public rollout do not match the official Microsoft rollout dates for KB5067036; timelines in early reporting were speculative and have been superseded by Microsoft’s Insider Blog posts. Readers should treat older timeline claims about 2024 general availability as inconsistent with Microsoft’s official release notes.
Note: the Release Preview distribution means features are being validated across a wider set of real‑world machines, but Microsoft still performs a gradual feature rollout, so not all Insiders will see each change immediately. Expect staged exposure over days or weeks.

Recommended actions — for enthusiasts, administrators, and enterprises​

For Windows Insiders and enthusiasts​

  • Join the Release Preview Channel via Settings > Windows Update > Windows Insider Program to receive KB5067036 if you want to test the new Start menu and related changes.
  • After installing, test Start menu views (Category, Grid, List) and note how the menu adapts on different display DPIs.
  • Try the Phone Link button to confirm phone integration works for your Android or iOS device and report issues in Feedback Hub.
  • If you’re privacy‑conscious, check Settings > Personalization > Taskbar > Taskbar behaviors and disable the “Share any window from my taskbar” option if you prefer to avoid Copilot Vision scanning.

For IT administrators and security teams​

  • Inventory Copilot‑capable hardware and Microsoft 365 Copilot licensing to map who will receive Copilot+ gated features.
  • Evaluate and document the privacy and DLP implications of Copilot Vision window scanning and File Explorer “Ask Copilot” actions. Consider centrally disabling sharing affordances until DLP rules and user training are in place.
  • Use Group Policy, Intune, or OMA‑URI to control rollout of administrator‑sensitive features (Microsoft’s release notes mention Administrator Protection Preview options that require policy configuration).

For power users who dislike change​

  • Hide recommended content in Start or revert view preferences in Settings > Personalization > Start, and give feedback if you encounter regressions or layout problems. The Start menu remembers the last selected view, which helps restore a preferred workflow across reboots.

Strengths, trade‑offs, and risks — critical analysis​

Notable strengths​

  • Improved discoverability: The scrollable “All” surface reduces friction for users with lots of apps and improves the chance of surfacing useful apps without extra clicks.
  • Practical small UX wins: Colored battery icons and optional percentage fill long‑standing user requests and help non‑technical users quickly understand device health.
  • Productivity through context: Copilot Vision and Click to Do provide smoother transitions from seeing content to acting on it (translate, summarize, export), which can speed common tasks.

Trade‑offs​

  • Discoverability vs. control: The new Start menu is more discoverable but introduces choices that some users may find cluttered, especially on small screens. The interface changes benefit large displays most; compact laptop users may need to customize the layout.
  • Fragmented experience: Hardware gating (Copilot+), licensing constraints (Microsoft 365 requirements), and regional exclusions (EEA/China) mean the set of features any given user sees will vary widely, complicating documentation and internal support.

Risks that deserve attention​

  • Privacy and data governance: The “Share with Copilot” affordance and File Explorer Copilot actions can surface sensitive content to on‑device or cloud‑assisted models. Enterprises must treat these as potential data exfiltration vectors and apply DLP and policy controls accordingly.
  • Usability regressions: Major reworks of core UI surfaces carry the risk of short‑term regressions (e.g., unexpected context‑menu behavior, or discoverability changes that break keyboard workflows). Microsoft’s release notes include fixes for File Explorer and taskbar issues, but Insiders should test workflows closely.
  • Support overhead: Help desks will need updated scripts and training to explain why features appear differently across user machines (Copilot+ vs non‑Copilot, EEA exceptions, etc.), which could temporarily increase support tickets.

Testing checklist for Release Preview Insiders​

  • Confirm build number: verify you received Build 26100.7015 (24H2) or Build 26200.7015 (25H2) after installing KB5067036.
  • Try all Start views: switch between Category, Grid, and List and confirm the menu remembers your choice.
  • Verify Phone Link behavior: pair an Android or iOS device and test the Phone Link sidebar from Start.
  • Validate battery icon states: unplug, run to ≤20%, and plug in to observe yellow, red, and green states; check Settings > Power & battery to enable percentage display.
  • Exercise taskbar Copilot sharing: hover an app icon and test the “Share with Copilot” flow; then disable the setting and confirm sharing is blocked. Log any data or privacy surprises.
  • Test Click to Do and Fluid Dictation on Copilot+ hardware if available; otherwise, note gating and licensing prompts.

Final assessment​

KB5067036 represents a substantive incremental update to Windows 11: the Start menu redesign improves discoverability and scales Start across a wider range of displays, battery icon improvements tackle long‑standing usability requests, and the Copilot/Click to Do pipeline directly connects visual context to AI‑assisted actions. For users and organizations prepared to manage the privacy and governance consequences, the changes stand to materially speed routine tasks and improve clarity.
However, the rollout is intentionally fragmented: Copilot+ hardware, regional exclusions, and Microsoft 365 licensing create a patchwork of experiences that will complicate support, analysis, and training. The most consequential risk is privacy and DLP exposure from Copilot Vision’s window scanning and new File Explorer actions; Microsoft provides toggles and admin controls, but organizations should proactively inventory risk and apply policy controls before enabling these features fleet‑wide.
The Release Preview distribution is a chance for broader but controlled testing. Insiders, IT pros, and accessibility advocates should use this window to validate workflows, confirm that new AI features respect data handling requirements, and collect feedback while Microsoft completes the gradual public rollout.

Conclusion: the Start menu redesign and the set of KB5067036 features mark a deliberate step toward a more discoverable, AI‑infused Windows 11. The updates promise real productivity gains when configured carefully, but the combination of hardware gating, licensing requirements, and privacy surface area requires deliberate testing and governance before enabling these features in production environments.

Source: Thurrott.com Windows 11’s Redesigned Start Menu is Now Available for Release Preview Testers
 

Back
Top