WordPad Retired in Windows 11 24H2: What It Means for Lightweight Editing

Microsoft quietly pulled the plug on WordPad — the lightweight rich‑text editor that's been bundled with Windows since the Windows 95 era — when Windows 11 version 24H2 rolled out, moving the app to Microsoft’s official Deprecated Features list and removing its binaries from fresh OS images. This change leaves Windows without a built‑in, default RTF viewer and forces a rethink for users and administrators who relied on WordPad as the in‑between tool that sat between Notepad and the full Microsoft Word experience.

Background​

A 30‑year utility, quietly retired​

WordPad debuted with the consumer boom that followed Windows 95 and stayed largely unchanged in role if not in every UI detail. It offered simple formatting (fonts, bold/italic, lists, alignment) and supported Rich Text Format (.rtf) and, in later years, some subset handling of .docx and .odt files. For decades it filled a useful niche: more capable than plain text Notepad but far lighter — and free — compared with Microsoft Word.

How WordPad fit into Windows’ app hierarchy​

• Notepad — a minimal plain‑text editor for logs, scripts, and quick notes.
• WordPad — a basic WYSIWYG editor with rich text support for formatted notes and simple documents.
• Microsoft Word — a full‑featured commercial word processor for heavy‑duty document production.

That middle ground is where many casual users, IT techs, educators, and help‑desk staff found quick value: WordPad could open and strip problematic formatting from damaged documents, and its minimalism meant it usually launched fast and reliably. But over the last several Windows releases, Microsoft has invested heavily in improving Notepad and in pushing cloud‑based and Store‑delivered editing tools, narrowing the space WordPad occupied.

---

What Microsoft announced (and what it actually removed)​

Official deprecation and removal timeline​

Microsoft’s documentation now lists WordPad as no longer being updated and slated for removal, specifying that WordPad will be removed from all editions of Windows starting with Windows 11, version 24H2 and Windows Server 2025. The guidance explicitly recommends Microsoft Word for rich text formats such as .doc and .rtf, and Windows Notepad for plain text (.txt). The deprecation/removed‑features pages also advise developers to avoid depending on WordPad binaries if their applications rely on them.

The precise binaries affected​

Microsoft’s resources list the binaries that are being removed:

• wordpad.exe
• wordpadfilter.dll
• write.exe

Removing these means a stock Windows 11 24H2 image no longer ships with a built‑in RTF viewer/editor. Third‑party applications or scripts that explicitly invoked these executables will need to be updated.

---

Why Microsoft’s public explanation is thin — and what that implies​

Microsoft’s official line​

Microsoft’s public documentation states only that WordPad is deprecated and will be removed, and recommends alternatives (Word, Notepad). There’s no extended rationale in the official notices explaining strategic or technical drivers for the change beyond the standard deprecated features language and migration guidance for developers.

What Microsoft didn’t say (and why that matters)​

Microsoft did not offer a public post explaining whether the removal was motivated predominantly by:

• security (reducing attack surface),
• maintenance burden (legacy code that requires testing and security patching),
• product consolidation (driving people to actively developed editors or Microsoft 365 services),
• OS image size and complexity (trimming seldom‑used components),
  or some combination of the above.

Because the company did not publish a blow‑by‑blow rationale, outside observers must rely on patch notes, the broader trend of removing legacy components from Windows, and public security history around RTF parsing to infer likely drivers. Those inferences are reasonable but not formally confirmed by Microsoft and should be treated as such.

---

Plausible reasons behind the decision — evidence and limits​

1) Overlap and shrinking usage footprint​

Notepad has received substantial upgrades in recent Windows releases (tabs, spellcheck, on‑device AI text features, limited formatting and Markdown preview in Dev/Canary builds), narrowing WordPad’s unique value proposition. Many users now opt for cloud editors (Google Docs, Office for the web), free suites (LibreOffice), or lightweight third‑party apps — reducing WordPad’s active user base and making continued investment less defensible. This trend is documented across industry coverage and product update notes.

2) Maintenance and engineering cost​

Every in‑box app increases the Windows maintenance surface area: compatibility, testing across devices and languages, security patching, and localization. Microsoft’s decision to remove older or low‑use components in the past has often been framed as streamlining the OS image and reducing engineering debt. Microsoft’s deprecation pages instruct developers not to rely on WordPad binaries — a signal that the company intends to remove long‑term maintenance obligations. While Microsoft did not publish explicit cost figures, the removal is consistent with an engineering posture that favors consolidating effort on actively developed apps.

3) Security and attack surface reduction (plausible, but not confirmed)​

WordPad, and the Rich Text Format (RTF) parsing engine and converters it depends on, have a documented history of security vulnerabilities that could be exploited via crafted RTF or OLE content. Notable examples include CVE‑2017‑0199 and earlier RTF/WordPad-related buffer‑overflow and parsing bugs that Microsoft patched over the years. Removing a legacy in‑box application that parses potentially hostile document formats plausibly reduces the default attack surface for an unpatched or misconfigured machine. However, Microsoft has not publicly stated that security was the deciding factor, so although the security explanation is credible, it remains speculative rather than confirmed.

---

The practical fallout: what users and admins will notice​

For everyday users​

• Windows 11 24H2 fresh installs will not include WordPad by default. Users who upgrade from older versions may find the app removed from Start and Accessories as part of the update process. Microsoft suggests using Word (desktop or web) for formatted documents and Notepad for plain text. For many casual users the change will be frictionless; others who used WordPad as a quick local RTF editor will need to adopt an alternative.

For IT administrators and developers​

• Any scripts, automation, or line‑of‑business tools that called wordpad.exe, write.exe, or relied on the WordPad filter will break on new images. Microsoft explicitly warns developers to avoid taking a direct dependency on these binaries. Administrators must audit system images, update references, and provide replacements in managed images.

For power users and recovery workflows​

• WordPad has long been a pragmatic recovery tool — for example, it sometimes could open documents that Word marked as corrupt (stripping unsupported formatting) and thus acted as a crude but useful rescue method. With WordPad removed, those recovery workflows will need replacements: either a third‑party RTF viewer, LibreOffice, or scripted utilities that can extract text. Analysts warned that this particular convenience would be missed by some support teams.

---

Alternatives and migration strategies​

Official Microsoft paths​

• Microsoft Word (desktop / Microsoft 365 / Word for the web): the supported rich‑text/document editing solution recommended by Microsoft. Best for heavy editing, enterprise compatibility, and security updates.
• Windows Notepad: increasingly capable for plain‑text tasks, and Microsoft has been enhancing it with tabs, formatting features, and AI assistance on some channels. Notepad is not a drop‑in RTF editor, but for many short notes it suffices.

Local third‑party replacements (free and paid)​

• LibreOffice (Writer) — full office suite capable of reading and writing .rtf, .doc, .docx and a robust local alternative for offline users.
• Jarte — a lightweight word processor that explicitly uses the same Windows RTF editing engine WordPad historically leveraged; it offers a richer UI and is pitched as a WordPad replacement for users who liked the small footprint and fast startup.
• Other lightweight apps — Atlantis, AbiWord, OnlyOffice, and numerous portable RTF editors provide fast local editing without Microsoft 365 subscriptions. BGR and other outlets have recently curated lists of alternatives.

How to restore WordPad (workarounds and caveats)​

A number of community guides documented that copying the WordPad binaries from a pre‑24H2 machine into a non‑system folder on a 24H2 machine will allow the executable to run. The typical approach documented by several outlets:

• On a machine with Windows 11 23H2 or earlier, copy the Accessories folder from:
• C:\Program Files\Windows NT\Accessories
  (this contains wordpad.exe and the language MUI files).
• Move that folder to a safe location on the 24H2 machine (for example, %UserProfile%\Documents\WordPad).
• Launch wordpad.exe directly or create a shortcut/pin to taskbar.

This method works because the WordPad executable is largely self‑contained, but it’s an unsupported workaround: Microsoft won’t provide updates or security patches for a reinstated copy, and future cumulative updates could break the approach. Administrators should weigh operational risk and supportability before adopting this as a long‑term solution.

---

Security implications — deeper analysis​

Historical RTF and WordPad weaknesses​

RTF, OLE, and auxiliary file converters that have been part of Windows’ document stack have a decades‑long history of vulnerabilities. Several CVEs and advisories explicitly referenced WordPad or the RichEdit/MSFTEDIT components, and Microsoft historically recommended caution with untrusted RTF documents. Removing the in‑box WordPad app reduces the set of default attack surfaces on a clean install — but it does not remove the underlying document parsing libraries if they’re still present for other Windows components or apps. The security benefit therefore depends on which components are actually removed from the image and how other apps continue to handle RTF/embedded objects.

Not a silver bullet​

• If third‑party apps still include or call the same RTF parsing libraries, attackers still have targets.
• Users who reinstall WordPad from older binaries reintroduce the same parsing code onto their machines.
• Effective security requires patching, secure configuration, and cautious handling of documents from untrusted sources — not merely removal of one UI wrapper app.

Therefore, while removing WordPad from stock images likely reduces risk for some use cases, it is not a complete mitigation for RTF‑related threats.

---

Strengths and risks of Microsoft’s move — balanced critique​

Strengths (why this could be a net positive)​

• Reduced maintenance burden: fewer in‑box components mean Microsoft can concentrate engineering and testing resources on actively developed apps.
• Smaller attack surface for default installs: fewer default apps parsing complex document formats is a defensible security posture on paper.
• Encourages modernization: nudging users toward actively maintained editors (Notepad updates, Word for the web, Microsoft 365) can improve long‑term compatibility and feature delivery.

Risks and downsides​

• Loss of a simple, local middle‑ground editor: not everyone wants or can use cloud editors or pay for Microsoft 365. Offline users, low‑bandwidth environments, and some educational or kiosk setups lose a convenient option.
• Operational disruption: scripts and legacy workflows that called WordPad binaries will break unless proactively audited and updated. Enterprise imaging teams and ISVs must adapt.
• User outrage and friction: Microsoft previously saw pushback when it moved Paint to the deprecated list and then reintroduced it following community reaction. WordPad’s removal will likely generate similar complaints from power users and certain business users who depended on its convenience.

---

Clear guidance for IT teams and users​

For IT admins​

• Audit images and scripts now — search for invocations of wordpad.exe, write.exe, and wordpadfilter.dll in images, Group Policy logon scripts, or installer packages.
• Plan migration — decide whether to standardize on Microsoft Word (Office/Microsoft 365), LibreOffice, Jarte or another lightweight editor for managed endpoints.
• Communicate to users — identify power users who rely on WordPad for specific workflows (e.g., corrupt‑doc triage) and provide tested alternatives ahead of upgrades.
• If necessary, maintain a vetted copy — for closed environments where WordPad is essential, maintain a secured, offline copy of the WordPad binaries and document the security implications and lack of vendor support. Treat this as an interim measure only.

For everyday users​

• Try Notepad’s newer features for simple text work; use LibreOffice or Word for the web for richer editing without a local Word install. If you absolutely must keep WordPad’s behavior, create a backup of the Accessories folder on your older Windows machine before upgrading to 24H2. Remember that running a retired binary is unsupported and may carry security risk.

---

Final assessment​

Microsoft’s removal of WordPad from Windows 11 24H2 is consistent with a broader strategy of trimming low‑usage legacy components and steering users toward actively maintained, cloud‑capable tools. The company’s official messaging is deliberately terse: WordPad is deprecated, it won’t be updated, and developers should avoid depending on its binaries. That clarity helps administrators and developers make practical plans, but the lack of an explicit rationale leaves room for speculation.
Security concerns are a plausible explanation — RTF and OLE parsing have produced high‑severity vulnerabilities historically — but Microsoft did not publicly pin the removal to a security incident or campaign. The better documentary evidence shows business and engineering trade‑offs: overlapping functionality, evolving user behavior, and a desire to reduce the default Windows footprint. For users and organizations that relied on WordPad’s specific combination of speed, offline availability, and lightweight rich‑text features, the change demands decisions: adopt a modern alternative, maintain a carefully controlled local copy of the old binaries (with known risk), or move workflows to cloud/office ecosystems. For administrators, the immediate priorities are auditing dependencies and communicating migration plans to avoid disruption.
Microsoft’s deprecation documentation and the subsequent coverage by industry outlets make the facts unambiguous: WordPad has been retired from new Windows 11 24H2 images and administrators should plan accordingly. The broader consequences — what this says about Microsoft’s product priorities, how users will adapt, and whether the community will push back or accept the change — will play out in how users and enterprises respond over the coming months.

---

---

Source: bgr.com Why Microsoft Discontinued WordPad After 30 Years - BGR

 

[ChatGPT]

Microsoft has quietly retired WordPad — the lightweight rich‑text editor that shipped with Windows for decades — removing it from Windows 11 with the 24H2 update and placing it on Microsoft’s official Deprecated Features list.

Background​

WordPad arrived as part of the Windows 95 era and for many years occupied a useful middle ground: more capable than plain‑text Notepad, but far lighter and free compared with Microsoft Word. It supported Rich Text Format (.rtf), basic document formatting, and in later years gained limited compatibility with other document formats. Its presence made Windows a self‑contained environment for simple word processing without needing third‑party software. In September 2023 Microsoft marked WordPad as deprecated; a follow‑up update clarified that WordPad would be removed from all editions of Windows beginning with Windows 11, version 24H2 (the public rollout of which began October 1, 2024). The company’s guidance explicitly recommends using Microsoft Word for rich‑text documents (.doc, .rtf) and Notepad for plain text (.txt). Microsoft also lists the WordPad binaries that will be removed so developers and administrators can plan accordingly.

---

What Microsoft actually changed​

• WordPad is no longer being updated and will be removed from Windows 11 starting with version 24H2.
• The specific binaries Microsoft lists as removed are: wordpad.exe, wordpadfilter.dll, and write.exe — a note IT teams and ISVs should not ignore.
• Microsoft’s official recommendation: use Microsoft Word for rich text and Windows Notepad for plain text.

These are not cosmetic edits — the binaries that provided RTF reading/editing functionality are gone from fresh images and will not be present after clean installs of Windows 11 24H2. Administrators and software that relied on a default RTF handler must update their guidance or ship fallbacks.

---

Why Microsoft’s public explanation is succinct — and why that matters​

Microsoft’s public documentation is terse: it lists the deprecation, removal date and migration suggestions, but it does not publish an extended rationale in marketing or product blogs. For enterprise and security teams, that leaves three important inference points:

• Maintenance cost of legacy code: older components require sustained QA, security patches, and compatibility testing across a vast matrix of hardware and OEM modifications. Removing underused components reduces that maintenance burden.
• Image and footprint management: trimming rarely used components can reduce image complexity and update surface area. This is a common motive when vendors streamline OS distributions.
• Strategic consolidation: Microsoft’s product focus has shifted toward living services — Office/Microsoft 365 and modern Store apps. Encouraging users to use Word, Word for the web, or updated Notepad aligns with that strategy.

None of those reasons are explicitly framed by Microsoft in their deprecation notice, so they remain informed inferences rather than confirmed causation. That absence of a public strategic case has amplified speculation in the community and press.

---

Security: plausible factor but not the whole story​

Why did WordPad, an innocuous simple app, become expendable? Security concerns are frequently cited by observers — and for good reason. Rich Text Format parsing has been a recurring attack surface across Microsoft’s document ecosystem for decades. Multiple high‑severity CVEs tied to RTF parsing in Word and WordPad exist in the public record (spanning 2000s-era exploits through modern RTF parser issues), and vendors have long recommended caution when opening untrusted RTF files. But: Microsoft did not say publicly that security alone drove WordPad’s removal. The official documentation does not state “we removed WordPad because of RTF vulnerabilities”; it simply marks the feature as deprecated and recommends migration paths. That means:

• Security is a credible and likely contributing factor (RTF parsing has a documented vulnerability history).
• It is not a verified, single cause — other operational and strategic reasons (maintenance, low usage, product consolidation) are at least equally plausible. Treat claims that “WordPad was removed for security reasons” as informed speculation unless Microsoft explicitly states otherwise.

---

Community reaction and immediate operational impact​

The removal triggered predictable user reaction: nostalgia, annoyance, and practical concern. Long‑time Windows users and many enterprise help‑desk teams relied on WordPad as the lightweight Zamboni between Notepad and Microsoft Word. Forums and community threads show users asking how to open existing RTF files, how to restore WordPad, and whether WordPad will return via the Microsoft Store — the short answers are: use Word/Notepad or third‑party alternatives; manual restoration is possible but unsupported; and no, WordPad is not being republished through the Microsoft Store.
Operationally, a few concrete impacts surfaced quickly:

• Systems or scripts that invoked wordpad.exe to display or print RTF files will fail unless updated. Microsoft explicitly warns developers not to take dependencies on those binaries.
• Fresh Windows 11 24H2 installs will not include WordPad; migration guidance must be provided for users who relied on it.
• Community workarounds exist: copying the accessories folder from a pre‑24H2 machine or keeping an older image preserves WordPad, but that is unsupported and carries long‑term security and reliability risks.

Forums captured both practical tips (back up C:\Program Files\Windows NT\Accessories before upgrading) and sentiment — many users mourned a small but useful tool, while others pointed to superior modern alternatives.

---

Alternatives: short‑term and long‑term choices​

For users and IT teams, the practical question is: what replaces WordPad? Here’s a compact, actionable list.

• Microsoft Word / Word for the web
• Best for fidelity with .doc/.rtf files and for enterprise workflows. Requires Microsoft 365 subscription or licensed Office. Microsoft explicitly recommends Word for rich text files.
• Windows Notepad (modernized)
• Notepad has received significant updates (spell‑check, formatting/Markdown support in preview builds, and on‑device AI features in some channels). For plain text and many quick tasks, Notepad is now a stronger contender than it was. However, it’s not a rich‑text editor.
• LibreOffice Writer / OpenOffice / Google Docs
• Free, cross‑platform alternatives that handle .rtf, .docx, and other formats. LibreOffice is widely recommended for offline, non‑proprietary workflows.
• Lightweight third‑party editors: AbiWord, Jarte, Notepad++ (for plaintext and some light formatting)
• These meet many users halfway; they are worth testing on enterprise images for compatibility and security.
• Custom in‑house viewer/renderer or an enterprise document viewer
• For organizations that rely on RTF viewing but not editing, shipping a hardened viewer or integrating a server‑side render pipeline may be the safest path.

When recommending a replacement, weigh three factors: format fidelity (does the app preserve the document’s layout?, security posture (how quickly is the app patched?, and cost (licensing or migration effort).

---

For IT admins and developers: a checklist​

• Inventory: Search your environment for calls to wordpad.exe, write.exe or any scripts that rely on WordPad as the default RTF handler.
• Replace: Repoint those scripts to a supported viewer (Microsoft Word, LibreOffice, a custom viewer) or rework the workflow to remove the dependency.
• Communicate: Notify end users that WordPad will not be present on new Windows 11 24H2 images and provide recommended replacements with step‑by‑step guides.
• Backup (if needed): If certain machines absolutely must retain WordPad, back up the Accessories folder (C:\Program Files\Windows NT\Accessories) before upgrading — but understand this is a stopgap and not supported.
• Security review: If your environment hosts files that were validated via WordPad’s parsing behavior, run a threat review — RTF files are known attack vectors. Update protective controls and scanning accordingly.

---

Restoration is possible but unsupported — caveats and risks​

Community guides show that copying WordPad’s executable and associated DLLs from an older Windows install to a 24H2 machine can restore functionality locally, albeit imperfectly. That approach is effectively “living with a legacy binary.” It brings immediate productivity relief, but:

• There is no official support or security updates for that restored binary. Over time, unpatched parsers can be exploited.
• The restored binary may fail to integrate cleanly with modern Windows features or may be flagged by security tools.
• Enterprise policy and compliance teams may disallow unsupported binaries on corporate endpoints.

Therefore, the pragmatic recommendation: use restoration only as a short‑term mitigation while migrating to a supported solution.

---

Product strategy and the subscription angle: hard facts, soft interpretations​

One media narrative frames WordPad’s removal as another nudge toward Microsoft’s subscription ecosystem. That argument has traction because Word, the recommended replacement, is a commercial product within Microsoft 365 — a revenue stream for Microsoft. However, a few points temper a conspiratorial reading:

• Microsoft explicitly points to Notepad as a free alternative for plain text, and Notepad’s modernization removes some of WordPad’s use cases without forcing a purchase.
• Microsoft historically culls legacy code and apps for maintainability and security long before any monetization consideration. The deprecation notice precedes the removal by many months.

In short: subscription economics matter to Microsoft’s overall business, but the empirical evidence for a roadmap driven solely by monetization is weak. The decision looks more like a mix of product consolidation, modernization, and maintenance calculus — with commercial upsell as a side effect rather than the official driver. That distinction matters for readers trying to parse corporate motives from product engineering realities.

---

What this means for everyday users​

• Casual users who used WordPad for occasional formatted notes will find equivalent or better options: Word for heavyweight documents, Notepad for plain text, or LibreOffice/Google Docs for free rich‑text editing.
• Users who relied on WordPad‘s simplicity will miss the convenience. Expect an adjustment period where users learn new tools or adopt community workarounds. Community threads show a mixture of nostalgia and pragmatic migration help from power users.
• For people who use WordPad to open questionable RTFs (e.g., email attachments), this retirement may be positive: modern Word uses Protected View and other mitigations that can reduce risk. Still, the surface area for RTF exploitation remains irrespective of the viewer, so continue following best practices for unknown attachments.

---

Strengths of Microsoft’s approach — and the shortcomings​

Strengths

• Clarity on migration: Microsoft’s documentation states what’s removed and what to use instead, giving enterprises definitive guidance.
• Reduced maintenance surface: Removing legacy components simplifies QA and reduces attack surface over time.
• Acceleration of modern tools: Microsoft is investing in Notepad and other small apps, which can absorb some WordPad tasks while offering modern features like Markdown and on‑device AI.

Shortcomings / Risks

• User experience gap: Microsoft did not ship a directly equivalent built‑in replacement for the WordPad use case (a free, lightweight RTF editor). That gap leaves price‑sensitive users or low‑resource scenarios exposed.
• Unsupported workarounds: The community’s “copy the executable” fixes are fragile and risky long term. They shift the burden to admins and users rather than the vendor.
• Developer friction: Apps and scripts that assumed wordpad.exe exist need changes. In complex enterprise automation, such dependencies are common and non‑trivial to refactor.

---

What to watch next​

• Will Microsoft document a formal migration tool or produce a lightweight RTF viewer in the Microsoft Store? Current documentation suggests no Store path has been announced. Community pressure could influence product choices (Microsoft has reversed course before on other apps), but nothing official has been published.
• How quickly will Notepad’s new features (formatting, Markdown, local AI) arrive broadly and fill the space left by WordPad? Notepad’s roadmap is public in preview channels and will be a key mitigator.
• Will security incident data show a decline in RTF‑based exploits tied to built‑in viewers? That would be an empirical metric suggesting security benefits from removing legacy parsers — worth watching in vulnerability advisories and patch notes.

---

Conclusion​

WordPad’s removal marks the end of a long chapter in Windows history: a small, dependable app that served millions for nearly three decades. Microsoft’s move to deprecate and remove WordPad from Windows 11 24H2 is documented and actionable — the binaries are listed, the timeline is public, and migration guidance exists. The decision is defensible on several grounds — maintenance, modernization, and likely security considerations — but it also exposes practical gaps for users who valued a free, built‑in rich‑text editor. Organizations must inventory dependencies, update automations that call WordPad binaries, and provide alternatives to end users. For those who want WordPad’s UI back, community workarounds will keep it running for a while, but those solutions are inherently unsupported and potentially risky.
This is a moment for IT teams, power users, and ordinary Windows customers to evaluate their document workflows: align default tools with organizational policy, choose supported viewers for sensitive content, and examine whether new Notepad enhancements or third‑party suites are adequate substitutes. The Windows ecosystem has evolved; the little app that sat between Notepad and Word is gone, but the larger platform continues to shift — and the practical challenge now is making that transition safely, deliberately, and with clear communication to users.

---

Source: bgr.com Why Microsoft Discontinued WordPad After 30 Years - BGR