Microsoft spent 2025 accelerating a long-running cleanup of legacy Windows code and services — quietly removing some familiar apps, formally retiring long‑deprecated protocols, and setting hard timelines for administrators to migrate away from decades‑old dependencies.
Background
Microsoft’s deprecation → removal lifecycle has always followed a three‑stage arc: deprecate (document and stop active development), discourage (recommend alternatives), then remove (strip binaries and APIs from future images). In 2025 that arc reached several high‑visibility endpoints. The company tied removals to specific OS releases (notably
Windows 11, version 24H2 and
Windows Server 2025) and published formal guidance and Knowledge Base updates that specify what’s gone, what remains supported for a transition window, and where administrators should focus migration efforts. This story matters because removals are not mere UI changes — they can delete on‑disk binaries, management snap‑ins, automation APIs, and authentication paths that enterprise systems or embedded devices still rely on. The work in 2025 was both broad and deliberate: the aim was to reduce attack surface, simplify the Windows image and testing matrix, and push customers toward modern alternatives such as DNS, modern PowerShell, and the new Teams client.
Overview: the big-ticket removals and deprecations in 2025
Below is a concise list of the most consequential Windows features Microsoft removed or placed into formal retirement timelines during 2025. Each item includes the official status (removed vs. deprecated), the release or date that triggered the change, and the practical impact.
- WordPad — Removed: WordPad was removed from all editions starting with Windows 11, version 24H2 and Windows Server 2025; the binaries (wordpad.exe, wordpadfilter.dll, write.exe) are no longer included in fresh images. Microsoft recommends Microsoft Word for .rtf/.docx and Notepad for plain text.
- Windows PowerShell 2.0 engine — Removed: The legacy PowerShell 2.0 engine, deprecated in 2017, was removed from Windows 11 24H2 images beginning August 2025 and from Windows Server 2025 images in September 2025. Microsoft published KB 5065506 with migration guidance.
- WINS (Windows Internet Name Service) — Removal planned after Server 2025: Microsoft formalized that Windows Server 2025 will be the last LTSC to include WINS and that WINS will not be included in server images following that release; WINS components in Server 2025 are governed by its lifecycle through the product’s support window. Microsoft published a KB titled “WINS removal: Moving forward with modern name resolution” outlining the timeline and rationale.
- Classic Microsoft Teams (the “classic” client) — End of availability: Microsoft completed the transition to the New Teams client and declared the classic Teams client unavailable as of July 1, 2025. The company provided timelines for end of support and end of availability and offered web and new‑client alternatives.
- NTLMv1 and related legacy auth elements — Removed / Deprecated: NTLMv1 was explicitly removed starting with Windows 11 24H2 and Windows Server 2025 as part of an ongoing push to modernize authentication. Microsoft’s “features removed” and “deprecated features” pages list NTLMv1 among removed items.
- Windows Mixed Reality & AllJoyn — Removed/Retired: Windows Mixed Reality components were removed starting with Windows 11 24H2, and Microsoft’s AllJoyn implementation was retired. Both moves reflect low adoption and a shift to modern cross‑platform / cloud alternatives.
- Microsoft Defender Application Guard for Edge, Suggested Actions, and other niche features — Deprecated or removed: A variety of lower‑usage features were deprecated or removed during 2024–2025 in follow‑up to the 24H2 wave; these include Suggested Actions, some legacy DRM services, Paint 3D (earlier), and others that Microsoft has explicitly listed on its removal/deprecated features pages. Community coverage and Microsoft’s deprecated‑feature resources document these changes.
- Microsoft 365 / Office lifecycle changes tied to Windows 10 EOL: Windows 10 mainstream support ended in October 2025; Microsoft announced nuanced changes to Office/Microsoft 365 support windows, including extended security update arrangements for Microsoft 365 Apps on Windows 10 and the retirement of older Office perpetual versions (Office 2016/2019) with an October 14, 2025 cutoff for certain kinds of support. Microsoft and Tech Community posts clarified timeline and extension details.
Each of these items has a Microsoft‑published page that lays out the technical details and migration recommendations; where available Microsoft KBs (for example, PowerShell 2.0 removal and the WINS removal article) provide step‑by‑step guidance.
Why Microsoft made these choices
Security and attack surface reduction
Several removals are explicitly security‑driven. PowerShell 2.0 lacks modern defenses such as AMSI integration, script block logging, and constrained language protections; retaining it in images kept an exploitable downgrade vector for attackers. Similarly, NetBIOS/WINS and NTLMv1 are legacy network auth/name resolution systems with weaker security profiles than modern DNS+Kerberos/FIDO solutions, so removing them reduces long‑term platform risk. Microsoft’s KBs and lifecycle notes consistently emphasize security as a principal driver.
Low usage and product consolidation
Features with narrow usage — AllJoyn, Paint 3D, Suggested Actions — cost engineering and testing effort while delivering minimal user value. Removing them lets Microsoft focus development resources on higher‑impact areas (e.g., Notepad improvements, Teams modernization, Copilot integrations). Community reports and Microsoft’s deprecated features list show usage and telemetry often factor into removal decisions.
Simplified platform surface for testing and cloud integration
By standardizing on fewer in‑box components (PowerShell 5.1 / 7.x rather than multiple engines; DNS rather than NetBIOS/WINS for name resolution), Microsoft reduces image complexity and makes cloud integrations and automated testing more predictable. This matters for both Microsoft and ISVs who must test products across OS builds and configurations.
Deep dive: selected items, technical specifics and migration paths
WordPad — what changed and what to do
- Status: Removed starting Windows 11, version 24H2 and Windows Server 2025. The WordPad binaries were explicitly called out for removal.
- Impact: Stock Windows images no longer include a default RTF editor; scripts or third‑party tools that invoked wordpad.exe or write.exe will break on fresh installs.
- Migration options:
- Use Microsoft Word (commercial) for full RTF/DOCX editing.
- Use an alternate free editor (e.g., LibreOffice, third‑party RTF viewers) where cost is an issue.
- Update scripts to avoid direct execution of WordPad binaries; prefer file associations or library APIs.
PowerShell 2.0 — timeline, technical reasons, and mitigations
- Status: Removed from Windows 11 24H2 images (Aug 2025) and Windows Server 2025 images (Sept 2025). Guidance appears in KB 5065506.
- Why: v2.0 lacks AMSI, script block logging, and other telemetry/defensive features. It relies on legacy CLR hosting that complicates modern module compatibility.
- Mitigation checklist:
- Inventory scripts that explicitly call powershell.exe -Version 2.
- Test and migrate scripts to PowerShell 5.1 or PowerShell 7.x (pwsh).
- For rare cases where v2 behaviour is required, Microsoft published a voluntary reinstall package (ps2DLC.zip) and steps, but this is a stopgap and not a long‑term supported path.
WINS — end of the NetBIOS era on Windows Servers
- Status: Removal scheduled: Windows Server 2025 is explicitly the last LTSC to include WINS; Microsoft’s removal guidance was published in a KB (“WINS removal: Moving forward with modern name resolution”). The KB explains WINS will remain under the Server 2025 lifecycle but will be absent from images after that release.
- Why: DNS is an RFC‑backed, distributed system that scales far better and supports modern mitigations (DNSSEC, conditional forwarding, split‑horizon).
- Migration guidance:
- Inventory services and devices using NetBIOS short names.
- Plan a DNS‑first migration: map short‑name dependencies to DNS names, use DNS suffixes/conditional forwarders where necessary.
- Consider hybrid solutions (DNS wrappers, DHCP option configuration) for legacy appliances that cannot be reconfigured immediately. Microsoft and community posts recommend a long runway — Server 2025 lifecycle provides years to complete migration.
Classic Teams — forced upgrade and user impact
- Status: Classic Teams reached end of availability on July 1, 2025; users were required to move to the New Teams client or the web app. Microsoft documented the timeline and provided upgrade tooling and pre‑installation scripts for mass rollouts.
- Impact: Organizations that delayed upgrades faced blocked clients and an enforced migration path; internal training and compatibility testing were the main administrative tasks.
- Recommended actions:
- Use Microsoft’s pre‑install scripts and deployment guidance to transition managed fleets.
- Validate add‑ins and meeting integrations; for users who must stay on older OS versions, plan web app fallbacks.
NTLM and other enterprise authentication changes
- Status: NTLMv1 removed starting Windows 11 24H2 and Windows Server 2025; Microsoft’s “removed features” reference lists NTLM among removed items.
- Impact: Systems or appliances that only support NTLMv1 will fail authentication on up‑to‑date clients/servers.
- Mitigation:
- Inventory authentication paths with tools like Microsoft Assessment and Planning (MAP) and AD logs.
- Migrate to Kerberos, NTLMv2 (short stopgap), or modern identity solutions (Microsoft Entra / Azure AD + OAuth/OIDC).
- Consider conditional access and phased disablement to reduce outage risk.
Notable removals and deprecation details (concise catalog)
- Removed from Windows 11 24H2 / Windows Server 2025:
- WordPad (binaries removed).
- NTLMv1.
- Windows Mixed Reality components.
- AllJoyn implementation (retired).
- Deprecated earlier and completed/announced in 2025:
- PowerShell 2.0 (final removal executed mid‑2025).
- Classic Teams end of availability (July 1, 2025).
- Suggested Actions (deprecated; no further updates).
- Paint 3D and other Store‑delivered / low‑usage apps (deprecated earlier; removal followed).
This condensed catalog is drawn from Microsoft’s “what’s new” / “deprecated features” pages, KB articles, and contemporaneous reporting by technical outlets who tracked the 24H2/Server 2025 cycle.
Strengths of Microsoft’s approach
- Predictability for IT planning: Microsoft tied removals to specific OS releases and published lifecycle windows (for example, WINS remains supported through the Server 2025 lifecycle), giving enterprises time to migrate rather than springing sudden cutoffs.
- Security posture improvement: Stripping legacy runtimes that cannot be tied into modern defenses (PowerShell 2.0, NTLMv1) shores up the platform for defenders and reduces well‑known downgrade attacks.
- Cleaner platform for innovation: Fewer in‑box legacy components lowers test surface and allows Microsoft to deliver richer features (Notepad enhancements, Copilot integrations) without indefinite backwards‑compatibility baggage.
Real risks and pain points for customers
- Legacy dependencies and brownfield environments: Industrial appliances, POS systems, and older line‑of‑business apps that expect NetBIOS/WINS or older auth may not be trivial to update. The migration cost (time, money, vendor coordination) can be material for some organizations.
- Third‑party software and automation breakage: Scripts invoking PowerShell v2, tools calling wordpad.exe, or management processes tied to retired MMC snap‑ins will break on fresh images; undocumented dependencies can be the hardest to find.
- Perception of forced obsolescence: End users who rely on lightweight in‑box tools (WordPad, small utilities) feel loss of convenience; organizations with conservative change policies may see this as a driver to buy commercial replacements or invest in test/migration cycles. Community coverage captured this sentiment when WordPad was removed.
- Fragmented support windows: While Microsoft provided multi‑year runways in many cases, the patchwork of deprecations across client and server lines, Teams timelines, and Office lifecycles requires disciplined lifecycle management to avoid surprises. For example, Windows 10 EOL intersects Office/365 support updates in ways that need careful calendar coordination.
Practical checklist for IT teams — a migration playbook
- Inventory: Run automated scans to detect use of:
- PowerShell v2 invocations.
- Applications or scripts that call wordpad.exe/write.exe.
- Devices relying on WINS/NetBIOS name resolution and NTLMv1 authentication.
- Classic Teams installations and custom Teams integrations.
- Prioritize: Categorize items by business criticality and replacement difficulty:
- Critical business apps and appliances first.
- Administrative scripts and management tooling next.
- Low‑usage personal utilities last.
- Test & remediate:
- Port PowerShell scripts to 5.1/7.x and validate behavior.
- Update automation to use modern management APIs (Microsoft Graph vs. older PowerShell modules).
- Reconfigure appliances to use DNS; where impossible, plan for network workarounds or vendor upgrades.
- Deploy incrementally:
- Use ringed deployments, pilot groups, and imaging to validate the new baseline.
- For Teams, use the New Teams preinstall scripts Microsoft published to mass deploy the new client before the classic client was blocked.
- Communicate:
- Notify end users about removed utilities (WordPad) and available alternatives.
- Provide training and support pages for changes that materially impact workflows.
- Monitor & audit post‑change:
- Check for authentication failures and missing automation tasks for a defined window after rollout.
- Use telemetry to detect failed launches or device incompatibilities early.
What was unverifiable or left ambiguous (and why that matters)
Microsoft’s formal KBs and Learn pages provide timelines and lists of removed/deprecated features, but they sometimes omit granular rationale for individual removals (for example, the specific engineering cost vs. security tradeoff for WordPad). In a few cases the community and independent reporting filled gaps about likely motives (low usage, maintenance cost), but those are informed inferences rather than explicit Microsoft statements. Where Microsoft has published change logs and KB IDs (e.g., PowerShell 2.0 removal KB 5065506, WINS removal KB 5071836) the technical specifics and mitigation options are authoritative; where public explanation is thinner, readers should treat stated rationale (e.g., "we recommend Word/Notepad") as guidance rather than a deep policy whitepaper.
Bottom line: modernization with caveats
2025 was a year when Microsoft stopped politely
deprecated and moved decisively to
removed for a set of long‑running legacy Windows features. The technical reasons are clear: reduce attack surface, simplify the testing/ship matrix, and concentrate product investment. That strategy benefits security and future‑proofing, but it also imposes real migration costs on organizations still operating with legacy appliances, undocumented scripts, or specialized workflows.
For IT leaders, the advice is straightforward and urgent: inventory aggressively, plan migrations with realistic timelines, and treat Microsoft’s lifecycle documents and KBs as the authoritative guide. For enthusiasts and power users, many removals can be accommodated with third‑party alternatives — but the era of “Windows includes everything forever” is over. The platform is leaner now, and that has real security and engineering benefits — provided migrations are planned and executed with care.
The catalog above consolidates Microsoft’s official removal/deprecation pages, product lifecycle notices, and contemporaneous coverage from technical outlets and community discussion to present a clear, actionable record of what Microsoft removed or deprecated in 2025 and what organizations should do next.
Source: Neowin
https://www.neowin.net/news/every-windows-feature-microsoft-removed-or-deprecated-in-2025/