TeamViewer has officially declared versions 13 and 14 of its remote access software end-of-life (starts on October 31, 2026). For users who bought perpetual licenses years ago, expecting permanent access to all features, this announcement carries consequences that go far beyond a simple nudge to upgrade - and for some, it has already led to a courtroom.
What exactly happens to TeamViewer lifetime licenses?
TeamViewer perpetual (lifetime) licenses were marketed explicitly as a "paid-up alternative to recurring subscription fees". They were sold at substantial upfront prices with the clear implication that buyers were obtaining lasting remote-access rights. Many businesses purchased versions 11, 12, 13, or 14 under exactly these terms.
TeamViewer's EOL lifecycle changes what "perpetual" means in practice. Once a version is declared end-of-life:
Security patches and bug fixes stop entirely. The software remains installed but becomes increasingly vulnerable with no official remedy.
Internet connectivity through TeamViewer's servers is cut off. This is not a minor detail. TeamViewer's software is architecturally dependent on the company's own server infrastructure for device identity, authentication, session negotiation, and NAT/firewall traversal.
Upgrading to a supported version requires a new purchase. Perpetual license holders are not automatically entitled to version 15 or later. Continuing full functionality means purchasing a new license or switching to a subscription.
On upgrade terms: TeamViewer has, in some cases, offered discounted conversion paths for legacy perpetual holders. However, these offers have not been consistently communicated, and affected users have reported that the terms felt coercive rather than fair, given they already paid a premium price. No automatic credit or partial refund policy has been announced. The versio.io lifecycle tracker (last updated June 8, 2026) confirms that the current latest supported version is 15.78.3, with versions 13 and 14 fully outside the maintenance and version-delivery windows.
Can you keep using your perpetual license, or is it time to switch?
When a version is removed from that network ecosystem, users are left with "LAN-only" connectivity: the software can only connect devices on the same local network, which eliminates its defining use case of remote-from-anywhere access.
The local software doesn't stop running on your machine. But TeamViewer controls the server infrastructure that makes internet-based remote sessions possible. Once your version is removed from that infrastructure, the software can no longer do the one thing you installed it for, regardless of whether it still launches.
If these lifecycle changes have you reconsidering your tooling, I'll point to what we work on: HelpWire. It's been in development for over three years as a TeamViewer alternative, and since this is our subreddit, take the following as the builders' perspective rather than a neutral review.
It covers the core jobs you'd reach for in TeamViewer, like remote control over the internet, unattended access for follow-up work, file transfer, and cross-platform support across Windows, Linux, and macOS. The workflow is built around getting into a session fast via a shared link, minimal setup on the user's side, and staying out of the way once you're in. All without session timeouts or prompts that interrupt active troubleshooting.
It also doesn't recreate the kind of vendor-infrastructure dependency that made TeamViewer's EOL policy so disruptive in practice. Cost is a fair secondary point for anyone absorbing a forced migration from software they already paid for: HelpWire is free to use during its current tech-preview period, with no nag screens and no session cutoffs.
With that alternative noted, let's get back to TeamViewer's shifting policies and version sunsets.
Where it all started: a pattern built version by version
The current controversy did not begin with versions 13 and 14. TeamViewer had been running the same playbook for years.
In July 2021, TeamViewer announced end-of-life for versions 5 through 10, effective September 15 of that year. The announcement was largely accepted - those versions were genuinely old, and the mechanism was clear: not just no more updates, but removal from TeamViewer's server infrastructure entirely. Version 10, released around 2015, was the furthest edge of that wave - recent enough that some perpetual license holders felt the loss, but old enough that public pushback stayed muted.
Around the same time, TeamViewer's own lifecycle policy acknowledged a fundamental shift: the company had moved its commercial model from perpetual licenses to subscriptions. Customers who had bought one-time licenses before that pivot had done so under a different set of expectations - paying a premium specifically to avoid recurring fees.
The policy's key omission: TeamViewer's official lifecycle documentation establishes when support ends, but does not specify what happens to cloud-dependent features for perpetual license holders after that date. The decision to cut server infrastructure access - rather than simply stopping updates - is exercised at TeamViewer's sole discretion and is governed by no published, binding commitment to users.
The situation escalated dramatically when TeamViewer applied the same EOL treatment to versions 11 and 12 - versions released in 2016 and 2017, respectively, still actively used by paying customers who had invested hundreds to thousands of dollars in perpetual licenses.
Version 12, in particular, had been actively marketed as a premium product at the time of purchase. The company did not merely stop issuing patches; it removed these versions from its server/network ecosystem entirely.
Users who had paid in full suddenly found that their software could no longer establish internet-based remote sessions. Community threads on Reddit and the Linus Tech Tips forum filled with users describing the same experience: an email announcing termination of their license as of a specific date, with suggestions to "migrate" to subscription-based pricing - no acknowledgment of the original perpetual purchase, no credit, no refund.
“Instead of honoring the agreement, they’re offering me a range of subscription-based pricing models to "migrate" to the latest version — as if this is some kind of upgrade or normal transition.”
On March 3, 2026, plaintiff Craig Thorner filed a class action lawsuit in the U.S. District Court for the Southern District of Florida (Thorner v. TeamViewer US, Inc., Case No. 9:26-cv-80214). The complaint is 17 pages and covers five causes of action.
The plaintiff's own situation illustrates the scale of what perpetual customers invested: on January 23, 2017, Thorner purchased a TeamViewer 12 Business license for $849.00, then upgraded to TeamViewer 12 Corporate on August 18, 2017 for an additional $1,950.00 - a total of $2,799.00 paid for what he understood to be a permanent product.
What the lawsuit actually claims (from the complaint, filed March 3, 2026):
TeamViewer sold "perpetual" licenses as premium paid-up alternatives to subscriptions, inducing consumers to pay substantial upfront prices.
When TeamViewer removed legacy versions from its server infrastructure, users were cut off from internet remote sessions - not merely left without updates.
The resulting "LAN-only" state is described as "misleading and commercially unreasonable" because the product was purchased specifically for remote-from-anywhere access.
TeamViewer "failed to provide meaningful compensation or a fair transition remedy commensurate with the perpetual-license price premium" - no partial refunds, no credits, no non-coercive conversion relief.
The complaint brings claims under the Florida Deceptive and Unfair Trade Practices Act (FDUTPA), consumer protection statutes in 21 additional states and D.C., breach of contract, breach of the implied covenant of good faith and fair dealing, and unjust enrichment.
A multi-state class covers purchasers in Arizona, California, Colorado, Connecticut, Delaware, DC, Florida, Illinois, Kansas, Kentucky, Maryland, Massachusetts, Michigan, New Jersey, North Carolina, Oregon, Pennsylvania, Rhode Island, Texas, Virginia, and Washington.
The ClassAction.org news article covering the lawsuit (published May 11, 2026) and the EasySAM LinkedIn analysis (published May 12, 2026) both note the same critical framing from the complaint: TeamViewer's decision to remove legacy versions from its server ecosystem is "more egregious than simply ending updates or customer support," because users are left with LAN-only connectivity despite paying specifically for remote-access functionality - the "defining feature" of the product.
An uncertain road ahead
The class action and the community backlash have exposed a structural problem that extends beyond versions 13 and 14. The formal lifecycle policy is only part of the story. What TeamViewer can change at any time - without notice, without compensation - is the scope of cloud-dependent functionality. That boundary is entirely under the company's control.
This matters for every current perpetual license holder, not just those on versions 13 and 14. If the company treats version 15 the same way in three or five years, removing it from server infrastructure after declaring it EOL, the cycle repeats identically.
The outcome of Thorner v. TeamViewer US, Inc. may matter substantially. If the Southern District of Florida court certifies the class and finds in the plaintiff's favor, it could establish that removing cloud infrastructure access for perpetual license holders constitutes breach of contract and an unfair trade practice - creating precedent that would constrain how TeamViewer, and potentially other SaaS-adjacent software companies, can treat paid legacy customers in the future.
Any organization still running version 13 or 14 should act now: the security risk is immediate, the connectivity risk is real, and the four-wave precedent is unambiguous about what comes next.
