Windows 11 Start Menu Redesign with KB5067036: Scrollable Surface and All Apps Views

Microsoft has begun rolling out a long‑anticipated redesign of the Windows 11 Start menu, delivered as an optional, non‑security preview update (KB5067036) that introduces a single, scrollable Start surface, multiple “All apps” layout modes, deeper Phone Link integration, and more granular personalization controls aimed at restoring discoverability and user choice to the OS.

Background​

Since Windows 11’s launch, the Start menu has been one of the most contentious parts of the user interface: Microsoft favored a centered, minimalist approach that many users found elegant but constrained, especially for dense app collections and power workflows. The new release responds directly to that feedback by reworking Start from a two‑pane interaction model into a unified, vertically scrollable canvas with view options that prioritize discoverability and customization.
Microsoft packaged the change as part of the Release Preview / optional preview servicing update labeled KB5067036, which increments builds for Windows 11 version 24H2 and 25H2 (notably builds 26100.7019 and 26200.7019 in the public preview). The update is distributed as an optional preview so that Microsoft can continue staged enablement and server‑side feature gating while collecting telemetry and user feedback.

---

What changed: feature snapshot​

The redesign focuses squarely on making the Start menu more discoverable, customizable, and better integrated across devices. The headline changes include:

• Single, scrollable Start surface — Pinned apps, Recommended items, and the All apps listing now sit on one continuous vertical canvas, eliminating the separate All‑apps page and reducing clicks.
• Three All apps views — Users can choose between:
• Category view, which groups apps into functional buckets (Productivity, Games, Creativity, Communication, etc.)
• Grid view, a denser alphabetical grid with larger icons for visual scanning
• List view, the classic alphabetical list many users still prefer
  The Start menu remembers the last view you selected.
• Customizable sections — Toggle off or hide the Recommended files/apps area, collapse or expand the pinned grid, and control layout density via Settings > Personalization > Start.
• Phone Link integration — A mobile device button next to Search opens a collapsible Phone Link panel inside Start, surfacing recent notifications, messages, missed calls, and quick phone controls for paired Android and (in selected markets) iOS devices.
• Responsive layout — The Start canvas adapts to display size; larger screens show more columns of pinned apps and categories by default.

These are not cosmetic tweaks alone — the update shifts how users navigate and discover installed applications on Windows 11.

---

How Microsoft is delivering the redesign​

Microsoft’s deployment model for this update follows the same conservative, telemetry‑driven pattern that’s become common for recent Windows feature work:

• The change appears in Insider channels and Release Preview as binaries become stable in servicing branches.
• Microsoft publishes KB5067036 as an optional, non‑security preview update for devices on 24H2 and 25H2; installing the preview package does not guarantee immediate activation of the redesigned Start because features are enabled progressively using server‑side feature flags (staged rollout / A/B testing).
• Wider deployment is expected to be folded into the normal Patch Tuesday cadence once the preview passes telemetry and feedback gates.

Practical takeaway: you may install KB5067036 and not see the redesigned Start immediately; conversely, some devices may get the new Start via Microsoft’s server‑side enablement before others even with the same build number.

---

Why this matters (strengths)​

The redesign addresses several concrete user complaints and adds features that matter in daily use:

• Faster app discovery — Consolidating Pinned, Recommended, and All apps into one surface reduces clicks and cognitive switching. For users with long app lists, the scrollable surface and Grid/Category views make scanning faster than navigating separate panels.
• Better use of modern displays — The Start canvas scales to larger screens, showing more content and therefore reducing the need to hunt across cramped lists. This improves workflows for large external monitors and multi‑monitor setups.
• More personalization — The ability to hide Recommended items, persist the chosen All apps view, and collapse pinned groups gives users real choices about density and emphasis. That’s a win for people who have asked for Windows to “get out of the way” and let them prioritize their own apps.
• Tighter cross‑device continuity — Bringing Phone Link into Start lowers friction for quick phone interactions while working on a PC, reducing context switching and keeping essential communications visible alongside app launch controls.

These strengths together make the redesign especially beneficial for users who juggle many applications, those who work across phone and PC, and environments where faster, at‑a‑glance access to tools restores productivity.

---

Risks, limitations, and unanswered questions​

No redesign is without tradeoffs. The rollout and architecture of this change introduce several points that IT pros and power users should weigh carefully.

1. Inconsistent user experience during staged rollout​

Because Microsoft uses server‑side gating, different machines — even in the same office or the same Microsoft account — can display different Start behaviors at the same time. That inconsistency complicates documentation, support scripts, and training materials for help desks and enterprise IT. Organizations should expect a transitional period with mixed experiences.

2. Limited manual control over Category grouping​

Category view groups apps automatically; current previews indicate Microsoft controls categories (generation is automatic and not user‑editable). That behavior risks misclassification and may frustrate power users and admins who need deterministic layouts for managed devices. There’s no sign yet of a manual reclassification UI or enterprise policy to pin categories explicitly.

3. Privacy and surface‑area concerns with Phone Link in Start​

Exposing phone notifications, messages, and other mobile content inside Start increases the feature’s convenience but also brings privacy considerations. On shared machines or in visible office setups, phone content surfaced in Start can reveal personal or sensitive information. Admins and users should verify pairing permissions, configure what the Phone Link pane displays, and consider whether to disable the feature for shared devices.

4. No guaranteed rollback to the old Start UX​

Microsoft’s documentation around KB5067036 focuses on feature toggles and personalization but does not offer a built‑in “revert to legacy Start” switch. Early reporting suggests there is no native one‑click rollback to the pre‑redesign Start once the update is applied, though users can hide or disable specific sections (for example, Recommended or Phone Link) through Settings. This makes pilot testing important before broad deployment. This point should be considered tentative — Microsoft has not publicly documented a global revert option in the preview notes and may adjust behavior based on feedback.

5. Power‑user and third‑party substitution dynamics​

Third‑party Start replacements such as Start11, StartAllBack, and Open‑Shell have served users unhappy with Windows 11’s default Start for years. The redesigned Start narrows the gap but may not satisfy users who need deterministic, scriptable layouts or who rely on advanced features those third‑party tools provide. Enterprises that standardize on a particular Start layout should test whether the new Start breaks or complements their chosen third‑party tooling.

---

Rollout, installation, and a quick how‑to​

For readers who want to try the redesigned Start now, here’s a practical checklist.

• Confirm your Windows 11 edition is running 24H2 or 25H2 (the preview targets both servicing branches).
• Enable “Get the latest updates as soon as they’re available” in Settings > Windows Update to be eligible for preview distribution, or join the Release Preview/Windows Insider channel if appropriate for testing.
• Check Windows Update: the package appears as Preview update (KB5067036) with the new build number (e.g., Build 26200.7019). Select Download & install or use the Microsoft Update Catalog to fetch the standalone .msu package if you prefer manual installation.
• Restart after installation. If the redesigned Start does not appear immediately, remember that Microsoft often enables new features server‑side; you may need to wait for the roll‑out to reach your device.

For administrators planning a staged pilot:

• Create a pilot update ring and restrict KB5067036 to a small set of test machines.
• Document expected changes and prepare quick support scripts that show users how to hide Recommended content and disable Phone Link if needed.
• Monitor Telemetry and user feedback, and prepare a broader rollout plan for Patch Tuesday once Microsoft declares the preview stable.

---

Enterprise and IT management considerations​

Enterprises should treat KB5067036 like any other optional feature preview: test, measure, and control. Specific recommendations include:

• Pilot first — Deploy the update to a controlled set of users across different roles (knowledge workers, developers, heavy app users) and collect UX/compatibility feedback before wider deployment.
• Update rings and feature policies — Use Windows Update for Business and MDM policies to stagger deployments and maintain control over which devices are eligible for optional preview updates. Documented deployment best practices remain the right approach here.
• Privacy settings — For machines in public spaces or shared environments, consider disabling Phone Link integration or controlling which users can pair phones to their devices. Audit paired devices and review consent settings.
• Support documentation — Prepare guidance for help desks on toggling Recommended items, switching All apps views, and addressing complaints about mismatched category groupings or missing icons.

These practical controls give IT teams leverage to balance user choice with organizational compliance and supportability.

---

UX critique: design, discoverability, and the AI angle​

The Start menu overhaul signals an important product design pivot for Microsoft: prioritizing discovery and context over the rigid minimalism of early Windows 11. The addition of Category view — which uses heuristics to group apps — is a notable move toward AI‑assisted organization; however, it raises two concerns.
First, accuracy and predictability: auto‑grouping is useful for typical consumer app sets but may produce surprising results with smaller or specialized app catalogs (internal LOB apps, legacy tools). Administrators and users who rely on deterministic layouts may find this frustrating. Evidence from early previews shows categories are generated automatically and currently lack manual editing.
Second, explainability: when the OS groups apps, users should be able to understand why a grouping occurred and how to correct it. Without a clear edit path, trust in the feature diminishes. For enterprise use, Microsoft will need to provide management controls or ways to pin and persist groupings to gain broader acceptance. The product signals are promising, but the delivery must include control surfaces to satisfy power users and admins.

---

Practical tips for power users​

• If you prefer a dense, deterministic app list, switch to List view and hide the Recommended area to replicate a classic Start experience while still retaining improved discovery for one‑off lookups.
• For faster keyboard navigation, test whether the new Start preserves search hotkeys and arrow navigation in your environment; if you rely on third‑party launchers, validate compatibility before committing.
• If Phone Link surfaces content you don’t want visible on a shared PC, toggle it off in Settings > Personalization > Start or disable Phone Link pairing for that device session.

---

What the redesign means for Microsoft’s broader strategy​

The Start redesign is consistent with Microsoft’s evolving platform strategy: make Windows the hub for device‑centric productivity, tighter integration across mobile/PC/cloud, and a richer surface for Copilot and other AI features. Bringing Phone Link into Start and adding category/grouping semantics are both steps toward a more contextual desktop that anticipates user needs.
At the same time, Microsoft’s staged rollout model and the continued use of optional preview updates underline a cautious approach — the company wants to collect behavioral telemetry and iterate based on real user data before committing changes broadly. That pragmatic, data‑driven posture reduces the risk of mass regressions but increases short‑term variability for users.

---

Caveats and unverifiable claims​

Some narrative threads circulating in commentary and coverage — for example, claims about irrevocable UI changes, or sweeping shifts in Microsoft’s partnership structures with OpenAI tied directly to this UI work — are not substantiated by Microsoft’s technical release notes or the official KB documentation. Where reporting speculates about corporate strategy or downstream AI governance, those claims should be treated as unverified until Microsoft publishes explicit announcements or documentation. Any such assertions in public commentary require careful cross‑checking against official Microsoft communications.

---

Final assessment and recommendation​

The Windows 11 Start menu redesign in KB5067036 is a pragmatic, user‑driven revision that meaningfully improves app discovery, adds sensible personalization options, and moves Start toward closer device integration. For most users the changes will be positive: faster discovery, better use of screen real estate, and a more flexible launcher model.
However, the staged rollout model, automatic category grouping, and Phone Link surface area raise practical concerns around consistency, control, and privacy — especially in managed or shared environments. Organizations and power users should pilot the preview, prepare support guidance, and verify compatibility with existing tooling and workflows before broad adoption.
For individual users who crave immediate benefit without corporate constraints, enabling the preview and toggling to your preferred view will likely yield an immediate productivity win. For IT admins, a cautious, measured pilot remains the best path forward.

---

Microsoft’s Start redesign is more than a visual refresh: it represents a philosophical reset that acknowledges user feedback and embraces practicality over strict minimalism. The approach is not without tradeoffs, but it restores choice and discoverability to the Start experience — the very aspects many Windows users have been asking for since 2021.

---

Source: TechRepublic Windows 11 Update Brings Customizable Start Menu and Streamlined App Discovery

 

[ChatGPT]

Windows 11 users installing the optional October preview update (KB5067036) have reported a baffling Task Manager bug that leaves the app running after it’s closed, spawning duplicate taskmgr.exe processes that can quietly eat memory and CPU and make a PC feel sluggish.

Background / Overview​

KB5067036 is an optional, non‑security preview cumulative update published for Windows 11 in late October 2025 that ships fixes and a handful of visible feature updates — notably a redesigned Start menu experience and updated battery indicators — and several under‑the‑hood corrections. Because this is a preview (optional) release, Microsoft delivers it as a staged rollout: some features are enabled server‑side and not every device will see visual changes immediately. That rollout model also means the package gets wider testing in the field before more complete distribution via regular cumulative updates.
Community reports surfaced within days of the package’s release describing two sets of stability problems: (1) some devices failing to install the update cleanly or presenting update error codes, and (2) an odd Task Manager regression where closing Task Manager with the window “X” does not actually terminate the process. The latter is the focus here because it’s both reproducible and capable of producing measurable system slowdowns if left unchecked.

---

What users are seeing: the Task Manager duplication bug​

Symptom summary​

• Open Task Manager (Ctrl+Shift+Esc), then click the window “X” to close it.
• Reopen Task Manager and inspect Processes → Background processes.
• Instead of a single Task Manager entry, additional Task Manager entries appear; the count increases each time Task Manager is opened and closed using the window close control.
• Each “stuck” taskmgr.exe instance remains resident in memory and continues polling system telemetry, so multiple copies accumulate resource usage over time.
• Systems with multiple accumulated Task Manager instances can show visible slowdowns, stuttering UI, longer app launch times, or higher idle CPU and RAM usage.

How bad can it get?​

Community testers reported that each zombie Task Manager instance typically consumes a modest amount of RAM (reports commonly cite ~20–30 MB per instance), but that adds up quickly if users repeatedly open and close the app. One tester demonstrated tens to hundreds of instances, which translated into multiple gigabytes of RAM used and noticeable system sluggishness. The performance impact depends on how many duplicates accumulate and the baseline resources of the PC: machines with limited RAM or heavy background workloads will be affected more quickly.
These observations come from broad community reporting and hands‑on tests performed by power‑user sites and user forums during the rollout window. The behavior is reproducible on affected builds by simply opening and closing Task Manager repeatedly and watching taskmgr.exe appear under Background processes.

---

Why this probably happened (technical context and hypothesis)​

Microsoft’s official notes for the preview update indicate they made changes to Task Manager behavior in this release — specifically a fix intended to correct scenarios where apps weren’t being grouped correctly with their processes. That wording confirms the update modifies Task Manager internals.
The most likely explanation is that an internal change intended to improve process grouping or UI‑level grouping logic inadvertently broke the clean shutdown path for Task Manager windows in at least some runtime configurations. When an app fails to perform its normal shutdown housekeeping — unregistering callbacks, stopping timers, or releasing internal references — the process can stay resident even though the visible window has closed. Opening the app again starts a fresh process, and the old one remains, so successive opens/close cycles multiply the number of resident taskmgr.exe processes.
That theory aligns with what community testers observed: the duplication began after the update that included a Task Manager change, and the duplicate processes are listed as background processes (not foreground windows), which suggests the GUI is torn down while process threads remain.
It’s important to stress this is a plausible technical explanation based on public release notes and community testing; Microsoft has not publicly released a detailed post‑mortem for this specific symptom as of October 30, 2025. Treat the cause as likely but not formally confirmed until Microsoft publishes a fix note.

---

Other update issues reported alongside the Task Manager problem​

While the Task Manager symptom is the most visible, community reports during KB5067036’s early rollout also documented:

• Update installation failures on some systems, sometimes stopping at 100% and then rolling back or throwing error codes. Users reported various error codes in community threads.
• A limited number of scattered reports describing severely degraded systems after the update (some users described needing to uninstall the update or use recovery options to restore normal operation). These reports appear to be outliers but underscore the risks of installing optional preview packages on production machines.
• Feature rollout inconsistency: because certain UI changes are staged server‑side, installing KB5067036 does not guarantee immediate appearance of the new Start menu or other visible features.

These are primarily community and forum reports collected during the preview rollout window. They do not represent universal behavior, and many users installed the preview without incident. Nevertheless, the mixed experiences argue for caution before installing preview updates on mission‑critical systems.

---

How to verify whether your machine is affected​

• Open Task Manager (Ctrl+Shift+Esc) and close it using the window “X.”
• Reopen Task Manager and expand the Processes list.
• Look under “Apps” and “Background processes” for multiple entries labeled Task Manager.
• Alternatively, run a quick command in PowerShell or Command Prompt:
• PowerShell:
  Get-Process -Name taskmgr
• Command Prompt:
  tasklist /FI "IMAGENAME eq taskmgr.exe"

If these commands return more than one taskmgr.exe entry after you’ve closed and reopened the UI a few times, your device is affected.

---

Immediate fixes and workarounds​

If your PC is showing duplicate Task Manager processes and you notice degraded performance, there are several practical ways to clear the stuck instances and avoid further impact.

Fast kill (single command)​

Open an elevated Command Prompt or a normal Command Prompt and run:
taskkill /im taskmgr.exe /f
This forcibly terminates all running Task Manager processes in one step. It’s the quickest remedy if multiple zombie instances exist.

PowerShell alternative​

Open PowerShell and run:
Get-Process -Name taskmgr | Stop-Process -Force
This accomplishes the same result for PowerShell‑centric users.

Manual end‑task​

If you prefer the GUI:

• Open Task Manager (Ctrl+Shift+Esc).
• In the Processes tab, locate each Task Manager entry under Background processes.
• Select it and choose End task for each instance.

That’s tedious for large counts, but works.

Workarounds to avoid creating duplicates​

The issue centers on using the window “X” to close Task Manager. Community testers found that instead of clicking the “X,” you can avoid the duplication by:

• Ending the Task Manager process from within Task Manager (select the process and click End task), or
• Using the keyboard shortcut to close windows (Alt+F4) — anecdotal testing suggests behavior may differ across systems; if Alt+F4 triggers a proper shutdown on your device, it’s a safer close method until an official fix arrives.

If performance has already degraded​

• Run taskkill once to clear the instances.
• Restart the PC to ensure no lingering background activity remains.
• If performance problems persist after killing the processes and rebooting, consider uninstalling the preview update (steps below) or restoring from a system restore point.

---

How to uninstall KB5067036 (roll back the preview)​

If you installed KB5067036 and prefer to revert until the issue is resolved, use the built‑in Windows update rollback tools. Note that not all packages are uninstallable (some servicing stack or mandatory packages are non‑removable); preview quality updates are generally removable, but follow these steps carefully and make sure you have recent backups.

• Open Settings (Windows + I) → Windows Update → Update history.
• Scroll to Related settings and select Uninstall updates.
• In the Control Panel dialog that opens, find the most recent Microsoft Windows update that matches the KB number and choose Uninstall.
• Follow prompts and reboot when the system requests.

If Windows will not boot normally, use the Advanced Startup Environment:

• On the sign‑in screen, hold Shift and select Restart (or use a recovery drive / installation media).
• Choose Troubleshoot → Advanced options → Uninstall Updates.
• Attempt to uninstall the latest quality update or the latest feature update as appropriate.

If the uninstall option is not present or the update is non‑removable, recovery options include using System Restore (if a restore point exists) or performing a repair install with in‑place upgrade media — but those are heavier actions and should be considered last resorts for production systems.

---

Prevention: best practices for updates (especially preview/optional releases)​

• Avoid installing preview/optional updates on production or mission‑critical systems. Preview updates are precisely that — pre‑release testing material. They can fix issues but can also introduce regressions.
• Use restore points or image backups before installing any optional updates so you can roll back quickly.
• Delay feature/preview updates on managed fleets via Windows Update for Business, WSUS, or SCCM until a wider validation window closes.
• If you have a “Get the latest updates as soon as they’re available” toggle enabled, consider disabling it if you want to avoid being offered preview releases unexpectedly.
• Monitor official Windows Release Health pages and patch notes before installing optional updates. When in doubt, wait for the next cumulative release through Patch Tuesday, which typically incorporates fixes discovered during the preview period.

---

Enterprise considerations and mitigation​

• For IT managers, the presence of a bug that can cause background processes to multiply and drain resources — even modestly — is a legitimate operational risk when it spreads across many endpoints.
• Recommended actions for enterprises:
• Block or defer installing optional preview updates across the fleet until vendor guidance confirms the issue is resolved.
• Use group policies or Windows Update for Business rings to keep at‑risk systems on a more conservative cadence.
• If a small test group has already installed the preview and experiences the Task Manager duplication, enforce a remediation script (taskkill or PowerShell stop) via existing management tooling to clear instances automatically.
• Headline monitoring: add a quick health check or script to detect multiple taskmgr.exe instances and report back to central management so remediation can be automated if necessary.

---

Risk analysis: strengths and threats exposed by this incident​

Strengths (what the update fixes or improves)​

• KB5067036 bundles legitimate fixes that matter: a corrected Media Creation Tool behavior for some Arm64 devices and several quality and UI tweaks.
• The staged rollout model lets Microsoft validate features on a broader set of real‑world configurations beyond Insider channels.
• Community reporting and rapid sharing on forums mean regressions get noticed quickly, which shortens the window between regression and fix when Microsoft engages.

Risks and weaknesses​

• Preview updates shipped to broad user bases can expose production machines to regressions. The Task Manager bug is an example where a targeted internal fix introduced an unforeseen regression in a core system tool.
• End users are serving as de‑facto QA when preview updates are optional but widely available, and that increases the odds of encountering edge‑case failures.
• Staged feature rollouts plus preview packages make troubleshooting more complex — applying the same KB to two computers may produce different behavior depending on feature‑flight flags and device configuration.
• Fragmented reporting (different error codes, scattered bricked reports) complicates triage. Community reports of installation failures and, in rare cases, devices needing recovery highlight the potential for serious impact even with a non‑security preview update.

---

What Microsoft has (and hasn’t) said — transparency status​

Microsoft’s published preview notes for KB5067036 document several fixes and feature changes related to Task Manager, updates, and Media Creation Tool behavior. However, as of October 30, 2025, Microsoft had not issued a formal, public acknowledgement specifically describing the Task Manager duplication symptom or a targeted hotfix for it. Community reporting picked up the issue quickly, and power‑user sites and forums circulated kill‑commands and rollback guidance while Microsoft investigates.
When Microsoft does publish an updated release note or a corrective package, it will typically appear in the Windows Release Health dashboard or in an updated support article for the KB. In the meantime, users and administrators should treat community guidance as actionable mitigation — but also keep a close watch on official channels for a supported fix.

---

Practical checklist: quick actions for affected users​

• Confirm symptom: open/close Task Manager and watch for multiple taskmgr.exe entries.
• Clear duplicates: run taskkill /im taskmgr.exe /f or PowerShell Stop-Process as above.
• Reboot to stabilize the system.
• If you installed KB5067036 and prefer not to risk further regressions, uninstall the preview update via Settings → Windows Update → Update history → Uninstall updates.
• If you run critical systems, roll back any affected machines, and pause pushing optional updates to the rest of the fleet.
• Keep a current image backup and create a restore point before applying future optional updates.
• Monitor Microsoft Release Health and apply the next cumulative update once Microsoft confirms the bug fix.

---

Conclusion — measured caution is the right approach​

Preview and optional cumulative updates are useful testing grounds for new features and fixes, but they are exactly that: pre‑release work that can behave differently across hardware, drivers, and third‑party software. The reported Task Manager duplication in KB5067036 is an uncomfortable reminder that even a minor change in how a core tool manages processes can cascade into real user pain when it prevents proper shutdown of background processes.
For everyday users and IT teams the prudent course is clear: avoid optional preview updates on production machines, back up before applying optional updates, and apply simple mitigations (taskkill, uninstall) if you find yourself affected. For Microsoft, the path is also straightforward — investigate, patch, and communicate. The community discussion has already provided reproducible steps and diagnostics; now it’s time for a supported fix and an official confirmation to close the loop.
Until then, use the quick commandline fixes to reclaim resources, uninstall the preview if you prefer stability, and treat optional updates with caution.

---

Source: TechRadar https://www.techradar.com/computing...-could-slow-down-your-pc-heres-how-to-fix-it/

 

[ChatGPT]

Microsoft has begun rolling out a substantial refresh of the Windows 11 Start menu as part of the optional October 28, 2025 preview update (KB5067036), introducing a single, vertically scrollable Start surface, multiple "All apps" view modes, tighter Phone Link integration, and a handful of taskbar and File Explorer refinements that together aim to restore discoverability and customization to the launcher while remaining gated behind Microsoft’s staged rollout model.

Background / Overview​

Since Windows 11’s debut, the Start menu has been a recurring point of user feedback: praised for a cleaner aesthetic but criticized for reduced discoverability and the extra step required to reach a full alphabetical app list. KB5067036 represents the most visible Start rework since Windows 11’s launch, packaging the redesigned Start surface into a non‑security preview update for Windows 11 versions 24H2 and 25H2. Microsoft shipped the preview bits on October 28, 2025 as OS builds 26100.7019 and 26200.7019 and is enabling the experience progressively via server‑side feature flags and phased rollout.
The update is being delivered as an optional preview for devices that have opted into receiving early feature releases; a broader rollout is expected to follow the usual Patch Tuesday cadence after telemetry and compatibility checks. That delivery model — shipping binaries but controlling activation — is central to how administrators and enthusiasts should approach KB5067036.

---

What’s new in KB5067036​

Single, scrollable Start surface (All apps on the main page)​

The most striking change is structural: Start is now a single, vertically scrollable canvas where the full installed-apps inventory sits on the main page instead of behind a separate “All apps” view. This reduces clicks, shortens the path to launch apps, and aligns the desktop launcher with the single-surface app drawers users see on mobile launchers. The Start canvas still surfaces pinned apps and (optionally) recommended files, but those sections now live on the same scrollable surface alongside All apps.
Key points:

• The scrollable All section places the entire app list at prime real estate.
• Pinned apps and Recommended content remain available but can be shown or hidden.

Multiple app-list views: Category, Grid, and List​

You can now choose how All apps is presented:

• Category view — auto-groups apps into functional buckets (Productivity, Games, Creativity, Communication, etc.) and surfaces frequently used apps within those buckets.
• Grid view — a denser, alphabetical grid optimized for horizontal scanning and visual scanning on wider screens.
• List view — a compact A–Z list preserved for keyboard-driven power users.

The Start menu remembers the last view you selected, so your preferred presentation persists across sessions. These modes are meant to offer flexibility: discoverability by intent (Category), fast visual scanning (Grid), or deterministic ordering (List).

Phone Link panel inside Start​

A new mobile device button appears next to Start’s search area. Clicking it expands a collapsible Phone Link panel embedded in Start so you can view notifications, recent messages, calls, and photos from a paired Android or iPhone without opening a separate app. The on‑Start Phone Link panel is designed to make the phone feel like a natural extension of the PC and reduce context switching for common phone workflows. Availability depends on device pairing and region.

Taskbar and battery UI refinements​

KB5067036 also introduces several subtle but useful taskbar refinements:

• Thumbnail animations for taskbar previews that make window switching feel smoother.
• Color-coded battery icons (green = charging/healthy, yellow = battery saver at ≤20%, red = critical) and an option to permanently display battery percentage in the system tray and on the lock screen.

These micro-interactions and visual cues are small individually, but they add up to a more polished and informative system tray experience, particularly for laptop users.

File Explorer, Copilot and accessibility updates​

Beyond Start, the preview bundles a set of File Explorer and Copilot-related improvements:

• File Explorer Home gains a Recommended files surface (toggleable for personal and local accounts) and hover quick-actions like “Open file location” and “Ask Copilot.”
• Copilot/Click to Do enhancements, including a typed prompt box and local prompt suggestions (on Copilot+ hardware) powered by on‑device models.
• Fluid Dictation for Voice Access — on‑device small language models that improve grammar and punctuation in real time on supported Copilot+ PCs.

Some of these features are hardware- or region-gated and will be available only on qualifying Copilot+ devices or after specific rollouts.

---

Deployment, availability, and how Microsoft is rolling this out​

• Microsoft distributed KB5067036 as an optional, non‑security preview on October 28, 2025; the official KB notes list builds 26100.7019 (24H2) and 26200.7019 (25H2).
• The update uses a mixed delivery model: binaries are delivered through the update, but feature exposure is staged via server‑side gating (A/B testing). That means installing the KB may be necessary but not always sufficient to immediately see the redesigned Start.
• Early visibility is limited to devices that opted into receiving the latest features (the “Get the latest updates as soon as they’re available” toggle or Release Preview ring). A wider rollout is expected to follow after Microsoft observes telemetry and addresses regressions.

How to check whether the update is present:

• Press Windows+R, type winver, and confirm your build number is at or above the preview builds (for example, 26100.7019 / 26200.7019). Presence of the build indicates the bits are installed, but not necessarily that the feature flag is enabled.

How to get the redesign sooner (official path):

• Install the optional preview via Settings → Windows Update → Check for updates → Optional updates, or download the package from the Microsoft Update Catalog. Do not use third‑party feature‑flag tools in managed or production environments — they are unsupported.

---

Strengths — why this matters​

• Reduced friction for app discovery. By moving All apps to the main surface and adding a scrollable canvas, Microsoft removes an extra navigation step that hindered fast workflows, particularly for users with many installed programs. Early hands‑on reporting and Microsoft’s notes highlight that this reduces clicks and can speed common launch tasks.
• Flexible personalization. Multiple views and explicit toggles to hide the Recommended area give users real choices. Power users can restore a compact alphabetical list, while casual users can benefit from Category grouping and the visual clarity of Grid view.
• Cross-device continuity. Embedding Phone Link in Start reduces context switches between PC and phone, making messages and notifications easier to act on while working on a PC. This is useful for remote workers and mobile-first users.
• Polish and small wins. The battery percentage toggle, color-coded battery icons, and thumbnail animation tweaks are examples of high-quality UI refinement that improve day-to-day ergonomics for mobile users.
• Platform hooks for the future. StorageProvider APIs and Copilot integration points show Microsoft is broadening the shell’s surface for third‑party integrations and contextual AI actions — potentially enabling deeper productivity scenarios.

---

Risks, caveats, and things to watch​

• Staged rollout means inconsistent visibility. Installing KB5067036 does not guarantee the redesigned Start will appear, because Microsoft flips server‑side flags gradually. That leads to inconsistent experiences across identical machines and can confuse pilot tests if feature exposure isn’t tracked carefully.
• Preview update = preview risk. KB5067036 is an optional, non‑security preview. Historically, preview packages may still contain regressions or interact unpredictably with certain hardware/driver combinations. Administrators should treat this update as a pilot candidate rather than a broad deployment target.
• Active bug reports. Community reports surfaced a Task Manager duplication/closure bug after installing the KB, and other October updates around this timeframe created issues such as WinRE input problems in a separate release. Those reports underline the need to test the full update and not just the Start redesign. Microsoft sometimes issues follow-up fixes in subsequent preview or cumulative updates.
• Hardware and regional gating for Copilot features. Several Copilot/Copilot+ experiences (including local SLM-powered features) are gated to specific hardware classes and regions, and some features are not available in the European Economic Area or China in early phases. Organizations must validate licensing and hardware entitlements before depending on those workflows.
• Privacy and telemetry considerations. The Category grouping logic is automatic and tuned on-device, but the presence of recommended files and Copilot suggestions means administrators and privacy officers should re-evaluate telemetry settings and data handling, especially in regulated environments. Some recommendation surfaces can be toggled off, but policy controls and MDM settings should be audited to ensure compliance.
• Unsupported community workarounds. Enthusiasts may be tempted to force-enable features via unofficial tools; these approaches are unsupported and risk stability and future update compatibility. Enterprises should avoid such methods.

---

Enterprise and IT guidance (practical steps)​

• Treat KB5067036 as a preview pilot.
• Enroll a representative pilot group — including devices with varied hardware profiles and common business apps — and install KB5067036 via Release Preview or Windows Update optional updates.
• Track feature exposure: verify both the OS build (winver) and whether the Start redesign is enabled on each device.
• Verify critical workflows.
• Test sign-in flows, remote management tools, WinRE-based recovery, imaging/tiered provisioning, and business-critical applications — especially anything that hooks into the shell or uses custom shell extensions.
• Check MDM/GPO and Intune settings.
• Confirm whether the new Recommended surfaces or Copilot integrations are compatible with existing privacy/telemetry policies.
• If Administrator Protection preview is relevant, control it through Intune OMA-URI or Group Policy as Microsoft documents.
• Rollout plan.
• Stage the update: pilot → targeted deployment → broad deployment aligned to a cumulative (non-preview) release once Microsoft signals GA for the features you rely on.
• Maintain a rollback or remediation plan: record restore points or recovery media in case a preview triggers regressions on production hardware.
• End-user comms and training.
• Inform users about the new Start views and how to switch between them (Settings → Personalization → Start), and provide guidance on hiding Recommended content if they prefer a minimalist view.

---

Recommendations for home users and enthusiasts​

• If you enjoy early features and can accept preview-level instability: install KB5067036 via Optional updates and wait for Microsoft to flip the feature flag. Use the in-Start toggles to tailor views and hide Recommended files if desired.
• If you prefer stability: skip the optional preview and wait for the redesign to arrive through the normal cumulative update channel after it reaches wider rollout.
• Avoid unsupported tweaks (ViVeTool or similar) on machines where stability matters — these can break future updates and are not recommended by Microsoft.
• If you encounter issues after installing the preview, check Microsoft’s release notes and the Windows release health dashboard for known issues and remediation guidance.

---

Verification of key technical claims (what has been confirmed)​

• Microsoft’s official KB notes for the October 28, 2025 preview (KB5067036) list the redesigned Start menu, scrollable All section, Category and Grid views, Phone Link integration, and the taskbar battery improvements under the OS builds 26100.7019 and 26200.7019. This is the authoritative confirmation of the feature set and the build identifiers.
• Independent coverage by national tech outlets and hands‑on reports confirms the same functional changes: the single-scroll Start surface, multiple views, and responsive layout behavior have been tested and observed by reviewers. These independent accounts corroborate Microsoft’s published notes and provide early user perspectives.
• Community and third‑party reports have already surfaced a few post-installation issues (for example, Task Manager duplication) and other October update-related regressions. These community-flagged problems warrant caution for wide deployments and reinforce the need for testing. Treat these reports as real‑world signals that Microsoft typically addresses in follow-up releases.

Where public documentation is deliberately opaque — for example, exact Copilot+ hardware SKU lists or precise EEA timing for every feature — clause language in Microsoft’s KB notes warns that feature availability depends on device and market. Those items should be validated directly with Microsoft support or through the organization’s Microsoft account manager if precise entitlement and timing details are required.

---

Final analysis — balancing design, control, and rollout mechanics​

KB5067036 is a pragmatic pivot by Microsoft: the Start menu redesign addresses one of Windows 11’s most persistent usability complaints without discarding the OS’s modern visual language. The move to a single scrollable canvas plus multiple presentation modes is sensible and aligns Windows more closely with modern launcher paradigms while restoring choice for different workflows. The Phone Link panel and File Explorer/Copilot touches also reflect a consistent strategy: fold continuity and micro‑AI actions into the places where users already work.
However, the delivery method — shipping the code broadly but gating feature activation — produces an awkward middle state for pilots and admins. You can have the update installed and still not see the feature, which complicates verification and rollout metrics. Preview-level regressions and region/hardware gating for advanced Copilot features further complicate enterprise adoption.
Practically, for home users and IT teams alike, the sensible path is measured: pilot KB5067036, verify device-specific behavior and critical workflows, and then follow Microsoft’s staged signals to expand deployment when the preview evidence and cumulative updates indicate broad compatibility and stability. The redesign itself is a clear usability win; the rollout mechanics are the real operational challenge.

---

The Start menu refresh in KB5067036 is more than cosmetic — it’s a thoughtful rework of how apps and device continuity are surfaced on Windows 11. For people who value discoverability and prefer launcher flexibility, this preview is an encouraging step; for administrators and stability‑sensitive users, a cautious, well‑instrumented pilot remains the right approach.

---

Source: Techlusive Microsoft Refreshes Windows 11 Start Menu: Here’s What’s New In The KB5067036 Update

 

[ChatGPT]

Microsoft has released a corrected Windows 11 Media Creation Tool after a late‑September regression caused the utility to close silently on many Windows 10 machines, restoring the official, single‑file path for creating bootable Windows 11 USB drives and ISOs and offering an official remediation path bundled with an optional preview cumulative update.

Background / Overview​

The Media Creation Tool (MCT) is Microsoft’s lightweight, single‑executable utility for downloading official Windows images and producing bootable installation media. It’s the go‑to option for home users, technicians, refurbishers and small IT teams that prefer a supported “one‑shot” workflow over manual ISO handling or enterprise imaging pipelines. In late September 2025 Microsoft shipped a new MCT binary commonly identified as version 26100.6584, and within days users began reporting a consistent failure: the tool would launch, prompt for UAC, show a brief Windows splash, and then exit with no error and no created media. Microsoft publicly acknowledged the regression and documented it as a known issue that primarily affected Windows 10, version 22H2 hosts.
The timing mattered. Windows 10’s routine support cutoff for Home and Pro editions was a fixed milestone that fell on October 14, 2025, driving a last‑minute surge of migrations, recovery‑media builds, and clean installs. The MCT regression removed the simplest Microsoft‑supported path for many of those users at a high‑pressure moment, forcing fallback to direct ISO downloads or third‑party utilities.

---

What happened: symptoms, scope and early diagnoses​

The visible symptom​

The reported failure mode was immediate and reproducible: double‑click the MCT executable on an affected Windows 10 machine, accept the UAC prompt, observe a split‑second Windows logo, and the process terminates with no error dialog or produced ISO/USB. Event‑log traces and community reproductions frequently showed early crashes referencing SetupHost.exe and low‑level modules, indicating the fault occurred in the tool’s bootstrap or initialization phase rather than during download or write operations.

Platforms and architectures impacted​

Microsoft’s advisory explicitly called out Windows 10 (22H2) hosts as impacted. Reports and community testing also highlighted brittle behavior on Arm64 devices, though Microsoft had previously documented that MCT’s Arm64 workflows were limited or unsupported for creating Arm64‑targeted media from Arm64 Windows 10 hosts — a nuance that added to confusion when Arm‑based users encountered failures. In practice, the problem manifested most widely on Windows 10 22H2 machines, with Arm64 scenarios appearing as a secondary pain point.

What Microsoft confirmed (and what remains unknown)​

Microsoft’s Release Health / Known Issues entry described the problem and identified the offending MCT build metadata as 26100.6584, released on September 29, 2025. The vendor advised affected users to download Windows 11 ISO images directly from the official Software Download page or to use the Windows 11 Installation Assistant until a corrected MCT version was published. Microsoft did not publish a detailed root‑cause post‑mortem or device‑impact telemetry, so the exact internal cause (for example, a compatibility shim, signing/certificate interaction, or a build artifact) has not been publicly verified. That lack of a technical after‑action report means any deep cause analysis is speculative until Microsoft publishes a formal explanation.

---

Timeline: discovery to remediation​

• September 29, 2025 — community reporting and binary identification of Media Creation Tool version 26100.6584 begins after Microsoft updated the tool for the Windows 11 refresh.
• Early October 2025 — users report the silent‑exit behavior on Windows 10 22H2 hosts; Microsoft posts a Release Health note acknowledging the regression and recommending ISO downloads as a workaround.
• October 28, 2025 — Microsoft publishes a refreshed MCT binary and releases an optional preview cumulative update KB5067036 that includes the MCT compatibility correction and a bundle of staged UI and Copilot/feature improvements. Microsoft indicates the issue has been addressed in the updated tool and the KB packaging.
• November Patch Tuesday (planned distribution) — Microsoft intends to fold the preview fixes into the regular cumulative update cadence so the MCT fix reaches mainstream servicing channels. The preview KB is optional and staged; broader rollout follows validation.

This sequence is corroborated by multiple independent community threads and specialist reporting, which reproduced the failure and tracked Microsoft’s advisory and the October 28 remediation packaging.

---

The fix: what Microsoft shipped and how to get it​

Microsoft resolved the symptom by updating the Media Creation Tool binary and packaging compatibility corrections into KB5067036, an optional non‑security preview cumulative update released on October 28, 2025. The KB’s notes list the MCT regression as fixed and also ship a set of staged UI and Copilot‑related improvements aimed at Windows 11 feature flights. Because KB5067036 is a preview, administrators and advanced users can install it from Settings > Windows Update under “Optional updates available,” or obtain the standalone MSU from the Microsoft Update Catalog for manual deployment. Microsoft indicated that the preview fixes will be rolled into the upcoming Patch Tuesday cumulative update for broader distribution.
Important practical notes about the fix:

• Installing the updated MCT executable from the official Microsoft Software Download page should immediately restore the normal media creation workflow on Windows 10 hosts.
• If administrators prefer not to install preview KBs, users can download the corrected MCT directly or continue to use the official ISO download route until the fix arrives via the regular cumulative update channel.
• The preview KB also contains several feature previews that are server‑side gated; installing the package does not guarantee immediate visibility of those features. The staged rollout reduces risk but increases variability in user experience.

---

Safe workarounds while the problem persisted​

When the MCT failed, Microsoft and the community converged on safe and tested alternatives that avoid unsupported or hazardous shortcuts.

• Download the official Windows 11 Disk Image (ISO) for x64 (or Arm64 where applicable) directly from Microsoft’s Software Download page and create bootable USB media using a trusted tool. Microsoft explicitly recommended this as the primary workaround.
• Use the Windows 11 Installation Assistant for an in‑place upgrade on eligible devices when preserving apps and settings is preferred.
• Run the Media Creation Tool from a functioning Windows 11 host to create installers for other machines — a practical cross‑host remediation for imaging teams with a validated x64 creation host.
• Use trusted third‑party USB tools such as Rufus or Ventoy to write a verified Microsoft ISO to a USB drive; these utilities are widely used by technicians and are pragmatic fallbacks. Verify ISO checksums after download.

These approaches keep users on canonical Microsoft media and avoid reliance on patched or unofficial ISOs and registry hacks that carry longer‑term security and compliance risks.

---

Step‑by‑step: create a bootable USB from the official ISO (safe, supported path)​

1. Download the official Windows 11 ISO from Microsoft’s Software Download portal (choose the correct architecture: x64 or Arm64).
2. Verify the ISO SHA‑256 checksum where available to confirm file integrity.
3. Use one of the following methods to create bootable media:
   1. Rufus (run as Administrator) — choose GPT/UEFI or MBR/BIOS depending on target device.
   2. Windows File Explorer + DiskPart — mount the ISO and copy files to a formatted USB (for UEFI/GPT targets ensure an NTFS/UEFI‑bootable layout or use Rufus for better automation).
   3. Ventoy — configure a persistent multi‑ISO USB and copy the ISO file to the Ventoy volume.
4. Boot the target device from USB to install or repair, and ensure Secure Boot/TPM settings match your deployment plan.

This sequence is the recommended fallback path when the MCT is unavailable or untrusted. Keep a validated x64 host for media creation if you regularly build images for diverse architectures.

---

Technical requirements and pre‑flight checks​

Before upgrading to Windows 11 or creating install media, validate these key requirements (the canonical Microsoft checklist):

• 64‑bit CPU (1 GHz dual‑core or better) on Microsoft’s approved list
• TPM 2.0 present and enabled (firmware or discrete)
• UEFI with Secure Boot enabled
• Minimum 4 GB RAM and 64 GB storage (practical installs typically require more)
• Confirm device eligibility with PC Health Check before attempting an in‑place upgrade

These system requirements remain the gating factors for a supported Windows 11 upgrade and should be verified prior to media creation to avoid wasted rebuilds or failed upgrades.

---

Risks, tradeoffs and best practices​

Risks introduced by the regression and Microsoft’s remediation model​

• The MCT regression exposed the fragility of a single‑file convenience tool at a time of high migration volume, increasing the risk that non‑technical users would adopt unsafe or unverified workarounds.
• Microsoft delivered the fix as part of a preview cumulative update that bundles a compatibility correction with feature previews. While this is operationally efficient, bundling fixes with feature flights can be disruptive for users who prefer critical bug fixes to be decoupled from UI experiments. Administrators should pilot preview KBs in controlled rings before wide deployment.

Best practices for administrators and home users​

• Maintain a canonical ISO repository and a validated x64 staging host for media creation to avoid relying solely on per‑device MCT runs.
• Verify ISO checksums and use trusted tools to write media; avoid modified ISOs or registry bypasses unless you fully understand the long‑term support and security implications.
• Back up critical data before attempting upgrades or clean installs. A robust backup is the first line of defense against failed upgrades.

---

Critical analysis: what this episode says about Microsoft’s servicing model​

This incident is instructive on multiple fronts. The Media Creation Tool is a micro‑utility used by millions; when a regression affects it, the operational blast radius is high because the tool is often the default fallback for users outside enterprise imaging pipelines. Microsoft’s modern servicing model — which mixes feature flights, staged rollouts and optional preview KBs — provides flexibility and safety for large feature drops, but it creates friction when a narrowly scoped compatibility fix is bundled with visible feature changes.
Positive aspects of Microsoft’s response:

• The company acknowledged the issue publicly and provided immediate, practical mitigations (ISO download, Installation Assistant, run MCT on Windows 11 host). That transparency reduced user confusion and offered safe fallbacks.
• The fix was delivered relatively quickly and distributed both as an updated tool and as part of a preview cumulative update, increasing the channels by which users could obtain remediation.

Concerns and potential risks:

• Bundling the compatibility fix within a preview KB that also contains feature previews introduces deployment complexity. Organizations that avoid preview releases to maintain stability may have to wait for the next Patch Tuesday to obtain the fix, slowing remediation.
• Microsoft has not released a detailed technical root‑cause analysis or impacted device counts. The absence of public telemetry and a formal post‑mortem means the community and enterprises must rely on anecdotal reproductions and vendor statements, complicating risk assessment and future mitigation planning. This lack of a public post‑mortem should be flagged to readers as an area of uncertainty.

Overall, the episode underscores a perennial tradeoff in modern software servicing: delivering fixes quickly versus controlling the complexity and visibility of simultaneous feature rollouts. For critical tools that serve broad, non‑technical audiences, there is an argument that urgent compatibility fixes should be distributed independently rather than bundled with feature previews.

---

What to do now — practical checklist​

• If you saw the MCT close unexpectedly on a Windows 10 device: download the updated Media Creation Tool from Microsoft’s Software Download page or download the official ISO and create media manually.
• If you manage multiple devices in production: pilot KB5067036 in a small ring, validate imaging and upgrade workflows, and stage the roll‑out based on telemetry. Do not deploy preview updates broadly without testing.
• Keep a validated x64 media‑creation host in your toolkit for cross‑architecture image creation.
• Always verify ISO integrity (SHA‑256), back up critical data, and confirm device eligibility with PC Health Check before upgrading.

---

Closing assessment​

Microsoft’s correction restores the official, supported path for creating Windows 11 installation media and reduces the operational friction introduced at an inopportune time — immediately ahead of Windows 10’s end‑of‑support milestone. The vendor’s public acknowledgement, practical workarounds and the October 28 update demonstrate an appropriate response cadence. However, the incident highlights two persistent tensions: the dangers of single‑file convenience tools breaking in the wild, and the complexities introduced when fixes are packaged alongside feature previews.
For most consumers, the updated Media Creation Tool or the direct ISO route will now resolve the issue. For administrators and imaging teams, the right course is conservative and methodical: validate the preview KB in a pilot ring, maintain a canonical ISO repository and staging host, and avoid ad hoc workarounds that compromise integrity or compliance. Finally, because Microsoft has not published a comprehensive root‑cause analysis or impacted device counts, treat any assertions about scale or precise cause as provisional until an official post‑mortem appears.

---

---

Source: Windows Report Microsoft Fixes Windows 11 Media Creation Tool Issue on Windows 10 PCs