Windows 11 version 24H2 arrives not as a gentle refresh but as a deliberate rebalancing act, jettisoning two long‑running pieces of Windows heritage—WordPad and Windows Mixed Reality—while injecting enterprise‑grade servicing, developer convenience, and a decoupled sandbox directly into the OS core. The changes, confirmed in Microsoft’s official documentation and now rolling out to users, mark the final retirement of the lightweight rich‑text editor that first shipped with Windows 95 and formally pull the plug on a consumer VR runtime Microsoft once hoped would rival the competition.

WordPad’s binary deletion and Mixed Reality’s runtime expiration head a list of over a dozen feature removals in 24H2, but they are countered by the introduction of checkpoint cumulative updates, Sudo for Windows, and a Store‑updatable Windows Sandbox. The tradeoff is stark: Microsoft is pruning legacy consumer baggage to sharpen enterprise manageability and developer workflows.

WordPad Removal: a 30-year staple gets the axe

Starting in Windows 11 24H2, WordPad and its associated binaries—wordpad.exe, wordpadfilter.dll, and write.exe—are stripped from every edition of the operating system. The removal, first signaled as deprecated in 2023, is now final; the binaries will not appear on new installations or upgrades. Microsoft’s official recommendation is to use Microsoft Word for rich‑text documents (.doc, .rtf) and Notepad for plain text.

The demise of WordPad closes a chapter that began with Windows 95. For three decades, the editor served as a free, no‑fuss middle ground between Notepad’s simplicity and Word’s complexity, capable of basic formatting and .rtf handling. Its removal leaves a gap for users who relied on that functionality without the overhead of a full Office suite.

Why Microsoft pulled the plug

Microsoft’s decision rests on three pillars:
- Low usage and functional overlap. Notepad has gained features like autosave and tab support, while free alternatives and web apps cover the middle ground WordPad occupied.
- Platform consolidation. Shipping fewer legacy components reduces the OS footprint and pushes users toward Store apps and cloud services, such as Office.com.
- Security and servicing burden. Each built‑in binary is a potential attack surface and a component that must be tested against cumulative updates. Removing WordPad simplifies the servicing matrix.

Real‑world impact

Casual users who drafted quick formatted letters or opened recipe .rtf files in WordPad will need to find replacements. For organizations, the bigger risk lies in automation: any script, installer, or legacy application that calls wordpad.exe or relies on WordPad’s filter library will break. Community reports highlight edge cases, such as niche .rtf variants generated by older applications that WordPad tolerated but modern word processors may not, raising compatibility headaches for regulated industries where those files remain in use.

What to use instead

  • LibreOffice Writer or OnlyOffice offer free, offline .rtf and .docx editing.
  • Microsoft Word (desktop or web) provides full fidelity but may carry licensing costs.
  • Notepad is recommended for plain text, and Notepad++ adds power‑editing features.
  • IT admins should audit for hardcoded references to WordPad binaries and replace them with supported APIs or alternate applications.

Windows Mixed Reality: the consumer VR dream fades

Windows 11 24H2 also removes the Windows Mixed Reality (WMR) runtime, including the Mixed Reality Portal, WMR for SteamVR, and related components. The deprecation was announced in December 2023, but 24H2 makes it operative: any system that upgrades will lose the ability to run WMR headsets. Existing devices continue to work only if users remain on Windows 11 23H2 or an earlier release, with Microsoft confirming that security updates for the relic runtime end after November 2026.

A business decision, not a technological one

WMR launched in 2017 as Microsoft’s attempt to carve a consumer VR niche, leveraging an open hardware ecosystem with partners like HP, Samsung, and Lenovo. It never achieved critical mass. Meta’s Quest line and Valve’s SteamVR ecosystem captured mainstream and enthusiast segments, while Microsoft’s corporate focus shifted to enterprise mixed reality (HoloLens, Mesh). Maintaining a consumer runtime across OS upgrades and hardware variants became financially unsustainable.

What headset owners must do

Owners of HP Reverb G2, Samsung Odyssey, Lenovo Explorer, or similar WMR‑dependent headsets face a hard choice: block the 24H2 upgrade for as long as usable, or retire the hardware. Community forums are already flooded with reports of headsets failing on 24H2 builds. SteamVR itself continues to function, but the bridge between SteamVR and the headset drivers evaporates once WMR is removed. For those needing full VR support, the only path forward is to migrate to headsets with native SteamVR support or standalone ecosystems like Quest.

New forward‑looking features strengthen enterprise and developer tooling

While the removals grab headlines, 24H2 introduces several features that underscore Microsoft’s servicing and developer strategy.

Checkpoint cumulative updates: smaller downloads, smarter distribution

The new checkpoint update model designates certain cumulative updates as “checkpoints.” Subsequent updates are built as differentials against these checkpoints, dramatically reducing download sizes for devices that are already near the latest baseline. For IT administrators managing fleets, this translates to less bandwidth consumption and faster update distribution through WSUS or Microsoft Update Catalog. Organizations that deploy language packs or Features on Demand should review the new catalog‑dependent procedures to avoid inadvertently pulling full payloads.

Sudo for Windows: a familiar elevation command

Sudo for Windows brings a Unix‑style elevation workflow to the Windows command line. Not enabled by default, it can be turned on in Settings > System > For Developers. Three modes are available: “New Window” (safest), “Input Closed,” and “Inline.” While convenient for developers and cross‑platform scripters, the inline and input‑enabled modes open additional privilege‑escalation surfaces. Microsoft open‑sourced the implementation and cautions that administrators must treat the configuration as a security boundary, not a mere preference.

Windows Sandbox goes Store‑updatable

Previously baked into the OS image, Windows Sandbox is now delivered as an app through the Microsoft Store, complete with a WinUI 3 interface and runtime controls for clipboard sharing, folder mapping, and audio/video input. Decoupling it from Windows servicing means security fixes and feature improvements can ship faster. Early 24H2 builds saw some initialization hiccups, but Microsoft’s Store‑driven update cadence enables rapid patching. For security testers and IT staff, the new Sandbox is a more flexible tool for isolating untrusted applications.

Usability tweaks and the ongoing ad‑vs‑UX tension

24H2 expands the Recommended section of the Start menu to include curated Microsoft Store app suggestions. While clearly labeled as promotions, the change reignites the debate over system‑level advertising. Microsoft includes an explicit toggle: Settings > Personalization > Start > “Show recommendations for tips, app promotions, and more.” Users and IT teams can disable it immediately, but the precedent of embedding such content in core UI surfaces remains contentious.

Notification controls also see refinement, with per‑app toggles and options to suppress suggestion‑style prompts. For managed devices, group policies and MDM settings can enforce a consistent notification posture.

Critical analysis: what Microsoft gets right and where risk remains

Strengths

  • Checkpoint updates solve a real‑world distribution pain point for enterprises and large‑image scenarios.
  • Sudo for Windows modernizes the elevation workflow without bypassing User Account Control.
  • Store‑delivered Sandbox accelerates innovation and patching outside the semiannual release cadence.
  • Removing legacy components shrinks the attack surface and simplifies servicing.

Tradeoffs and risks

  • Legacy compatibility gaps. WordPad’s removal may break .rtf workflows that rely on its unique parsing quirks.
  • Hardware obsolescence. WMR headset owners are forced into costly hardware migrations or locked onto aging OS versions.
  • Security considerations with Sudo. Inline mode can be abused if not carefully restricted; administrators must treat it as a privilege‑boundary change.
  • Start menu promotions undermine user trust even with an opt‑out toggle.

What Microsoft should do next

  • Monitor telemetry for Word/RFT file failures and consider a standalone converter tool if widespread issues surface.
  • Provide a clear, time‑bound migration path for WMR users, possibly partnering with third‑party runtime maintainers.
  • Ensure enterprise controls over Store updates don’t block critical Sandbox patches in locked‑down environments.
  • Keep the Start menu promotion toggle visible and respect it during feature updates—ad creep in the OS is a persistent user sore point.

Practical checklist: preparing for 24H2

For home users

  • Switch to LibreOffice Writer, OnlyOffice, or Word for rich‑text needs.
  • Use Notepad++ or standard Notepad for plain text.
  • If you own a WMR headset, defer the 24H2 upgrade or begin planning a hardware replacement.

For IT administrators

  • Audit scripts and GPOs for hard references to wordpad.exe, write.exe, or wordpadfilter.dll.
  • Evaluate checkpoint cumulative update workflows: adjust WSUS/Update Catalog procedures to leverage differentials.
  • Inventory all WMR‑capable endpoints and block 24H2 upgrades on those devices until a hardware strategy is finalized.
  • Test the new Sandbox client and verify that Store‑based updates comply with your enterprise update policies.

For developers

  • Enable Sudo for Windows only when needed and prefer the “New Window” mode unless you have thoroughly reviewed the security implications.
  • Use the Store‑updated Sandbox for application testing and take advantage of its new runtime sharing options.
  • Update any tooling that relies on deprecated binaries or WordPad filters.

Final assessment: a necessary, if painful, evolution

Windows 11 24H2 is not a flashy feature update; it’s a discipline update. Microsoft is actively curating the OS image—removing components that no longer align with its cloud‑first, enterprise‑centric direction while simultaneously building out the servicing and developer toolkits that modern IT demands. The disappearance of WordPad will irk nostalgic users and small businesses that appreciated a free, offline rich‑text editor, but a robust ecosystem of alternatives exists. The end of Windows Mixed Reality stings more: it leaves loyal headset owners stranded and underscores the fickle nature of consumer hardware platforms.

The addition of checkpoint updates, Sudo for Windows, and a decoupled Sandbox shows that Microsoft is reinvesting those maintenance savings into tangible, forward‑looking improvements. For organizations that plan ahead—auditing scripts, vetting replacement editors, and locking down hardware upgrade paths—the transition will be manageable. For everyone else, the 24H2 update is a sharp reminder that platform stewardship demands both pruning and planting. How well Microsoft supports the fallout will determine whether this release is remembered as efficient modernization or unnecessary disruption.