Windows 11 24H2: WordPad and Mixed Reality Removed; New Checkpoints, Sudo, Sandbox

Microsoft’s Windows 11 24H2 test build quietly removes two long-running pieces of Windows heritage — WordPad and Windows Mixed Reality — while shipping a set of newer, developer‑ and servicing‑focused features that point to where Microsoft wants Windows to go next. The change is consequential: WordPad’s removal severs a nearly 30‑year lineage of a lightweight rich‑text editor bundled with Windows, and the Mixed Reality exit formally pulls the plug on a consumer VR/AR foothold Microsoft once hoped would grow into a platform. These retirements arrive alongside pragmatic improvements for enterprise update management, developer ergonomics, and sandboxing — and they reveal a deliberate strategy to trim legacy consumer baggage while accelerating cloud, Store and modern servicing scenarios.

---

Background / Overview​

WordPad debuted with Windows 95 as a middle ground between Notepad and Microsoft Word: free, simple, but capable of basic rich text formatting and opening .rtf files. In 2023 Microsoft signaled WordPad’s future by marking it deprecated; with Windows 11 version 24H2 that step becomes final — WordPad and related binaries are removed from the OS image. Microsoft now recommends using Microsoft Word for rich formats and Notepad for plain text, and warns developers not to take direct dependencies on the WordPad binaries.
Windows Mixed Reality (WMR), introduced in 2017 as Microsoft’s consumer VR/AR runtime and portal, has also been deprecated and removed from 24H2. The deprecation affects the Mixed Reality Portal, Windows Mixed Reality for SteamVR and related tooling; existing WMR headsets continue to work only on older Windows releases and will be supported in limited ways until the vendor‑specified sunset dates. (learn.microsoft.com, theverge.com)
At the same time, 24H2 brings several forward‑looking features:

• Checkpoint cumulative updates to shrink update downloads for devices already at recent checkpoints. (techcommunity.microsoft.com, learn.microsoft.com)
• Sudo for Windows, a new elevated command flow familiar to UNIX users but designed for Windows UAC/consent flows; it’s present but disabled by default and requires enabling in Settings. (learn.microsoft.com, devblogs.microsoft.com)
• Windows Sandbox delivered as an updated Store client with improved runtime controls and runtime sharing options. (learn.microsoft.com, blogs.windows.com)

Taken together, these moves show Microsoft trading some legacy consumer features for modern manageability, developer convenience, and a tighter integration with Microsoft Store and cloud services. The rest of this feature examines the removals, explains the technical mechanics and mitigations, assesses impacts, and gives practical recommendations for end users and IT pros.

---

The end of WordPad: what changed and why it matters​

What Microsoft removed​

Microsoft’s compatibility and “removed features” documentation is explicit: WordPad is removed from all editions of Windows starting with Windows 11, version 24H2. That removal includes binaries such as wordpad.exe, wordpadfilter.dll and write.exe; the operating system will no longer provide a built‑in default RTF reader. Microsoft directs users who need richer editing to Microsoft Word and suggests Notepad for plain text.

Why Microsoft made the call​

The reasons are pragmatic and strategic:

• Low usage and overlap. Notepad has become more capable over recent releases and cloud‑based editors and Office/365 have tightened document workflows. WordPad’s role as a no‑cost, middle‑ground editor is now duplicated by numerous free alternatives and online apps.
• Platform consolidation. Microsoft is streamlining the core Windows image and encouraging use of the Store and cloud apps (Office.com, Microsoft 365) for functionality beyond minimalist editing. This reduces maintenance surface area for seldom‑used components.
• Security and servicing. Fewer legacy binaries shipped by default means one less component to track for vulnerabilities and update compatibility, particularly across Windows servicing models.

Who this affects​

• Casual users who relied on WordPad for quick formatted notes (RTF) will need to pivot to alternatives.
• Organizations that automated workflows around WordPad or used it as a default RTF viewer might find that scripts or local processes expecting wordpad.exe now fail.
• Software that integrated WordPad as an embedded viewer or relied on WordPad filters may require code changes.

Risks and frictions​

• RTF compatibility edge cases. Some vendors historically produced vendor‑specific RTF‑like files that WordPad tolerated but modern word processors may not. Losing WordPad can expose those edge cases. Community reports indicate some real‑world files fail to open cleanly in other apps without conversion.
• Migration burden. Education, small businesses and public kiosks that used WordPad’s simple, offline, free interface now must standardize on alternatives — raising training, licensing or imaging questions.
• Potential security complacency. Users who try to “resurrect” old WordPad binaries from an older image bypassing official support risk running unpatched, unsupported code.

Practical mitigation paths​

• If you require full RTF fidelity and offline editing, use:
• LibreOffice Writer or OnlyOffice (free, local installations).
• Microsoft Word (desktop or Office.com) for full fidelity — note licensing implications for offline use.
• For simple formatted notes, Notepad with Markdown/light formatting, or lightweight editors such as Jarte, can substitute.
• IT teams should audit automation and installer logic for references to wordpad.exe, wordpadfilter.dll or write.exe and migrate to supported APIs or tooling. Microsoft explicitly advises developers to stop depending on those binaries.

---

Mixed Reality’s sunset: the consumer VR story closes (for now)​

What’s being removed​

Windows Mixed Reality and the Mixed Reality Portal are deprecated and removed from 24H2. The deprecation includes the WMR SteamVR bridge and related beta components; devices that rely on the WMR runtime will stop functioning on systems that upgrade to 24H2 unless users maintain older OS versions. Microsoft’s timeline allows limited continued usage on older Windows releases with shrinking support windows.

Why Microsoft is stepping back​

• Market realities. WMR failed to build a critical mass against competitors and ecosystem partners. Meta/Oculus, Valve, and other vendors captured VR market share, and Microsoft’s focus shifted toward enterprise holographic scenarios (HoloLens, Mesh).
• Business focus. Microsoft’s investments now prioritize cloud, AI, and enterprise AR/VR where the commercial returns and strategic alignment (e.g., HoloLens and Mesh) are clearer.
• Maintenance and compatibility. Maintaining a consumer runtime across OS versions, Steam integrations and hardware variants is increasingly expensive relative to the user base size.

Practical implications for owners of WMR headsets​

• If you rely on a WMR headset (HP Reverb G2, Samsung Odyssey, Lenovo Explorer, etc.), upgrading to Windows 11 24H2 will break the runtime support for those devices. Users are advised to:
• Stay on Windows 11 version 23H2 (or Windows 10) for as long as vendor support permits.
• Avoid upgrading to 24H2 until a robust third‑party runtime alternative appears or you migrate to newer hardware. Community reports and vendor forums document device incompatibility on 24H2. (neowin.net, answers.microsoft.com)
• SteamVR integration that depended on WMR will be affected; SteamVR may still run but dependent runtimes and drivers will be missing.

Bigger picture​

Microsoft continues to invest in cloud‑driven mixed presence (Microsoft Mesh, enterprise HoloLens scenarios) but the consumer headset and WMR runtime are no longer strategic priorities. That’s a practical — if disappointing — business decision for consumer VR users.

---

New and notable additions: what’s actually improving​

Checkpoint cumulative updates: smarter servicing​

Windows 11 24H2 introduces checkpoint cumulative updates, a new servicing concept where some cumulative updates are designated as checkpoints against which future binary differentials are computed. That reduces the size of subsequent update downloads for devices already at the latest checkpoint and reduces distribution costs for IT administrators. The mechanism preserves standard update flows for WU and WSUS but changes how Microsoft packages and ships cumulative update payloads for efficiency. This is a meaningful win for large environments with bandwidth and storage constraints. (techcommunity.microsoft.com, learn.microsoft.com)
Key benefits:

• Smaller downloads for devices already on a recent checkpoint.
• Better caching and redistribution efficiencies for enterprise update catalog distributions.
• Potentially faster installs for long‑unupdated devices.

Practical note: Image customization scenarios that require language packs or Features on Demand (FoD) may still need full payloads; IT pros should read the catalog guidance before changing distribution workflows.

Sudo for Windows: a developer convenience​

Windows 11 24H2 ships with a new sudo command concept aimed at improving the console‑to‑elevation workflow. The feature is off by default; admins and devs enable it under Settings > System > For Developers. Sudo allows elevating a command from an unelevated shell and supports three configurations — new window, input closed, and inline — with documented security caveats for the latter two configurations. Microsoft open‑sourced the implementation and provides guidance on safe configuration. (learn.microsoft.com, devblogs.microsoft.com)
Why it matters:

• Familiarity: UNIX/Linux users get a familiar "sudo"-style ergonomics.
• Convenience: Scripts and interactive usage avoid reopening admin terminals.
• Security tradeoffs: Inline and input‑enabled modes expose greater attack surface and must be enabled consciously.

Windows Sandbox modernization​

Windows Sandbox is now a Store‑updateable app with WinUI 3 UI, runtime controls (clipboard redirection, audio/video input toggles, folder sharing) and initial command line support. That shift enables quicker fixes and feature updates outside of full OS servicing. Admins and security teams get a more flexible, quicker‑patchable sandboxing tool for untrusted application testing and containment. Community reports early in 24H2 identified some teething issues (some crashes, initialization errors) — typical for a newly modularized component — but Microsoft maintains an update cadence through the Store. (learn.microsoft.com, blogs.windows.com)

---

Usability, privacy and policy implications​

Start menu: recommended Store apps and opt‑out​

24H2 expands the Recommended area of Start to include curated Microsoft Store app recommendations — effectively a promotional slot. Microsoft provides a clear opt‑out via Settings > Personalization > Start (“Show recommendations for tips, app promotions, and more”). That option is present because Microsoft initially rolled this capability as an opt‑in/insider experiment and then pushed it more broadly, provoking user backlash in prior updates. The presence of an explicit toggle is important, but some users will view any promoted content in a system UX as an intrusion. (windowscentral.com, windowslatest.com)

Notification improvements​

Windows 11 24H2 continues to refine notification control: per‑app notification toggles are available from Settings > System > Notifications, and system controls now include options to disable certain suggestion prompts. The platform still presents several global and per‑app settings; IT teams can script or configure notification behavior via policy for managed devices. (support.microsoft.com, superuser.com)

---

Critical analysis: strengths, tradeoffs and risks​

Strengths​

• Servicing advances are practical and welcome. Checkpoint cumulative updates address a real pain point for enterprise environments and long‑lived images. Smaller differentials save bandwidth and reduce install friction. (techcommunity.microsoft.com, learn.microsoft.com)
• Developer ergonomics improved. Sudo for Windows is a thoughtful improvement that reduces friction for command‑line workflows while keeping UAC in the loop. The open‑sourcing approach gives transparency and community review. (learn.microsoft.com, github.com)
• Sandbox modernized and decoupled. Delivering Windows Sandbox as a Store app accelerates fixes and features independent of the OS release cadence. For security testers and IT teams, this is a net win.

Tradeoffs and risks​

• User experience vs. monetization tension. The Recommended/Store ad placement in Start, while optional, increases user resentment and feeds narratives about Windows pushing promotions into system surfaces. The opt‑out toggle mitigates but does not eliminate the UX precedent.
• Legacy support gap. Removing WordPad and WMR shifts the burden to users and organizations to adopt alternatives, which could increase operational friction in specialized scenarios (legacy RTF file formats, device‑dependent VR setups). Community reports show real compatibility pain points for edge files and hardware. (reddit.com, neowin.net)
• Security considerations around new conveniences. Sudo for Windows increases convenience but also introduces privilege‑escalation surface area; Microsoft’s docs call out specific security tradeoffs and recommend conservative default configurations. Administrators must treat sudo’s configuration as a security decision, not merely a usability setting.

What Microsoft should watch​

• Monitor post‑rollout telemetry for Word/RFT compatibility failures and provide guidance or conversion tools if certain industry file variants are failing in the wild.
• Continue to harden Sandbox and ensure Store‑side updates respect enterprise blocking controls (some organizations lock down Store updates).
• Keep a clear roadmap for WMR owners: prolonged uncertainty breeds fragmentation and user frustration; transparent timelines and fallback guidance are essential.

---

Practical checklist: what to do now​

• For home users who simply want a WordPad replacement:
• Evaluate LibreOffice Writer, OnlyOffice, or Office.com for RTF and DOCX compatibility.
• Use Notepad for plain text and lightweight needs; explore Notepad++ for power editing.
• For IT administrators:
• Audit automation and scripts for direct invocations of wordpad.exe, write.exe, or wordpadfilter.dll and plan replacements.
• Review update distribution plans and assess whether checkpoint cumulative updates improve your bandwidth and caching strategy; update WSUS/Update Catalog procedures accordingly.
• If you manage mixed‑reality hardware, inventory WMR devices, and delay upgrades for affected endpoints until hardware strategy is settled.
• For developers and power users:
• Test Sudo for Windows in controlled environments, enable it only when necessary, and prefer default (forceNewWindow) mode unless you understand the security tradeoffs.
• Try the new Windows Sandbox Store client for secure testing and evaluate runtime sharing features for your app validation workflows.

---

Final assessment and closing thoughts​

Windows 11 version 24H2 is not a single‑issue update; it’s a deliberate rebalancing of the OS image toward manageability, modularity and modern workflows. Removing WordPad and Mixed Reality signals Microsoft’s willingness to retire long‑standing consumer features that no longer align with platform priorities, even at the cost of legacy user goodwill. At the same time, the addition of checkpoint cumulative updates, Sudo for Windows, and a Store‑updated Windows Sandbox are tangible improvements for enterprises, developers and security pros.
For most users, WordPad’s departure will be a minor inconvenience — easily addressed by free alternatives or the Office web client. For WMR enthusiasts, however, the end of the runtime is a material disruption that forces hardware migration or extended use of legacy OS images. Organizations should audit dependencies and prepare migration plans now.
Microsoft’s choices in 24H2 reflect a clear tradeoff: prune and modernize the OS core while providing stronger tools for servicing and development. That’s a defensible, long‑term direction. The practical impact will be felt in migration work and in a small number of hardware and file‑format edge cases — and how Microsoft supports those transitions will define whether this update is remembered as effective upkeep or as a painful pruning.
The release is a reminder that platform stewardship requires both additions and removals: the gain in update efficiency, developer ergonomics and sandboxing is real; the cost in legacy compatibility and user nostalgia is equally real. Teams that plan for the changes now — auditing scripts, vetting alternate RTF workflows, and inventorying mixed reality hardware — will have the smoothest path forward. (learn.microsoft.com, techcommunity.microsoft.com)

---

Source: Mashdigi Microsoft officially removed the WordPad text processing editor and Mixed Reality features from the Windows 11 24H2 test version released earlier.