Windows 11 Canary Build 27965: Start Menu Redesign, Edit Editor, and .NET 3.5 Packaging

Microsoft has rolled out Windows 11 Insider Preview Build 27965 to the Canary Channel, bringing the long-teased, redesigned Start menu to early testers — and introducing a set of platform-level changes that matter beyond mere cosmetics, including a shift in how legacy .NET Framework 3.5 is delivered and the arrival of a lightweight, first‑party command‑line text editor called Edit. These moves are being staged through phased enablement and server-side gating, so visibility will vary across devices; at the same time, several important fixes and new known issues were published alongside the flight, making this build a mix of promising UX progress and real-world caution points for IT teams and power users.

---

Background / Overview​

Canary Channel builds are Windows’ experimental sandbox — the place Microsoft tests bold ideas and early prototypes that may evolve dramatically before (and if) they ship to wider audiences. Build 27965 follows that pattern: it delivers a single-scroll Start surface, new app-browsing modes, native Phone Link integration inside Start, and platform-level packaging changes for legacy components. Because many of these changes are deployed via enablement flags and server-side toggles, some users may see the new Start while others on the same Windows version will not. That rollout model reduces the need for heavy OS reinstallation but increases variance in what any individual machine receives.
This release mixes usability wins with compatibility considerations. While everyday users will immediately notice improved app discovery and tighter controls over recommended content, IT administrators and developers must pay attention to the delivery change for .NET Framework 3.5 — a packaging decision with implications for imaging, offline installs, and legacy LOB applications.

---

The new Start: what changed and why it matters​

A single, scrollable Start surface​

The most visible change in Build 27965 is the consolidation of the Pinned, Recommended, and All apps areas into one continuous, vertically scrollable canvas. The old multi‑pane flow — where you had to switch to an “All apps” page — has been replaced by a unified layout that reduces extra clicks and cognitive switching. For users with many installed apps this makes finding software faster and more direct. Insiders report an immediate improvement in app discovery and at-a-glance density, particularly on high-resolution displays.

Multiple “All” views: Category, Grid, and List​

Build 27965 introduces three distinct ways to browse installed applications:

• Category view (default) — the OS groups apps into buckets such as Productivity, Games, Communication, Creativity, and Other when at least three apps fit a recognized category. Frequently used apps within a category “bubble up” toward the top.
• Grid view — an alphabetically ordered grid that uses horizontal space to reduce vertical scrolling and favors visual scanning.
• List view — the classic alphabetical list retained for familiarity.

These options aim to satisfy different mental models: category groupings help users who think by task, grid view benefits visual searchers, and list view preserves the old alphabetical lookup. However, categories are system‑generated and cannot currently be manually created, renamed, or reordered — a limitation that may frustrate power users and enterprise admins who need deterministic layouts for managed devices.

Responsive sizing and adaptive sections​

Start now adapts to your display size and scale. On larger monitors you may see up to 8 columns of pinned apps, 6 recommendations, and 4 columns of categories; on smaller screens those numbers are reduced (for example, 6 columns of pinned apps and 3 columns of categories). Sections are responsive: if you have only a few pinned apps the Pinned area compresses to a single row, letting the rest of the UI slide up. The OS also remembers your last-selected All view (List/Grid/Category), so your preferred browsing mode persists across sessions. These responsive rules make better use of modern, high-DPI and multi-monitor setups.

Privacy and recommendation controls​

One of the most practical tweaks is the addition of clear toggles under Settings > Personalization > Start to disable recommendation surfaces:

• Show recently added apps
• Show recommended files in Start
• Show websites from your browsing history
• Show recommendations for tips

Switching these off hides the Recommended area entirely, returning Start to a more app-centric launcher. This direct control answers years of user complaints about the prominence of the Recommended feed.

Phone Link integration inside Start​

Start now contains a collapsible Phone Link button next to Search, opening a compact mobile-panel that surfaces messages, calls, photos, and battery for connected Android and iOS devices. This in-Start integration is designed for lightweight cross-device workflows and quick glances without launching the full Phone Link app. Microsoft is staging availability and indicated broader market availability for most regions, with delayed rollouts for some jurisdictions. As with other new features, server-side gating means not every Insider will see this immediately.

---

Edit: a native, open-source command-line text editor​

A less flashy but strategically meaningful addition is Edit, a new command-line text editor shipped as part of Windows. Users can open it from Terminal by typing:

• edit <filename>

Edit is an open-source project hosted on GitHub and intended to provide a small, reliable editor for quick edits directly within command-line workflows. This improves the built-in tooling for developers, SREs, and power users who frequently edit scripts or config files without leaving the terminal environment. For the curious, Microsoft published the editor’s docs and feature list as part of the announcement (Insider documentation and repo-based docs detail capabilities and usage).

---

.NET Framework 3.5: delivery and compatibility implications​

Packaging change: not a Windows Feature on Demand​

Starting with Build 27965, .NET Framework 3.5 is no longer offered as a Windows Feature on Demand (FoD) optional component. Microsoft is explicitly encouraging migrations to modern .NET versions, while acknowledging that some business-critical apps still require the legacy runtime. For those cases, Microsoft is providing a standalone .NET Framework 3.5 installer that organizations can use. This is a packaging and distribution change — not an immediate deprecation — but it has practical consequences for deployment workflows.

Why this matters operationally​

• Image management and offline deployments: organizations that rely on FoD packages delivered via Windows Update or on-device feature management must adjust their imaging and recovery processes. A FoD item is typically handled differently by DISM, WSUS, and other servicing pipelines; a standalone installer requires separate tracking and distribution in SCCM/Intune or manual deployment.
• Offline/air-gapped environments: previously, FoD components could be provisioned during offline servicing if the package was present in the image servicing repository. With a standalone installer, administrators should ensure the installer is included in offline deployment media or provide an internally hosted distribution point.
• Compatibility testing: groups still running legacy .NET 3.5 apps must validate the standalone installer path and ensure any dependent registry or system behaviors remain consistent after installation. Planner exercises for compatibility testing are strongly recommended.

Recommended steps for IT teams​

• Inventory apps that require .NET Framework 3.5 and categorize them by criticality.
• Acquire the standalone installer and test deployment in a controlled lab (including offline scenarios).
• Validate imaging workflows (Sysprep, DISM, PXE/bootstrap images) and update deployment documentation.
• Prioritize migration paths to supported, modern .NET versions where feasible — for example, .NET 6 or .NET 8 — to reduce long-term maintenance risk.
• Communicate timelines, testing windows, and contingency plans to stakeholders.

If a customer cannot migrate quickly, the standalone installer remains a supported fallback, but plan the modernization effort — legacy runtimes carry security and maintenance risk over time.

---

Fixes included in Build 27965​

Microsoft shipped a handful of fixes intended to polish daily usability:

• Taskbar and System Tray: a reported issue that caused the taskbar not to autohide correctly in the previous flight was addressed.
• Video playback: a bug that caused some videos and games to show unexpected red tint was fixed. Another fix addressed playback issues for protected content in certain Blu‑ray, DVD, and digital TV apps that used Enhanced Video Renderer with HDCP enforcement.

These fixes resolve some of the more visible regressions Insiders encountered and indicate Microsoft’s continued focus on media and shell polish as the Start redesign rolls out.

---

Known issues and stability caveats​

As expected in the Canary Channel, Build 27965 lists multiple known issues you should weigh before installing on production hardware:

• File Explorer: a new crash that can occur when transferring files to a network drive. This can interrupt file movement and jeopardize large transfers.
• Settings: Settings may crash when accessing drive information under Settings > System > Storage; this also affects accessing drive properties from File Explorer.
• Lock and login screens: media controls may not display on the lock screen in this build.
• Power and battery: reports indicate sleep and shutdown may not work correctly for some Insiders after recent Canary builds. This is a critical reliability concern for laptops and managed endpoints.

These are not minor quibbles — a File Explorer crash during network transfers or failures to sleep/shutdown can break workflows and cause potential data inconsistencies. Microsoft is actively investigating, but until fixes land, Canary builds should be confined to test and enthusiast systems.

---

Practical guidance: who should install Build 27965 — and how​

Ideal candidates​

• Enthusiasts and Windows Insiders who want to experience the Start redesign early.
• Developers and command-line users curious about the native Edit editor.
• UX researchers and IT pilots evaluating the new Start behaviors on a small fleet.

Who should avoid it​

• Production machines, especially those used for critical work or remote employees, due to known issues with File Explorer, Settings, and power management.
• Systems that host legacy .NET 3.5 dependent applications unless the team has validated the standalone installer and deployment path.

How to get it​

• Join the Windows Insider Program and opt into the Canary Channel. Because Microsoft is gating some features server-side, not every Canary device will see every element of the build immediately.
• For power users: manual enabling tools (like ViveTool) exist to flip local feature flags, but manual activation bypasses Microsoft’s staged rollout and may not enable server-controlled components. Manual enabling is unsupported and should only be used by those comfortable with troubleshooting and backups.

---

Enterprise & security analysis​

Deployment and imaging impacts​

The removal of .NET Framework 3.5 as a FoD component changes the lifecycle of images and the default assumptions of many enterprise deployment scripts. Administrators should update golden images and capture offline installers for environments that cannot contact Windows Update during provisioning. Additionally, patch management workflows must incorporate the standalone installer and verify its compatibility with WSUS/SCCM deployment flows.

Security considerations​

• Legacy runtimes like .NET Framework 3.5 can increase surface area if they remain in use long-term; migration to supported .NET releases reduces maintenance and vulnerability risk.
• Phone Link integration inside Start increases cross-device convenience but adds another surface for privacy scrutiny — particularly in regulated environments where mobile devices may contain sensitive data. Admins should validate Mobile Device Management (MDM) policies and review Phone Link behavior before enabling widely.

Policy & compliance​

Organizations should review group policy baselines and Intune configurations to ensure that new Start behavior and Phone Link integrations do not conflict with established corporate UI preferences, telemetry settings, or compliance requirements. The presence of server-side feature gating means admins cannot rely on a single configuration change to produce consistent behavior across a mixed fleet; robust testing and communication are essential.

---

Strengths, trade-offs, and risks — an editorial take​

Strengths​

• Improved discoverability: consolidating Pinned and All apps into a single canvas materially reduces friction.
• Meaningful user control: explicit toggles to hide Recommended content are a direct response to user feedback.
• Responsive design: Start’s adaptive columns and remembered view modes respect modern device diversity.
• Native command-line tooling: the addition of Edit fills a practical gap for script-first users.

These changes demonstrate Microsoft’s responsiveness to long-standing Start menu complaints and a pragmatic UI direction that privileges discoverability and control.

Trade-offs and risks​

• Non-editable categories: automatic grouping is helpful for many users but lacks the manual control that power users and admins often require. This reduces determinism for managed fleets.
• Rollout fragmentation: enablement packages and server-side gating improve deployment flexibility but create inconsistent experiences across otherwise similar devices. This complicates support and helpdesk troubleshooting.
• Compatibility and reliability: known crashes and power issues in the Canary build make it unsuitable for production and highlight the risk of early adoption.

Bottom line​

The Start redesign is a solid, user-centric improvement that addresses clear usability deficits in Windows 11’s original launch. The tooling and packaging changes (Edit and .NET Framework 3.5’s delivery shift) are pragmatic moves designed for modern workflows, but they introduce operational work for IT shops. Given the known stability issues in Canary builds, organizations should pilot and validate before broad deployment. fileciteturn0file3turn0file13

---

Quick checklist for pilots and admins​

• Create a small pilot group of diverse hardware (laptop, desktop, high‑DPI).
• Backup images and collect offline installers for .NET Framework 3.5.
• Test Phone Link behaviors and confirm privacy posture for connected mobile devices.
• Validate imaging and deployment scripts against the standalone .NET installer.
• Monitor known issues (File Explorer network transfer crashes, Settings drive-info crashes, power regressions) and hold off on production-wide rollout until fixes land.

---

Conclusion​

Build 27965 brings a genuinely practical Start menu redesign to the Canary Channel that many users and IT pros will find welcome: a single, scrollable Start surface, new browsing modes, better controls over recommendations, and integrated Phone Link are all meaningful UX wins. The inclusion of the open-source Edit editor modernizes command-line workflows, and the change in .NET Framework 3.5 packaging signals Microsoft’s continued push toward modernization — while acknowledging the reality of legacy dependencies.
However, the Canary nature of this flight, combined with notable known issues and a packaging change for a widely used legacy runtime, means this build is best suited for enthusiasts, pilots, and labs. Enterprises should treat the .NET packaging change as an operational event that requires action — inventory, test, and deploy the standalone installer where needed — and should not deploy Canary builds on production endpoints until the flagged reliability issues are resolved. fileciteturn0file13turn0file0
The redesign is not merely cosmetic; it reflects a deliberate, incremental shift toward an app-first, adaptive Start experience that respects user choice. Over the next servicing updates, expect stability improvements and additional customization options — and for IT teams, expect a small but real surge of work to keep legacy applications running smoothly as Windows’ delivery model evolves. fileciteturn0file3turn0file10

---

Source: Neowin Microsoft releases the redesigned Start menu to Windows 11 Canary Insiders with build 27965