Windows 11 Start Menu Redesign in KB5067036 Preview: Fluid, Context Aware Launcher

  • Thread Author
Microsoft has begun rolling out a redesigned Start menu for Windows 11 as part of the KB5067036 preview packages, delivering a more fluid, context‑aware layout, tighter mobile integration, and a string of productivity‑focused refinements that signal a shift away from a fixed Start experience toward a dynamic, screen‑aware launcher.

Blue Windows-like app launcher with pinned and all apps sections.Background​

Microsoft released the preview builds tied to KB5067036 to the Release Preview Channel on October 21, 2025, targeting Windows 11 versions 24H2 (build 26100.7015) and 25H2 (build 26200.7015). The package is being rolled out as a controlled feature update—many features are gated server‑side and will appear gradually for subsets of devices.
This staged delivery model is part of Microsoft’s ongoing “continuous innovation” strategy: the company ships features in dormant state in monthly updates, then activates them later via service flags or enablement packages. That makes the visible experience on any one PC dependent on Microsoft’s rollout schedule and device compatibility checks rather than solely on installing a single cumulative update.

What changed: Start menu redesign explained​

The Start menu update is the headline item in KB5067036 and represents the most visible redesign of the Start surface since Windows 11’s initial launch. The new Start menu emphasizes discoverability and adaptability rather than a single rigid layout.
  • The main screen now contains a scrollable All surface that integrates pinned apps, the All apps list, and recommendations into one continuous view. This reduces context switching between separate panes and puts more content on a single canvas.
  • Two distinct views are available for the apps list: Category view (groups apps by type and surfaces frequently used apps) and Grid view (an alphabetical grid that’s easier to scan horizontally). The Start menu remembers the last view you selected.
  • Sections such as Pinned and Recommended can be shown or hidden, letting users free up space and reduce clutter without third‑party tools. The layout is responsive—it automatically adjusts pinned and recommended sizes based on screen real estate (wider or taller displays show more items).
These changes are intended to make reaching apps faster with fewer taps or clicks, and to provide a Start menu that behaves more like a modern, adaptable launcher than a static grid.

Category view and grouping behavior​

Category view creates groups automatically when a cluster of apps meets grouping thresholds (for example, three or more related apps). If the system can’t form a logical group, items fall into an Other bucket. This behavior reduces manual organization work while surfacing commonly used or related apps together. The grouping logic is on‑device and tuned to reduce noisy or irrelevant categories.

Grid view and alphabetic scanning​

Grid view is a more traditional alphabetic list with increased horizontal spacing and clearer item affordances, designed for fast visual scanning and keyboard navigation. For users who prefer the familiarity of an alphabetic index, Grid view reduces cognitive overhead when searching for seldom‑used programs.

Mobile integration: Phone Link appears in the Start surface​

One of the more practical changes is a Phone Link pane integrated into the Start menu, exposed as a collapsible button next to Search. When a phone is paired, the pane can surface recent notifications, message previews, and quick reply actions directly in the Start panel—cutting down on context switches to a separate Phone Link window. The feature supports both Android and iOS devices in most markets, though Microsoft has noted region‑based availability differences and phased rollouts.
This tighter phone‑to‑desktop coupling aims to save time for users who regularly glance at notifications and respond to messages while working. It does not replace full Phone Link functionality (calls, deep photo transfers, app streaming) but is useful as a quick glance + action surface. Because the feature is rolling out gradually, not all paired devices will see the Phone Link pane immediately.

Taskbar and interface refinements​

KB5067036 also includes a range of smaller but meaningful refinements across the taskbar and other UI elements that improve day‑to‑day polish.
  • Battery icon improvements: the taskbar battery icon can now show a persistent battery percentage (“perma‑percent”) and color‑coded icons (green when charging or healthy, yellow for low battery), making state information easier to parse at a glance. The same visual treatment is applied to the lock screen’s battery indicator.
  • Thumbnail hover animations: hovering over taskbar icons produces more refined thumbnail previews, and Microsoft has added new micro‑interactions such as a “Share with Copilot” shortcut on window thumbnails in some builds. These are subtle UX changes but reduce friction for users who use hover previews and taskbar multitasking every day.
  • Taskbar icon resizing behavior: in earlier 24H2 previews Microsoft introduced logic to compress or resize icons when space runs low; this continues to be refined in the October/November preview.
These are examples of the kind of quality‑of‑life improvements that add cumulative value—even when individual changes appear small.

How Microsoft is rolling this out—what to expect​

The Start menu redesign and associated changes in KB5067036 are being deployed via a controlled feature rollout. That means:
  • The preview builds were published to the Release Preview Channel on October 21, 2025, as optional/preview updates.
  • Devices set to “Get the latest updates as soon as they’re available” are more likely to receive the visible features early; Microsoft applies safeguards to withhold features from systems with known incompatibilities.
  • Microsoft has indicated the broader release to stable channels will align with November Patch Tuesday (the company’s notes point to feature parity and broader enablement by the November security update cycle). Expect a phased rollout to continue into November.
Because of this approach, seeing the update in Windows Update doesn’t guarantee every change will immediately show up—server‑side flags and A/B testing can delay activation or selectively enable features.

Getting the changes early (ViVeTool) — steps and caveats​

Enthusiasts have used community tools to force‑enable dormant features that Microsoft gates. KB5067036’s feature set has been unlocked by ViVeTool IDs shared in community guides; typical steps reported include:
  • Installing the preview update for your build (26100.7015 or 26200.7015).
  • Running ViVeTool with the feature flag IDs to flip the on‑device toggles (community guides show IDs for the Start redesign and battery percentage).
  • Restarting to surface the changes.
Important caveats: ViVeTool is a community, unsupported utility that modifies internal feature flags. Using it can expose unfinished features, create stability regressions, and may bypass safeguards Microsoft placed for hardware or driver compatibility. It also can make it harder to receive official troubleshooting or support. Enthusiasts who are comfortable with troubleshooting can use it, but production systems and enterprise endpoints should avoid this route and wait for Microsoft’s official rollout.

Enterprise and OEM implications​

The redesign also introduces additional hooks for OEMs and IT administrators to adapt the desktop to varied form factors. Microsoft calls out the potential for OEMs and IT pros to tune the Start experience for tablets, foldables, large‑screen PCs, and traditional laptops—through policy and layout controls such as Start pins configuration. Enterprise customers are advised to pilot the update via Windows Autopatch or targeted Autopilot deployments before broad deployment.
Administrators should consider:
  • Testing app‑pin policies and Start configuration settings to ensure custom Start layouts survive the change.
  • Validating driver, security, and application compatibility because feature activation may introduce new UI elements or background services.
  • Planning staged rollouts using Microsoft’s channel options (Release Preview, optional stable installs, and Patch Tuesday enablement).

Power‑user and community reactions so far​

Early community signals show a mix of enthusiasm and caution. Power users appreciate the new view options and the ability to hide recommendation sections without hacks, but there are also reports of edge‑case regressions and behavior changes:
  • Some users reported that removing the Recommendations section (or toggling certain Start settings) interacts unexpectedly with jump lists and pinned action behavior, which can disable features they rely on. These reports are mostly community posts and should be treated as user‑reported issues while Microsoft evaluates telemetry.
  • A gradual rollout means not everyone sees the changes at the same time, producing confusion when users compare machines or discuss the update across forums.
These community reports are useful early signals but are not definitive proof of systemic regressions—Microsoft’s phased approach allows the company to pull or adjust features in response to such feedback.

Security, privacy, and accessibility considerations​

The Start menu and Phone Link surface changes raise a few considerations worth calling out for admins and privacy‑minded users:
  • Privacy: surfacing phone notifications and message snippets in the Start surface is convenient, but it increases the number of places sensitive content can appear on a desktop (lock screen, Start, Phone Link window). Organizations with strict data handling policies should consider guidance on paired device use and notification content.
  • Accessibility: Microsoft’s release notes indicate wider accessibility work continues across Windows 11; the Start changes include memory of last view and larger hit targets in Grid view, which can improve discoverability for some assistive scenarios. Still, accessibility teams should validate the new flows (category grouping, collapsible panes) with their assistive tech stacks.
  • Security: enabling additional inter‑device integration increases the attack surface in theory—Phone Link requires authentication and pairing; enterprises should enforce device‑pairing policies and ensure endpoints are protected by up‑to‑date security agents.
Where claims about behavior are based on community testing (for example, exact grouping thresholds or animated micro‑interactions), those details should be treated as provisional until Microsoft publishes full documentation in its release notes.

How to decide when to adopt​

For most consumer users, the recommended approach is:
  • If you’re on a personal device and like to try new UI changes early, enable “Get the latest updates as soon as they’re available” and monitor Windows Update for the optional KB5067036 preview entry. Expect a staged rollout—some features may appear immediately, others later.
  • If you rely on a work PC or need rock‑solid stability (developers, creatives, enterprise users), hold on and test the update first on a non‑critical machine or a small pilot group. Use Windows Autopatch / Intune pilot rings for controlled deployment.
  • Avoid third‑party techniques (ViVeTool) on production systems. If attempting early enablement on a test device, back up critical data and be prepared to roll back the preview package if issues arise.

Strengths and risks — critical analysis​

Strengths
  • The redesign is a thoughtful evolution rather than a radical break: it increases discoverability, adds flexible views, and adapts to different screen sizes, which suits the modern hardware mix of laptops, tablets, and foldables. The addition of the Phone Link pane is a pragmatic productivity win for users who want glanceability without a full Phone Link context switch.
  • The combination of small UI refinements—battery percentage, colored battery icons, thumbnail tweaks—addresses real daily frictions and shows Microsoft prioritizing polish. These changes compound into a smoother, more informative desktop experience.
  • The controlled rollout model protects a large installed base from sudden regressions while allowing Microsoft to iterate quickly on UX and telemetry‑driven fixes.
Risks and open questions
  • Because many changes are server‑gated, users receive inconsistent experiences across devices and time, which can complicate support and community guidance. That mismatch creates confusion for help desks and peer troubleshooting.
  • Some community reports suggest feature interactions (for example, when hiding Recommendations) affect other functionality like jump lists. These user‑reported edge cases indicate Microsoft still needs to tune the interactions between legacy Start behavior and the new surface. These claims remain partially unverified at scale and should be treated as early warnings rather than confirmed regressions.
  • Using community tools to flip hidden flags can surface unstable code and bypass Microsoft mitigations. That’s useful for enthusiasts and testers, but it increases risk for average users who may not have the experience to recover from stability issues.

Practical checklist for Windows 11 users and administrators​

  • For consumers who want the new Start now:
  • Enable “Get the latest updates as soon as they’re available” in Settings > Windows Update.
  • Check Windows Update for optional preview packages (KB5067036 in Release Preview).
  • If comfortable with community tools, use ViVeTool only on non‑critical machines and follow reputable community guides—expect instability and no vendor support.
  • For IT administrators:
  • Pilot the update with a small set of devices and validate Start pin policies, jump list behavior, and notification handling.
  • Use Autopatch and staged deployment rings to manage exposure and rollback if issues surface.
  • Review data handling policies for paired devices and notification content if Phone Link will be permitted on corporate devices.

Conclusion​

KB5067036’s Start menu redesign is a meaningful, pragmatic update: it brings flexibility, better discoverability, and practical mobile integration to Windows 11’s most used launcher. The changes reflect a maturation of design thinking—moving the OS toward context awareness and adaptable UI surfaces that scale across device classes.
At the same time, the phased rollout and gated activations mean the experience will be uneven for a short while, and community reports point to a handful of interaction edge cases that still require attention. Users who value polish and early access can opt into preview channels, while businesses and stability‑focused users should plan staged testing and rollouts. Overall, Microsoft’s approach balances rapid iteration with cautious deployment; the redesigned Start is a welcome step forward that will need a few refinement cycles to settle into everyday reliability.

Source: India.Com Microsoft rolls out redesigned Start Menu for Windows 11 with smarter layout and productivity-boosting features
 

Microsoft’s optional preview update KB5067036 delivers a targeted, practical repair for a frustrating Windows Update failure — error 0x800f0983 — and also patches a long‑running “Update and shutdown” behavior that sometimes left machines powered on after applying updates, while bundling a raft of UI, accessibility and on‑device AI enhancements that are being rolled out gradually.

Windows Update card showing KB5067036 with a green checkmark and hammer icon on a laptop screen.Background / Overview​

Microsoft published Release Preview notes on October 21, 2025 announcing Builds 26100.7015 (Windows 11 24H2) and 26200.7015 (Windows 11 25H2) under the KB5067036 umbrella. The update is delivered as an optional preview (Download & install) in Windows Update and as MSU packages via the Microsoft Update Catalog for offline or enterprise deployment.
KB5067036 is not just a single fix — it is a mixed preview that contains:
  • Reliability and servicing fixes (including the 0x800f0983 install failure and the Update-and-shutdown bug).
  • Shell and productivity changes (Start menu redesign, File Explorer Home enhancements, new taskbar affordances).
  • Accessibility and on‑device AI improvements (Fluid Dictation, Voice Access, Click-to-Do integrations).
    Administrators and enthusiasts should treat it as a preview/validation release: binaries arrive on machines but many features are server‑gated and will be enabled progressively.

What exactly was broken — the 0x800f0983 problem explained​

Error code 0x800f0983 is a Windows Update/servicing failure that most often signals problems in the Component-Based Servicing (CBS) pipeline or component store corruption. The common pattern reported by users is a successful download followed by a failed installation that rolls back — leaving the device on the previous build and generating repeated retries. Standard local remediation (SFC /scannow, DISM /Online /Cleanup-Image /RestoreHealth) sometimes helps but has not been a universal cure.
Why it mattered:
  • Failed installs lock devices into a cycle of retry/rollback or force help‑desk intervention.
  • Some users and admins adopted heavier workarounds (in‑place repair installs, offline MSU application, or, less preferably, clean installs).
  • For organizations, repeated failures can delay security patching and create operational churn.
Microsoft’s engineering notes and community reporting indicate that KB5067036 contains servicing‑stack and component‑store fixes that reduce the specific failure modes tied to 0x800f0983 — the change targets underlying update sequencing and CBS edge cases that were surfacing after recent cumulative rollups. This makes KB5067036 particularly useful as a repair path for devices that were previously failing with that error code.

The Update-and-shutdown bug: small symptom, outsized annoyance​

A simpler but long‑standing annoyance: choosing Update and shutdown sometimes did not result in the PC powering off after installation completed; instead the machine was left on — often returning to the lock screen or desktop. That behavior drained laptop batteries, confused users expecting a shutdown, and broke some scripted workflows that assume a power‑off after updates. Microsoft has acknowledged and included a fix for this behavior in the Release Preview builds tied to KB5067036.
Independent outlets and the Windows Insider blog confirm the fix is in preview builds, with testing and staged rollouts still underway. Users should expect the behavior to be corrected once the fix graduates into broader cumulative updates, but caution is warranted during preview deployment.

How to get KB5067036 (installation paths and practical notes)​

  • Consumer / safe path (recommended)
  • Settings → Windows Update → Check for updates → look for the optional/preview entry for KB5067036 → Select Download & install → Reboot when prompted.
  • Manual offline path (enterprise or disconnected)
  • Download MSU packages from the Microsoft Update Catalog that match your architecture (x64, ARM64) and the target build series.
  • Use DISM if injecting multiple packages:
  • DISM /Online /Add-Package /PackagePath:C:\Packages\Windows11.0-KB5067036-x64.msu
  • Reboot when installation completes and follow package ordering Microsoft specifies if multiple MSUs are present.
Practical notes:
  • KB5067036 is a preview/optional package; it will not be automatically applied by forced security rollups unless Microsoft folds the fixes into a future cumulative.
  • Offline MSU install sometimes requires prerequisite servicing stack updates (SSUs). Verify the package information in the Update Catalog before offline deployment.

Troubleshooting guidance when you hit 0x800f0983​

If you’re experiencing repeat failures with 0x800f0983, follow an ordered approach that balances safety and speed:
  • Pause aggressive remediation: stop automatic retries to avoid repeated rollbacks.
  • Built‑in troubleshooters: Settings → Windows Update → Troubleshoot.
  • Run system health checks:
  • sfc /scannow
  • DISM /Online /Cleanup-Image /RestoreHealth
  • Reset Update components (Windows Update service, SoftwareDistribution, catroot2) if the above show inconsistencies.
  • Install optional preview: check the optional updates area — Microsoft sometimes exposes a targeted fix in a preview KB that resolves the failure.
  • Offline MSU approach: apply the KB5067036 MSU(s) from Update Catalog if Windows Update refuses to progress.
  • In‑place repair (repair upgrade): mount an official Windows 11 ISO and run setup.exe → Keep personal files and apps. This replays servicing but preserves data and apps.
  • Last resort: back up and clean install only after other remediation paths are exhausted.
These steps track Microsoft’s documented guidance and community‑validated workflows; they are standard practice for servicing and component‑store anomalies. When in doubt, test recovery approaches on a non‑critical device first.

What else KB5067036 brings (features and admin implications)​

KB5067036 also includes a number of user‑facing and platform changes that are being rolled out gradually and can affect administration and compliance:
  • Start menu redesign: scrollable All, Category and Grid views, improved responsiveness and Phone Link integration. Feature exposure is gradual and may be server‑gated.
  • File Explorer Home: Recommended files, hover quick actions including “Ask Copilot”, and new StorageProvider APIs for cloud vendors. Enterprises can toggle Recommended in Folder Options or manage via MDM.
  • Taskbar and battery UI: colored battery icons and an option to always show battery percentage in Settings → Power & battery. Taskbar thumbnails may include a “Share with Copilot” action that invokes Copilot Vision — administrators should evaluate DLP implications.
  • Accessibility and on‑device AI: Fluid Dictation (Voice Access), improved language support, and local SLMs for private, low‑latency dictation and table extraction workflows. Some of these capabilities require Copilot+ hardware or Microsoft 365 licensing for full functionality.
  • Administrator Protection: a preview feature that can require Windows Hello verification before granting elevation — off by default and manageable via OMA‑URI (Intune) or Group Policy. Test escalation workflows for scripted installers and management agents.
These additions are meaningful for productivity and accessibility but increase the surface area for privacy, licensing and compliance controls. Administrators should review feature gating (hardware, region, Microsoft 365 entitlements) before broad enablement.

Critical analysis — strengths, limits and risks​

Strengths​

  • Targeted reliability fixes: KB5067036 addresses concrete, high‑impact servicing failures (0x800f0983) and the Update-and-shutdown bug, which directly reduce user friction and help‑desk load. This demonstrates Microsoft’s ability to push targeted fixes via preview channels.
  • Meaningful, practical UX improvements: Start redesign, File Explorer refinements, and battery UI changes are small but accumulate into better day‑to‑day usability. The new StorageProvider APIs open integration opportunities for third‑party cloud vendors.
  • On‑device AI and accessibility gains: Fluid Dictation and local SLMs provide improved dictation and lower privacy exposure for users in sensitive contexts. When implemented correctly these features can reduce cloud egress and latency.

Limits and caveats​

  • Preview nature and server gating: Installing the update supplies binaries, but many features are controlled server‑side and may not appear immediately. That makes feature verification inconsistent across test devices. Relying on feature-appearance as proof of a successful install is a common pitfall.
  • Hardware and licensing fragmentation: Several Copilot and Convert-to-Excel features require Copilot+ certified hardware or Microsoft 365 licensing. This produces uneven experiences across mixed fleets and complicates rollout plans.
  • Risk of preview regressions: Optional preview updates act as broad field tests; they can introduce new regressions even as they fix other issues. Recent months have already shown an out‑of‑band emergency patch was needed to repair WinRE USB input regressions introduced by an earlier rollup. Admins must weigh the tradeoff between early fixes and potential instability.

Operational recommendations (high priority)​

  • Build a pilot ring: test KB5067036 on representative hardware for at least 48–72 hours including apps, sign‑in flows, virtualization networking, and VoIP/media playback.
  • Validate recovery: confirm you can boot into WinRE, use rescue ISOs and offline servicing paths, and have clear rollback steps (uninstall preview KB or restore image).
  • Update DLP & governance: review Click-to-Do, Copilot Vision, and taskbar sharing policies in enterprise settings; consider disabling share affordances until controls are proven.
  • Confirm licensing & hardware entitlements: verify Microsoft 365 subscriptions and Copilot+ hardware eligibility for specific AI features before planning user enablement.

Cross‑validation and verification​

Key load‑bearing claims (fixing 0x800f0983, Update-and-shutdown, Release Preview builds and build numbers) were verified against:
  • Microsoft Windows Insider blog release notes for Builds 26100.7015 and 26200.7015 (KB5067036).
  • Independent reporting and update coverage (BleepingComputer, Pureinfotech, Windows Central / TechRadar summaries) confirming the same fixes and rollout behavior.
  • Community/operational advisories and deployment notes captured in the uploaded forum files that document practical installation paths, troubleshooting steps (DISM/SFC), and pilot recommendations.
If you require absolute certainty about which specific devices or tenants will see a given Copilot or Start menu feature on a particular date, treat any timing claims as provisional: feature exposure is controlled by server‑side flags and regional/licensing gates, and timings can change. For mission‑critical rollouts, confirm entitlements directly via tenant admin controls or Microsoft commercial support.

Practical checklist for home users and admins (concise)​

  • Home users:
  • If you’ve seen 0x800f0983: try Windows Update Troubleshooter, run SFC/DISM, then check Optional updates for KB5067036. If that fails, use the Microsoft Update Catalog MSU or perform a repair in‑place with an official ISO.
  • If you rely on automatic stability, consider waiting for the fixes to appear in a cumulative Patch Tuesday rollup (the preview serves validation purposes).
  • IT admins:
  • Create a small pilot ring (mix of Copilot+ hardware and standard devices).
  • Validate update flow, Windows Hello elevation scenarios, File Explorer behaviors, and recovery procedures.
  • Ensure offline packages and up‑to‑date SSUs are available for offline remediation.
  • Update DLP and Intune/GPO to control Copilot sharing until policies are confirmed.

Conclusion​

KB5067036 is a pragmatic preview release that merges real servicing fixes — notably for the vexing 0x800f0983 install failure and the persistent Update-and-shutdown behavior — with a broader set of UI, accessibility and on‑device AI features that Microsoft is rolling out gradually. For users and admins who have been blocked by repeated 0x800f0983 failures, installing this preview (or waiting for its inclusion in the next cumulative) offers a clear path to resolution. At the same time, the preview nature of this KB means measured, staged deployment is the right operational posture: test, validate recovery, and lock down data‑sharing affordances before enabling Copilot‑driven integrations at scale.
For immediate remediation of update failures, follow the standard troubleshooting order (troubleshooter → SFC/DISM → optional preview/MSU → in‑place repair) and keep a recovery ISO handy. For enterprise deployments, pilot widely, assess hardware/licensing gates, and update governance and DLP policies to control the new assistant‑centric surfaces the update introduces.
In short: KB5067036 patches important servicing pain points and ships compelling productivity and accessibility improvements — but it also highlights the balance organizations must strike between early adoption of fixes and disciplined testing to avoid preview‑induced regressions.

Source: Windows Report KB5067036 Fixes Windows 11 Update Error 0x800f0983 & Shutdown Bug
 

Back
Top