First-Gen Chromecast Not Working in 2026: Why a Fix Is Unlikely

Reports of first-gen Chromecast devices disappearing as a cast target in major apps have accelerated this week, and the pattern is unusual enough that observers are calling it something more than normal hardware aging. The first-gen Chromecast not working reports have clustered in a Reddit thread where multiple owners described the same breakage occurring at roughly the same time. Google has not publicly commented. According to 9to5Google, any response from the company would likely point back to the 2023 end-of-life notice which warned users only that they "may notice a degradation in performance," not that apps would stop recognizing their device.

The EOL notice ended firmware updates for the 2013 dongle. What it didn't address, and what Google hasn't explained, is what happens when the infrastructure beneath those apps keeps moving while the device stays frozen.

Why is my first-gen Chromecast not working? What the reports actually show

Start with what's confirmed. YouTube and HBO Max are no longer showing the first-gen Chromecast as a cast target for some users. Disney+ and Spotify continue working on the same hardware. Peacock has explicitly dropped support for the device a clean, documented app-level decision, 9to5Google notes. Isolated failure reports had been building for weeks. The Reddit thread shifted that from a trickle to a cluster.

What's still unknown is why. No cause has been confirmed, Google hasn't commented, and the available reporting doesn't support a definitive explanation.

What observers suspect and this is informed inference, not confirmed fact is that something changed at a shared infrastructure level. The normal pattern of aging hardware is gradual: individual apps raise their minimum requirements, older devices fall off one at a time, with announcements. That's not what's happening here. As 9to5Google points out, it's odd that multiple apps stopped working simultaneously and inconsistently, with no announced changes from any of the services involved. YouTube and HBO Max gone; Disney+ and Spotify still working. On identical hardware. That pattern fits a shared dependency failing beneath some apps but not others not a coordinated round of compatibility decisions.

The 2025 outage shows what that infrastructure looks like

In March 2025, second-gen Chromecasts and Chromecast Audio units stopped working entirely. Not gradually, not app by app. All reported users of those models saw a uniform "Untrusted device: couldn't be verified" error appear at once, 9to5Google reported at the time.

The likely cause was identified by independent analysis, not Google. Tom Hebb, a former Meta software engineer, concluded that an intermediate device authentication certificate embedded in those 2015-era devices carried a 10-year validity window that closed on March 9, 2025 the exact date failures began, according to The Register's reporting on his analysis. With that certificate expired, sender devices could no longer verify the Chromecast as Google-approved. Casting was blocked entirely. Hebb concluded that a server-side fix was not possible, since the keys live in read-only firmware; resolving it required pushing a firmware update directly to the device.

Google's response was direct and fast. The company emailed owners, posted community updates, and explicitly warned users not to factory-reset their devices. That warning mattered: users who reset during the outage found themselves unable to complete setup at all, because the expired keys also blocked the configuration process, according to AFTVnews. Google confirmed the outage was a bug rather than intentional deprecation, 9to5Google reported, and shipped firmware versions 1.56.467165 and 1.56.467166 within days. Second-gen devices and Chromecast Audio have worked normally since, 9to5Google notes.

The 2025 incident is not a direct explanation for what's happening to first-gen devices now. The current failures are partial and app-dependent rather than a uniform outage, and no "Untrusted device" error has surfaced. The relevance is what it documents: Chromecast functionality depends on authentication infrastructure that can expire abruptly, without warning, and that fixing it requires a firmware push. The original Chromecast stopped receiving firmware updates in 2023. When second-gen devices broke in 2025, Google was still within its support window and acted accordingly. The first-gen device has no equivalent path.

What first-gen owners should know right now

If your original Chromecast is still working in some apps, that could change without notice. There is no published fix path, and 9to5Google reports no indication Google plans to provide one.

On factory resets: the 2025 second-gen outage showed that resetting can actively worsen the situation. Users who reset their devices during that incident found themselves unable to complete setup, because the expired authentication keys also blocked reconfiguration, per AFTVnews. The root cause of the current first-gen failures hasn't been confirmed, so direct comparison carries some uncertainty but if authentication or protocol dependencies are involved, a reset is unlikely to help and could leave the device in a worse state than partial functionality.

Google's silence on the current failures is itself useful information. The contrast with 2025 is sharp: when second-gen devices broke, Google emailed users, warned against resets, confirmed a bug, and patched within days. When first-gen Chromecast failures surface in 2026, there's been no comment. That's not negligence so much as the logical endpoint of a support policy. "End of updates" doesn't mean the device remains stable until the hardware physically gives out. It means Google is no longer responsible for fixing what breaks beneath it including authentication infrastructure, protocol dependencies, and the compatibility layers apps rely on to recognize the device.

What comes next, and which other devices may be at risk

The first-gen Chromecast situation also points forward. Independent analysis by Hebb flagged that the Chromecast Ultra and first-generation Google Home face their own authentication certificate expiry timelines in the coming period, according to The Register. Those devices are presumably still within Google's support window. Whether the company addresses those expiries proactively before failure or responds only after users report breakage will clarify whether the swift 2025 response reflected a broader commitment or simply what the support calendar required at the time.

The current first-gen failures remain unexplained. What isn't in question is that the breakage is unusual, the pattern doesn't fit normal app attrition, the device has no update path, and Google has said nothing. Those four facts, taken together, are probably the most accurate picture of where this ends.