Over the weekend, users of Google's Chromecast (2nd gen) and Chromecast Audio found themselves unable to cast any audio or video content, sparking concerns about potential device obsolescence. Reports began surfacing on March 9, 2025, detailing difficulties when attempting to use these devices, leading to widespread frustration among users.
By March 10, 2025, confusion reigned as many users encountered the error message, "Untrusted device: [name] couldn't be verified. This could be caused by outdated device firmware," through various applications such as YouTube. This alarming message effectively rendered the devices non-operational, preventing users from casting content or accessing their devices through the Google Home app.
Google has since confirmed it is aware of the issue impacting Chromecast v2 and Chromecast Audio and is working toward resolving it. "We're aware of the issue impacting Chromecast 2nd gen and Chromecast Audio devices and are working on a fix," stated Google on March 10. The devices have been functional for many years since their release at the same event back in September 2015, but the recent bug poses significant questions concerning their future usability.
Newer models, such as the Chromecast with Google TV and Chromecast Ultra, are not affected by this outage. The reports, originating from users globally, suggest this disruption is rooted on Google's end, primarily due to what many believe is the expiration of the devices' security certificates. A Redditor identified the precise cause, noting, "The intermediate certificate authority for the Chromecasts (2nd gen) expired on March 9, 2025," and this expired authority results in these older devices being unable to securely connect with Google's systems.
The problem escalated as it became clear standard troubleshooting methods—like restarting or factory resetting the devices—proved ineffective and left the users even more frustrated. Google has reiterated its stance on factory resets, urging users not to reset their devices, as it would not rectify the underlying certificate issue. "Do not factory reset your device – we will keep you all updated when the fix rolls out. If you have already factory reset your device, we will provide instructions to set your device back up as soon as possible," Google announced via the Google Nest community.
Despite the tech giant's warnings, users continued seeking solutions, often venting their frustrations over social media and Reddit threads dedicated to Chromecast. Many suggested alternative routes to working around the issue, including manually resetting the Chromecast and then setting their phones’ date to before March 9, 2025, to re-authorize the devices through the Google Home app. This workaround has yielded mixed results; some managed to regain functionality, yet many others found themselves still trapped within the chaos of the outage.
The frustration reached new heights as the outage extended across borders, leaving users worldwide unable to utilize their streaming devices. The disappointment was palpable, as many depended on the Chromecast for home entertainment. Comments on various tech blogs reflected on the growing fears about the lack of continued support for the older devices, raise eyebrows on whether such outages will become common as Google seems to slowly phase out older technologies for newer versions, including the Google TV Streamer.
At this time, Google has not established any timeline for when the fix will be rolled out. Repairing trust with the substantial user base will take time, especially when videos and music streaming are at the center of many home entertainment systems. For both casual users and tech enthusiasts, the dilemma poses questions about reliance on certain devices and how susceptible they are to sudden outages due to certificate authorities.
Until then, the community continues to support one another through shared frustrations and suggested remedies, reaffirming the notion of collaboration among technology users. The incident serves as another reminder of the importance of maintaining updated authentication protocols for connected devices, and the lessons learned will likely steer future designs and policies surrounding user support.
With Google working on resolving the issue, users are left with the prevailing hope for swift solutions, the urgency to protect their cherished devices, and securing their investment—and above all, restoring functionality to their homes.