A lawsuit filed in San Diego Superior Court demands that Microsoft continue issuing free security updates for Windows 10 until the aging operating system’s global market share falls below roughly 10 percent. The complaint, brought by plaintiff Lawrence Klein, names the October 14, 2025 end‑of‑support date as a forced obsolescence tactic that will harm consumers, school districts, nonprofits, and small businesses while steering millions toward new AI‑ready hardware.

The legal challenge arrives as Microsoft stands firm on its published lifecycle calendar. After October 14, Windows 10 Home and Pro editions will stop receiving routine quality and security patches, leaving an install base that still accounts for between 40 and 45 percent of all Windows desktops worldwide without baseline protection. The plaintiff argues that sunsetting support for a product that hundreds of millions of people still rely on everyday is not a routine business decision. It is, the complaint alleges, a calculated move designed to monopolize the emerging generative AI market by forcing users onto Windows 11 devices that ship with Copilot and meet the hardware requirements for Copilot+ PCs.

A Courtroom Showdown Over Windows 10’s Expiration Date

The lawsuit frames the end‑of‑support event as more than an inconvenience. The filing interlaces consumer‑protection claims, competition law arguments, and environmental concerns to paint a picture of corporate overreach. Klein asks the court to issue an injunction that would block Microsoft from turning off the free update pipeline until the Windows 10 install base shrinks to a plaintiff‑defined floor, reported in court documents as about 10 percent of the worldwide Windows population. Such an order would be extraordinary: no U.S. court has ever compelled a major platform vendor to extend free security patching for a legacy product against its published lifecycle policy.

The complaint’s core allegations rest on three pillars. First, that ending free updates while a supermajority of devices remain in service will coerce users into buying new PCs, paying for Extended Security Updates (ESU), or operating unprotected machines that invite cyberattacks. Second, that the timing is anticompetitive because it advantages Microsoft’s generative AI ambitions. Windows 11, and particularly the Copilot+ device class, requires a neural processing unit (NPU) capable of at least 40 trillion operations per second (TOPS), a hardware‑level gate that excludes most Windows 10 machines. Third, that the forced turnover will generate mountains of avoidable electronic waste, deepening environmental inequities for households and public institutions that cannot afford rapid hardware refreshes.

The Stakes: Millions of PCs Left Unpatched

StatCounter data from mid‑2025 underlines the scale of the problem. Although Windows 11 overtook Windows 10 in global desktop share for the first time earlier this year, Windows 10 still commanded a low‑to‑mid‑40s percentage of the market in July. Analysts project that roughly 240 million PCs are ineligible for the free Windows 11 upgrade because they lack a Trusted Platform Module (TPM) 2.0 chip, Secure Boot support, or a sufficiently modern CPU. Many of those devices remain perfectly serviceable for everyday tasks—web browsing, office productivity, media playback—but will lose vendor patching in a matter of months.

Cybersecurity researchers warn that an unsupported OS is a honeypot for adversaries. Once the regular Patch Tuesday releases cease, any new vulnerability discovered in Windows 10 will remain unpatched forever unless a user buys into the ESU program. Past end‑of‑support events for Windows 7 and XP triggered spikes in malware infections, and that pattern is expected to repeat on an even larger scale given the current size of the Windows 10 fleet. Schools, municipal governments, and small medical practices that operate on tight budgets are especially vulnerable; a spate of ransomware attacks following the 2020 Windows 7 sunset offers a grim preview.

Microsoft’s ESU Lifeline

Microsoft has not ignored the predicament entirely. The company is offering a consumer Extended Security Updates program that will deliver critical patches through October 13, 2026. For eligible Windows 10 devices, enrollment can be achieved by syncing a Microsoft Account, redeeming Microsoft Rewards points, or making a one‑time purchase from the Microsoft Store. The final cost and exact mechanics vary by region, but the bridge buys one additional year of security coverage.

Enterprises and large organizations have long had access to commercial ESU agreements, which can extend support even further. Microsoft’s official end‑of‑support page encourages users to “move to a new PC” and highlights OneDrive as a migration tool, but the original source material provided by the forum discussion makes no mention of the lawsuit or any concession to extend free support. The page functions as a straightforward transition guide, not a response to litigation.

The existence of ESU—and its associated costs—cuts two ways in the legal fight. The plaintiff will argue that charging for what was once free imposes a de facto tax on the unwilling, while Microsoft will point to ESU as a reasonable mitigation that undermines claims of irreparable harm. Courts routinely consider whether a party has taken steps to soften the blow when evaluating the need for emergency judicial intervention.

The AI Angle: Copilot+ and Hardware Gating

The complaint’s most provocative theory ties the Windows 10 sunset directly to Microsoft’s AI roadmap. The Copilot+ PC certification program, introduced in 2024, mandates an NPU with at least 40 TOPS of performance. Only the latest silicon from Qualcomm, Intel, and AMD meets that bar. By herding users onto Copilot+ devices, the lawsuit contends, Microsoft ensures a captive audience for its Copilot assistant, Bing AI, and other cloud‑connected AI services while raising barriers for competitors like Google, Apple, and the open‑source AI community.

This hardware‑tethering argument is not entirely new. Industry observers have noted since Windows 11’s launch that the TPM 2.0 and CPU requirements effectively deprecated millions of otherwise functional computers. The Copilot+ tier adds another layer: even a Windows 11 PC without a qualifying NPU cannot run certain AI workloads locally. The plaintiff argues that the cumulative effect is an illegal tying arrangement—forcing consumers to purchase new hardware to maintain security updates and then steering them toward Microsoft’s own AI ecosystem.

Microsoft has consistently defended its hardware baselines on security grounds. TPM 2.0, Secure Boot, and modern processors enable stronger encryption, virtualization‑based security, and system integrity features that are difficult to retrofit onto older architectures. The NPU requirement, the company says, is about delivering a “new category of PC” that can handle generative AI tasks with low latency and high battery efficiency—not a plan to lock out rivals.

Environmental and Public Interest Claims

The e‑waste argument resonates beyond the courtroom. United Nations reports estimate that the world generates over 50 million metric tons of electronic waste annually, and only a fraction is properly recycled. Forcing millions of otherwise functional laptops and desktops into retirement because they fail a cryptographic or AI‑acceleration check would add substantially to that stream. The complaint highlights the environmental injustice of a policy that most burdens lower‑income households and underfunded public institutions.

Right‑to‑repair advocates and sustainability groups have already begun citing the lawsuit as evidence that device lifecycles are being artificially shortened. Several European regulators are examining similar issues, and the lawsuit arrives at a moment when legislative bodies in the U.S. are debating digital right‑to‑repair and consumer‑protection bills. Even if the legal remedies fail, the reputational pressure alone may force Microsoft to expand trade‑in programs, improve recycling partnerships, or offer free ESU to verified nonprofits and schools.

Precedent is not on the plaintiff’s side. Courts apply a four‑factor test when considering preliminary injunctions: likelihood of success on the merits, irreparable harm absent an injunction, the balance of equities tipping in the movant’s favor, and the public interest. Satisfying all four is a heavy lift for any private litigant, and the extraordinary nature of the relief requested—global, open‑ended, and market‑share‑contingent—almost certainly exceeds what a state trial court is willing to order.

First, the claims rest heavily on allegations of intent and market definitions that will require extensive discovery to prove. Antitrust claims specifically demand proof of monopoly power in a relevant market and a showing that the conduct at issue harmed competition, not just a competitor. The plaintiff’s “generative AI market” framing is novel and untested. Microsoft will argue that Windows, Copilot, and AI accelerators are separate products, that users have alternatives (macOS, Linux, ChromeOS, and web‑based AI services), and that lifecycles are a standard industry practice.

Second, the availability of the ESU program and the free upgrade path to Windows 11 (for compatible hardware) weaken the argument that users face irreparable harm. While paying for updates or buying a new PC imposes costs, money damages are the classic remedy that courts can award after trial; injunctive relief is reserved for situations where the harm cannot be fixed later with a check. Microsoft’s legal team will almost certainly move to dismiss or oppose any emergency motion by emphasizing the adequacy of legal remedies.

Third, the balance of hardships and public interest factors could cut in either direction. The public certainly benefits from secure computing, but courts are reluctant to micromanage the product roadmaps of private companies. Ordering Microsoft to maintain legacy code indefinitely would impose substantial engineering, testing, and support costs that could divert resources from security innovation elsewhere. A narrow injunction targeting specific vulnerable user classes—such as hospitals or election systems—would be far more manageable, but the plaintiff’s current request goes well beyond that.

What This Means for IT Teams and Home Users

While the legal drama unfolds, the clock continues to tick. Prudent organizations and individuals cannot wait for a court ruling that may never materialize. The actionable steps are clear:

  • Inventory and classify. Run a full hardware and software audit to identify every Windows 10 device in your environment. Flag machines that meet Windows 11 hardware requirements, those that require only a BIOS setting change (e.g., enabling TPM 2.0), and those that are definitively incompatible.
  • Prioritize internet‑facing systems. Any device that processes email, web traffic, or sensitive data must be at the top of the migration or ESU enrollment queue. Compensating controls—network segmentation, application allowlisting, and enhanced endpoint detection—can buy time but are not substitutes for patching.
  • Test and back up. Before mass migrations, validate Windows 11 compatibility of critical applications in a pilot group. Ensure full system backups and a rollback plan exist for every device.
  • Evaluate ESU realistically. For machines that cannot be replaced before the October deadline, calculate the cost of one year of ESU against the price of a new device. For some budget‑strapped organizations, the one‑time fee may be cheaper than a hardware refresh, especially when paired with a plan to transition during the extension window.
  • Watch for Microsoft’s response. Past end‑of‑support transitions have seen last‑minute policy tweaks, expanded free ESU offers for certain education or nonprofit customers, and improved trade‑in values. The lawsuit amplifies the public pressure for such concessions, so monitor Microsoft’s official Windows End‑of‑Support page and related announcements.

Beyond the Courtroom: The Likely Outcome

The odds of a sweeping, market‑share‑triggered injunction are slim. What is far more probable is a negotiated settlement or unilateral policy changes that address the most acute pain points without upending Microsoft’s lifecycle model. The lawsuit has already succeeded in one respect: it transformed the Windows 10 sunset from an IT project management headache into a national story about corporate responsibility, digital equity, and the environmental cost of planned obsolescence.

Microsoft may respond by making ESU enrollment significantly easier for consumers, expanding free access for schools and nonprofits, or pumping fresh incentives into its device trade‑in and recycling programs. The company could also adjust the Windows 11 hardware baseline—something it has done in limited ways before—or offer a standalone Copilot experience that works on older hardware, undercutting the antitrust narrative.

For the tens of millions of users still running Windows 10, the lawsuit provides a glimmer of hope that the cost of staying current may be lowered. But it is not a plan. The October 14 deadline remains real. In the time it takes for courts to deliberate, attackers will be scanning for unpatched Windows 10 machines. The prudent path is to treat the litigation as a possible tailwind for future concessions while preparing your own migration strategy based on the facts as they exist today.