Older models of Google’s Chromecast media-streaming sticks remain broken, and independent research suggests a fix could take potentially weeks to materialize.

Second-generation Chromecast and Chromecast Audio devices [1]stopped working on March 9.

Google hasn’t said what went wrong, but an expired device authentication certificate authority is a likely cause. More on that later.

[2]

The internet goliath has not said when the problem will be fixed, either, but did share [3]an alert advising users not to perform a factory reset as that won't help.

[4]

[5]

The Silicon Valley giant also emailed owners of the devices a mea culpa.

"We’re contacting you because of the disruption affecting Chromecast (2nd gen) and Chromecast Audio devices," reads the message forwarded by numerous Register readers.

[6]

"We apologize for the issue and understand your frustration. We are working to roll out a fix as soon as possible and will share updates and guidance on the Nest Community page. We appreciate your patience as we resolve this issue."

Despite our repeated requests for details about the outage, Google told The Register only that it is "aware of an issue" and pointed to the status page for updates.

A fix could take weeks

One knowledgeable chap believes he has identified the problem and concluded that fixing it won't be easy. We reckon he's on the money.

Tom Hebb, a former Meta software engineer and Chromecast [7]hacker , has published a [8]detailed analysis of the issue and suggests a fix could take more than a month to prepare. He's also [9]provided workarounds here for folks to try in the meantime.

We spoke to Hebb, and he says the problem is [10]this expired device authentication certificate authority.

[11]

Chromecasts are basically media players that you plug into equipment, such as a loudspeaker or TV. Apps and such things can connect to your Chromecast and send it, among other data, a URL to fetch media from and output by itself, when you want to play something.

Briefly put, Chromecast devices each contain a cryptographic public-private key pair, installed at the factory and together form a certificate, that can create a digital signature that proves the gadget is a legit Google-made device. That means it's not a knock-off and can be trusted by whatever app and service you're using it with – such as an official Google app – to play some media.

When we say this proves the gadget is legit, we mean the factory-installed certificate used to create the signature proof is itself digitally signed by a Google-owned intermediate certificate authority that chains up to a Google-owned root authority. This allows applications and services, including Google's official apps, to cryptographically verify that the device they're talking to was made by Google: Software can walk back from the signature proof to the web giant.

The affected devices' intermediate authority's 10-year validity expired on March 9, 2025, which means it cannot be used by today's apps to complete this cryptographic process. Software analyzing the chain of trust will reject the whole thing as broken, due to the expired intermediate authority, and that's why folks are seeing error messages about their Chromecast being an "untrusted" device, resulting in the thing being rendered useless.

[12]Google begs owners of crippled Chromecasts not to hit factory reset

[13]Googlers asked if they'd like to bury themselves next to Stadia, Chromecast, DropCam

[14]All y'all love AI, right? Get ready for Gemini in Nest cameras, Google Assistant

[15]It's Google's hardware launch day, and what do we get? A few Pixel phones, Nest kit, and another Chromecast

Note that applications don't have to perform the authenticity check; Google's apps will, and fail, but unofficial clients, such as VLC, are happy to continue working with the gadgets, we're told.

The fix is not simple. It's either going to involve a bit of a hack with updated client apps to accept or workaround the situation, or somehow someone will need to replace all the key pairs shipped with the devices with ones that use a new valid certificate authority. And getting the new keys onto devices will be a pain as, for instance, some have been factory reset and can't be initialized by a Google application because the bundled cert is untrusted, meaning the client software needs to be updated anyway.

Given that the product family has been discontinued, teams will need to be pulled together to address this blunder. And it does appear to be a blunder rather than planned or remotely triggered obsolescence; earlier Chromecasts have a longer certificate validity, of 20 years rather than 10.

"Google will either need to put in over a month of effort to build and test a new Chromecast update to renew the expired certificates, or they will have to coordinate internally between what's left of the Chromecast team, the Android team, the Chrome team, the Google Home team, and iOS app developers to push out new releases, which almost always take several days to build and test," Hebb explained.

"I expect them to do the latter. A server-side fix is not possible."

So either a week or so to rush out app-side updates to tackle the problem, or much longer to fix the problem with replaced certs.

Polish security researcher Maciej Mensfeld also [16]believes the outage is most likely due to an expired device authentication certificate authority. He’s proposed a workaround that has helped some users, at least.

Hebb, meanwhile, warns more certificate authority expiry pain is looming, with the Chromecast Ultra and Google Home running out in March next year, and the Google Home Mini in January 2027.

Please let us know your experiences in the comment section below. ®

Get our [17]Tech Resources



[1] https://www.theregister.com/2025/03/10/google_chromecast_outage/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Z9K62sygvuGLPPoY0qiaywAAAhU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://www.googlenestcommunity.com/t5/Streaming/Regarding-an-issue-with-Chromecast-2nd-gen-and-Chromecast-Audio/td-p/686992

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z9K62sygvuGLPPoY0qiaywAAAhU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z9K62sygvuGLPPoY0qiaywAAAhU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z9K62sygvuGLPPoY0qiaywAAAhU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://xdaforums.com/t/flasher-v1-3-2014-07-07-flashcast-quickly-and-easily-mod-your-chromecast.2452838/

[8] https://old.reddit.com/r/Chromecast/comments/1j8wtxa/heres_why_a_fix_is_taking_so_long/

[9] https://old.reddit.com/r/Chromecast/comments/1j7lhrs/the_chromecast_2s_device_authentication/mgy1a88/

[10] https://old.reddit.com/r/Chromecast/comments/1j7lhrs/the_chromecast_2s_device_authentication/

[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z9K62sygvuGLPPoY0qiaywAAAhU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[12] https://www.theregister.com/2025/03/10/google_chromecast_outage/

[13] https://www.theregister.com/2025/01/31/googles_latest_layoffs_buyout/

[14] https://www.theregister.com/2024/08/06/google_upgrades_nest_cameras_and/

[15] https://www.theregister.com/2020/09/30/google_pixel_5_hold_for_me/

[16] https://mensfeld.pl/2025/03/bringing-your-chromecast-back/

[17] https://whitepapers.theregister.com/