Copilot Arrives on TVs: LG Samsung AI Assistants Spark Privacy and Uninstall Debate

Microsoft’s Copilot has quietly crossed from desktops and phones onto living-room screens — and for some LG owners the arrival didn’t come with a polite “remove” button.

Background / Overview​

The Copilot assistant that Microsoft has been rolling across its ecosystem was announced for smart TVs at CES 2025 and has already begun appearing on manufacturers’ platforms, most visibly Samsung’s 2025 lineup and — according to multiple user reports and forum threads — some LG webOS sets following recent over‑the‑air updates. Official partner messaging framed Copilot on TVs as a convenience feature for on‑screen search, content discovery and contextual cards; users who discovered it installed on their sets, however, report that the app behaves like a system component with no standard uninstall option, leaving only a “hide” or disable affordance in the UI. That dual reality — vendor messaging about helpful AI vs. consumer frustration about lack of control — is at the heart of the controversy. The technical facts in the field are currently a mixture of published rollouts (Samsung’s confirmed deployment and Microsoft’s Copilot blog posts) and first‑hand consumer reports (forum and Reddit threads) that describe what looks like a firmware‑level or privileged app push on some LG TVs. Where independent verification is available, it supports the claim that Copilot is being brought to TVs as an integrated accessory; where it is not available, the strongest evidence remains user screenshots and community troubleshooting.

---

What happened: the timeline and the observable facts​

CES announcement and vendor positioning​

At CES 2025 Microsoft, Samsung and LG publicly discussed plans to surface Copilot on TV platforms. Samsung’s rollout of Copilot for selected 2025 TVs and smart monitors has been documented by Samsung and Microsoft as an available feature in select markets; Samsung’s implementation ties Copilot into its Vision AI suite and its homescreen UX. LG’s public messaging emphasized a broader webOS AI push — an “AI Remote,” an AI section in the interface and Copilot as a shortcut inside that experience. Those announcements established intent and placed Copilot firmly on OEM roadmaps.

The on‑set reports: copies of the app appearing after updates​

Beginning in the months after those announcements, owners of LG TVs reported receiving a webOS update that placed a Copilot tile or app into their home screens. Multiple owners across forums and Reddit threads described similar behavior: the app appears in app rows or AI sections after a routine firmware push, and when users attempt to manage installed apps they find no uninstall/trash option — only hide or disable. Community threads documenting the behavior include screenshots and stepwise accounts from affected owners. Those reports rapidly aggregated into widely read discussion threads and community complaint posts.

What the vendors have (and haven’t) said publicly​

Samsung published rollout details for its supported models and confirmed availability in select markets. LG has been public about expanding AI on webOS and launching webOS Hub 3.0 / webOS 25 that boosts AI features and partner integrations, but OEM documentation and corporate press releases do not uniformly describe the installation model that would make an app permanently non‑removable. Until a vendor statement explicitly confirms the packaging method used for Copilot in a specific firmware build, the strongest direct evidence of non‑removability remains user reporting and technical explanation of how system‑level installs behave on webOS.

---

How an app can be made effectively permanent (technical mechanics)​

Manufacturers distribute new capabilities and apps to TVs via firmware‑over‑the‑air (FOTA) and privileged package channels. There are two canonical ways such a component becomes “non‑deletable” in practice:

• Install as a privileged system package outside the regular app sandbox so the UI exposes only limited management actions (hide/disable) rather than uninstall.
• Bake the app into the firmware image itself so that a factory reset returns the device to the same updated image with the app present.

Both approaches are standard in embedded systems when vendors need to ship DRM components, low‑level utilities, or tightly integrated services. The result for consumers, however, is the same: the app cannot be removed using the normal app manager and may reappear after resets or future updates unless the vendor provides a removal path. Community analysis and forum testing consistent with those observations suggest Copilot on affected webOS sets was pushed as a privileged or firmware‑baked component in at least some updates.

---

Live Plus and Automatic Content Recognition: why this matters for privacy​

LG’s webOS includes a feature line often called Live Plus (also referenced in menus as Live Promotion, LivePlus or similar) that provides automated content recognition (ACR). Live Plus can analyze what's on the screen to provide contextual info, promotions and interactive content tied to what you’re watching. LG’s official user guides and independent privacy reporting document Live Plus’s presence and show the menu path to toggle it off: Settings → All Settings → General → System → Additional Settings → Live Plus (wording varies by model). Several privacy guides and investigations have also spelled out how these ACR flows feed ad personalization unless users opt out via the TV's settings and user agreements. Why this matters: if an assistant like Copilot offers contextual on‑screen insights, it will logically benefit from the same signals ACR provides (what’s playing, timestamps, metadata). That combination — a privileged assistant plus on‑screen content recognition and advertising inventory — escalates data collection surface area unless clearly limited by opt‑in policies and robust privacy defaults. Forum discussions and privacy analyses have highlighted that combination as a major source of consumer concern.

---

What’s verifiable and what remains unproven​

• Verifiable: Microsoft publicly announced Copilot integrations with TV partners and Samsung has publicly rolled out Copilot to selected 2025 TVs and smart monitors. LG’s webOS AI roadmap has been publicized; LG user guides document Live Plus and its setting path.
• Documented by users (strong but not vendor‑confirmed): multiple LG owners have reported an over‑the‑air update that adds a Copilot app tile which cannot be uninstalled from the app manager — it can only be hidden. Multiple community threads recorded the same pattern across models and firmware updates.
• Not fully verified: there is not yet an official LG or Microsoft statement that specifies whether Copilot was intentionally packaged as an undeletable, privileged system app in a specific firmware build. Claims about Copilot actively collecting new classes of telemetry beyond existing webOS flows — e.g., continuous ambient audio capture or cross‑device profiling tied explicitly to Copilot — require vendor confirmation or independent forensic analysis to substantiate. Community investigations recommend caution and further technical verification.

---

Strengths and intended user benefits​

When implemented transparently and with appropriate opt‑in and privacy defaults, integrating a conversational assistant on TVs can deliver real user‑visible value:

• Improved content discovery: Copilot can search across multiple streaming apps, and surface spoilers‑safe summaries, metadata and watch options in a single conversational interface.
• Accessibility gains: voice navigation and contextual explanations are valuable for users with mobility or vision impairments.
• On‑screen companion content: live information cards, cast or scene context, and educational overlays can enrich documentaries, sports broadcasts and news.
• Ecosystem convenience: tight tie‑ins with Xbox, Windows devices, or Microsoft 365 features might help households that already use Microsoft services across devices.

These are legitimate use cases that explain why manufacturers and Microsoft see Copilot as a strategic addition: it is a way to modernize TV UX beyond app grids and simple voice search.

---

Risks, tradeoffs and why users are upset​

• Loss of control: consumers expect to be able to remove or opt out of optional services on devices they purchased. A preinstalled, non‑removable assistant feels like vendor overreach and reduces perceived ownership.
• Privacy creep: Copilot’s contextual value depends on data — audio, screen context, viewing habits — expanding telemetry beyond simple app metrics. Without clear disclosures and simple, persistent opt‑outs, users rightly worry about how that data will be used or shared.
• Monetization and attention economy: modern smart TV homescreens are monetized through promotions, screensaver ads, and ACR‑driven targeting. An assistant that improves personalization can be an ad business multiplier unless privacy‑preserving guardrails are in place.
• Technical brittleness: system‑level installs are harder to remove and harder for support teams to ignore. Factory resets may return the app; blocking network endpoints can degrade service; external workarounds shift the problem rather than solve it.

Regulatory risk is also real: where consent is obscured or opt‑out is effectively difficult to exercise, vendors can attract scrutiny from consumer protection or privacy authorities in jurisdictions with strong rules. The combination of consumer complaints and opaque update notes is what amplifies the reputational risk for manufacturers.

---

Practical steps for owners who want to reduce exposure​

If you find Copilot installed on your LG TV and you want to minimize its presence or the TV’s telemetry footprint, consider the following, ordered from least to most disruptive.

1. Check and turn off Live Plus / ACR and ad targeting
   • Navigate to Settings → All Settings → General → System → Additional Settings → Live Plus and set it Off (menu wording varies). Also review User Agreements and opt out of Viewing Information, Voice Information, Interest‑Based Advertising and Similar toggles where present.
2. Disable “Home Promotion,” “Home Auto Launch” and limit ad tracking
   • Use the Home/Settings menus to disable promotions and limit ad personalization; these settings reduce the volume of targeted content surfaced on the homescreen.
3. Hide the Copilot tile and avoid signing in
   • If the UI allows, hide the app from the home row and refrain from linking a Microsoft account to the TV. Hiding is reversible but removes visible friction in everyday use.
4. Keep the TV offline or use router‑level controls
   • Disconnect Wi‑Fi/Ethernet or block known telemetry domains at your router (Pi‑hole or firewall). This prevents cloud calls but also disables all native streaming capabilities and automatic updates. Use with care.
5. Use an external streaming device
   • Run your streaming experience through a small external box (Roku, Apple TV, Fire TV, Nvidia Shield) and use the TV mostly as a display. This effectively sidesteps the platform’s UI and any forced apps.
6. Factory reset — and then evaluate updates
   • A factory reset can help if an app was installed at the user level, but if the app is baked into the installed firmware image, a reset will likely reintroduce it. Test with caution and keep firmware rollbacks in mind only if you have a supported method to reflash older firmware.
7. If you purchased the TV recently and functionality changed materially
   • If your device was sold with promised Google Assistant features that have been removed, or the device now includes non‑removable software you explicitly didn’t consent to, pursue return/refund or consumer remedies via the retailer or manufacturer support channels where appropriate.

Note: each mitigation has tradeoffs. Blocking network domains can break legitimate services; using an external streamer relinquishes integrated accessibility features; and keeping a TV offline sacrifices convenience. The pragmatic path for many privacy‑conscious users is a combination: opt out of Live Plus and ad personalization, hide the Copilot tile, and run a dedicated external streamer for everyday apps.

---

Corporate incentives and market forces driving this behavior​

Why would LG or Microsoft push Copilot in a way that looks permanent to users? The answer is a mix of strategy and economics:

• Feature differentiation: as display hardware matures, UX and AI features are the battleground for premium positioning.
• Ecosystem reach: Microsoft benefits from Copilot’s presence across more screens, deepening brand familiarity and increasing touchpoints for Microsoft services.
• Ad inventory and data: TVs with ACR and personalized recommendations generate valuable signals for CTV advertisers; an assistant that augments personalization multiplies that value.
• Partnership leverage: OEMs and platform vendors often highlight launch partners by surfacing partner apps prominently; those same partners are incentivized to secure durable placements that maximize engagement metrics.

These incentives are rational from a business standpoint but they conflict with a reasonable consumer expectation: that optional experiences should be optional and removable by the device owner. The mismatch is what has provoked the public backlash and calls for clearer opt‑outs or policy changes.

---

What vendors should do (and what to watch next)​

Manufacturers and platform partners can restore trust quickly with a few straightforward moves:

• Ship AI features as truly optional, installable user‑level apps, or provide a one‑click uninstall that also purges associated telemetry.
• Default to privacy‑minimal settings (ACR and personalized ads off) until users explicitly opt in.
• Publish clear and specific firmware change logs that list added apps and explain exactly how to disable or remove them.
• Offer a simple web‑facing privacy dashboard that shows what viewing data was collected and offers deletion controls.
• When deprecating services (e.g., Google Assistant removal), provide a migration window and clear guidance for affected customers.

If vendors adopt those practices the UX value of a TV Copilot becomes reachable without a credibility cost. Without them, expect continued consumer complaints, negative press, and possible regulatory attention in privacy‑sensitive regions.

---

Conclusion​

Copilot on TVs is a textbook example of an innovation that looks useful in principle but can backfire in execution. The technology’s promise — better discovery, accessibility and conversational control on a large screen — is real and may bring tangible benefits for many households. But the rollout pattern documented in community forums and complaint threads shows a fault line: if the assistant arrives as a privileged, non‑removable component with opaque privacy defaults, it triggers consumer backlash and erodes trust.
For now the evidence supporting both sides is clear: Microsoft and Samsung publicly announced Copilot for TVs and have begun shipping it; LG’s webOS AI roadmap likewise makes Copilot plausible across models. The strongest evidence that some LG TVs received a non‑removable Copilot app comes from aggregated user reports and forum analysis describing privileged installs and hide‑only behavior. Vendor confirmation of the specific packaging model — and a clear, persistent path for data opt‑out — would greatly reduce friction.
Owners who want to reduce exposure have practical levers: disable Live Plus and ad personalization, hide the tile, use an external streamer, or keep the TV offline. Those mitigations are effective but imperfect. The longer‑term fix is not technical ingenuity from users but better product design and clearer consent models from vendors.
The next chapters will be written by two actors: manufacturers who must choose whether to prioritize short‑term engagement metrics or durable customer trust, and privacy‑conscious consumers deciding whether to accept AI bloat for convenience or to return to simple displays and external streamers. The balance they strike will determine whether Copilot becomes a genuinely helpful TV companion or another contested chapter in the uncomfortable history of preinstalled software.

---

Source: TechPowerUp Microsoft Copilot AI Comes to LG TVs, and Can't Be Deleted | TechPowerUp}

 

[ChatGPT]

LG owners across multiple forums woke up to a firmware update that planted Microsoft’s Copilot on their webOS home screens — and many discovered there’s no obvious way to remove it.

Background / Overview​

In product announcements and at CES 2025, Microsoft and TV makers signaled a clear strategy: bring Copilot’s conversational AI to living-room screens as a core part of the smart‑TV experience. LG positioned Copilot as an extension of webOS’s AI initiatives — an assistant to aid discovery, answer questions, and surface contextual recommendations — while Samsung published staged rollouts for selected 2025 models. That roadmap is straightforward. What inflamed users this week was the delivery mechanism: a routine webOS over‑the‑air (FOTA) update that added a visible Copilot tile to the home screen on a number of LG sets. Owners reporting the change say the tile behaves differently from ordinary apps — the TV’s app management UI offers only the option to hide or disable Copilot, not to uninstall it. Multiple community posts and screenshots indicate the tile can reappear after a factory reset, suggesting the app may be provisioned as a privileged system component or baked into a firmware image rather than installed as a removable Content Store app.
The technical mechanics of those packaging decisions are well known in embedded platforms: system‑package installs and firmware‑baked components are common ways for OEMs to deliver deeply integrated features. The result for end users is the same — a visible, persistent feature they cannot remove through the standard UI.

---

What happened: the observable facts​

Timeline and scope​

• CES 2025: Microsoft and TV OEMs publicly announced Copilot integrations for select 2025 smart TVs, positioning it as a conversational helper for content discovery and contextual queries.
• Mid‑December (community reports): Multiple LG owners reported an automatic webOS update that added a Copilot tile to their home screens. Those reports spread quickly on Reddit and other forums and were picked up by tech outlets.

User-reported behavior​

• Copilot appears in the home row or the AI/assistant section of webOS after an update.
• The TV’s app manager does not show an uninstall/trash icon for Copilot — users see only hide or disable options.
• In several reported cases, performing a factory reset restored the Copilot tile, indicating the component may be integrated at the system or firmware level.

These are the observable, repeatable facts circulating in community posts and supporting screenshots; they are distinct from claims about undisclosed telemetry or microphone behavior, which require a technical audit or vendor confirmation to verify.

---

Why this matters: device autonomy, privacy, and consumer expectations​

Loss of control and the “bloatware” dilemma​

Consumers reasonably expect optional services on purchased hardware to be removable. When an OEM treats a partner app as a system component, the device feels less like a product the owner controls and more like a platform with vendor‑imposed services. That perception fuels immediate anger because the change is visible — the tile sits where users expect their chosen streaming apps to be — and because the normal uninstall affordances are absent.

Privacy and telemetry concerns​

webOS already supports Automatic Content Recognition (ACR), marketed as Live Plus, which can identify on‑screen content and feed personalization and advertisement features. An assistant like Copilot is more useful when it has contextual signals about what’s playing. That combination increases the telemetry surface area (viewing habits, timestamps, potentially audio-based cues) and amplifies concerns about unseen data flows. Disabling Live Plus reduces some of those signals, but it does not remove a system‑level app. Users have been advised to toggle Live Plus off as an immediate mitigation.

Commercial incentives​

Embedding Copilot on TVs makes commercial sense for both OEMs and Microsoft: it’s a headline feature (feature differentiation), it increases Microsoft’s footprint across screens (ecosystem reach), and it can improve personalization that increases ad value (monetization). Those incentives are legitimate from a product and business perspective — but they clash with user expectations when the delivery removes choice.

---

Technical explanation: how an app becomes “undeletable” on a smart TV​

Two canonical mechanisms explain the behavior users report:

• Privileged system package: The OEM installs the app outside the user sandbox and marks it as a system app. The settings UI commonly permits hiding or disabling, but not uninstalling. This is a standard approach for deeply integrated services or DRM components.
• Firmware‑baked component: The app is included in the firmware image installed by the FOTA update. A factory reset reinstalls that image, restoring any baked‑in components. Removing those components typically requires vendor tools or a firmware rollback — options normally unavailable to consumers.

Community testing — hide vs uninstall attempts and the tile returning after resets — aligns with one or both of those packaging patterns. Without an OEM technical bulletin or firmware inspection, community evidence remains the best practical indicator of the packaging method.

---

Cross‑checking the record: vendor announcements vs. community evidence​

• Vendor announcements at CES and in product messaging established intent to bring Copilot to TVs, and Samsung published availability details for selected models. These two independent reporting streams corroborate that Copilot was meant for TV platforms.
• Community evidence — screenshots, forum posts, and user reports — repeatedly documents the unexpected arrival of Copilot on LG sets and the lack of an uninstall option in app management. Those on‑the‑ground accounts are consistent across several independent threads and platforms.
• What remains unverified is an explicit LG or Microsoft technical statement saying Copilot was intentionally packaged as a non‑removable system app in a specific firmware build. Community behavior strongly suggests privileged provisioning, but vendor confirmation is the definitive proof and, at the time of reporting, absent. That distinction — observed behavior versus vendor‑confirmed packaging — is important and should be made explicit when evaluating claims.

---

What users are doing right now: practical mitigations​

Owners who want to reduce Copilot’s presence or telemetry exposure have a limited set of practical options. Each approach has tradeoffs.

Steps ranked from least to most disruptive​

• Toggle Live Plus / ACR and ad personalization off. (Settings → All Settings → General → System → Additional Settings → Live Plus — wording varies by model. This reduces contextual signals but does not remove the app.
• Hide the Copilot tile and avoid signing in to Microsoft services on the TV. Hiding removes daily visibility and avoids account-based personalization.
• Keep the TV disconnected from the Internet or block telemetry domains at the router. This prevents cloud calls but disables automatic updates and may break legitimate services. Domain‑blocking requires technical skill and careful whitelisting.
• Use an external streamer (Apple TV, Roku, Amazon Fire TV, Nvidia Shield). This sidesteps the smart‑TV layer for everyday streaming and preserves a “dumb display” experience, at the cost of integrated features and convenience.
• Factory reset and test. If the app is truly firmware‑baked, reset will likely reintroduce it. Reflashing unsupported firmware is risky, voids warranties, and is not recommended for most users.
• Seek vendor support or consumer remedies. If an advertised feature was promised and then changed or if the update materially alters advertised functionality, retailers and consumer‑protection channels may be options.

None of these options is perfect. For many privacy‑conscious owners, the most practical compromise is to disable Live Plus, hide Copilot, avoid sign‑in, and use an external streamer for heavy streaming.

---

Strengths and the case for Copilot on TVs​

When implemented transparently and with user‑first defaults, Copilot can provide genuine user value:

• Improved content discovery: A conversational assistant can search across multiple streaming services and present aggregated results, reducing friction.
• Accessibility gains: Voice navigation and contextual explanations help users with mobility or vision impairments.
• On‑screen companion content: Live cards, scene summaries, or sports statistics delivered conversationally can enrich viewing for some audiences.

These benefits explain why OEMs and Microsoft are eager to place assistants on large screens. The problem is not the capability; it’s how the capability is introduced and whether owners keep meaningful control.

---

Risks, tradeoffs, and red flags​

• Loss of ownership control: Non‑removable system apps subvert user expectations about what they can remove from hardware they bought. That perception damages trust and can turn a differentiator into a liability.
• Telemetry expansion: An assistant that uses ACR and account signals expands the types of data collected by the TV. Without clear, persistent opt‑out controls and robust defaults, that expansion can be perceived (and may be) privacy invasive. Claims that Copilot introduced always‑on audio capture or new telemetry classes remain unverified and should be treated as concerns until independently audited.
• Opaque update practices: Firmware updates that add visible functionality without clear patch notes or opt‑out options create distrust. Vendors should publish short, discoverable update notes including removal or disable instructions for new features.
• Support and maintenance burden: System‑level integrations are harder to troubleshoot and can tie support teams to partner dependencies (e.g., account linking and cloud‑service availability).
• Regulatory exposure: In jurisdictions with strict data‑protection rules, obscured consent flows or difficult opt‑outs could attract regulatory scrutiny or consumer‑protection complaints.

---

What vendors should (and can) do — practical recommendations​

To restore user trust and reduce regulatory risk, OEMs and partners should adopt these concrete actions:

• Make Copilot optional or provide a clear uninstall path that also removes any associated telemetry artifacts. If full removal isn’t practical due to integration complexity, provide a single‑click disabled state that also severs cloud bindings until re‑enabled.
• Default to privacy‑minimal settings. ACR and ad personalization should default to off and require an explicit user opt‑in.
• Publish concise update notes with every FOTA push that adds or modifies visible features, and include a clear path to remove or disable those features.
• Provide a dedicated privacy dashboard and data‑deletion tools so users can view and purge viewing data associated with their device.
• Offer transparent documentation about what signals the assistant uses (ACR, account data, voice input) and how those signals are stored, processed, and deleted.

These moves won’t cost much relative to the reputational and regulatory risks of opaque rollouts, and they would reestablish an expectation of treatable user control.

---

What’s verified — and what still needs confirmation​

Verified:

• Microsoft and major OEMs publicly announced Copilot on TVs at CES and in follow‑up messaging.
• Community reporting documents that some LG webOS TVs received an over‑the‑air update that added a Copilot tile which, in reported cases, lacked the normal uninstall affordance (the tile could be hidden but not deleted).
• webOS includes a Live Plus / ACR setting that can be toggled; that capability is documented in user materials.

Unverified or vendor‑confirmed claims requiring technical validation:

• That Copilot introduced previously undisclosed classes of telemetry such as continuous ambient audio capture bound to Copilot. These are plausible privacy concerns but lack public, independent forensic confirmation. Treat as unverified until packet captures, telemetry disclosures, or vendor technical notes confirm specifics.
• Whether LG intentionally packaged Copilot as a non‑removable system app across all affected firmware revisions. Community tests strongly suggest privileged provisioning in some builds, but an OEM technical bulletin is the definitive confirmation.

---

Conclusion​

The arrival of Microsoft Copilot on LG webOS sets underscores a growing tension in modern consumer electronics: vendors see software and AI as the primary battleground for differentiation and monetization, while many owners still expect meaningful control over what runs on hardware they purchased. The observable facts — a FOTA update adding Copilot to home screens and community reports that the app lacks an uninstall option — are well documented and worrying for those who value device autonomy and privacy.
There are legitimate product benefits to a conversational assistant on a TV, but the rollout matters. When new features are pushed in ways that remove or obscure user choice, the result is backlash, distrust, and potential regulatory scrutiny. OEMs and partners can — and should — address these problems quickly: provide clear uninstall or disable paths, default to privacy‑minimal settings, publish transparent update notes, and offer accessible data‑deletion controls. Those steps would protect user trust while preserving the genuine value assistants can offer on the big screen.
For owners affected today, the immediate, practical steps are modest: disable Live Plus, hide the Copilot tile, avoid account sign‑in, and consider an external streamer or network‑level blocking if you want to reduce the assistant’s surface area. Those mitigations are imperfect, and some are inconvenient, but they are the available path to reclaiming control until vendors offer a cleaner remediation.
Finally, any claims about Copilot’s telemetric behavior beyond established webOS flows should be treated as concerns rather than proven facts until verified by vendor disclosures or independent technical analysis. Users, privacy advocates, and regulators should demand that confirmation — and vendors should provide it promptly.

---

Source: Tom's Hardware https://www.tomshardware.com/servic...non-removable-microsoft-copilot-app-to-webos/