Google Rolls Out Urgent Fix for Chromecast Outage | Image Source: arstechnica.com
Mountain View, California, March 14, 2025 – Google is launching a critical solution for its second-generation Chromecast and Chromecast Audio devices after users have been frustrated by an unexpected output service. The problem, which emerged on March 9, prevented affected devices from working with Google’s official apps, showing an error “unconnected device.” The root cause? An expired device authentication certificate authority that left streaming hardware a decade ago unable to connect.
What caused the Chromecast problem?
According to several sources, the problem arose from a Google property certificate that expired after ten years of validity. This certificate has been integrated into the firmware of Chromecast (2nd Gen) and Chromecast Audio devices, ensuring secure authentication with Google services. However, when the certificate expired, the affected Chromeecast were suddenly seen as unreliable devices, making them useless for dissemination.
Interestingly, while Google apps could not work, some third-party applications, including VLC Media Player, would have continued to work. This indicated that the problem was specific to Google’s authentication system rather than a complete hardware failure.
How does Google fix the problem?
In response to the widespread interruption, Google confirmed on March 12 that it had identified the root cause and downloaded an update of the firmware on air (OTA) to the affected Chromecast devices. The update migrates devices to a new Google Property Certificate Authority that will remain valid until 2045, potentially giving users another 20 years of functionality.
Google said, “We started solving the problem with Chromecast (2nd gene) and Chromecast Audio devices, which will be completed in the next few days. Users must make sure their device is connected to Wi-Fi to receive the update. »
Why do users reset problems again?
While fixing works well for most users, those who have done factory reset during problem solving find additional obstacles. A factory reset erases all user data, including Wi-Fi identifiers, which makes it impossible for affected Chromes to reconnect to Google servers for OTA update.
According to Tom Hebb, a former software engineer Meta who helped diagnose the problem, “Reset means the device will not have Wi-Fi or Internet connection. The Google Home app seems to run the expired certificate, so you will not be able to press an update. The implementation of this system will require a home update to stop it by forcing the certificate, but this must be a simple solution. “
Google has recognized this problem and is working on an additional update that will allow factory readjustment devices to avoid the expired certificate and install the solution.
What should affected users do?
If you have a Chromecast (2nd Gen) or Chromecast Audio that is currently affected by this problem, here’s what you need to do:
- Ensure your device is plugged in and connected to Wi-Fi to receive the automatic update.
- Avoid performing a factory reset, as this could prevent your Chromecast from getting the fix.
- Monitor Google’s official support forums for further updates on the situation.
For those who have already adjusted a factory, patience is the key. Google is working on a secondary solution to successfully update these devices.
How does this affect other Google devices?
While the current problem only affects Chromecast (2nd Gen) and Chromecast Audio devices, this incident raises concerns about the aging hardware of other Googles. Several Chromecast compatible smart devices, including Chromecast Ultra, Google Home and Google Home Mini, have certificates to expire in 2026 and 2027. If no proactive updates are implemented, similar interruptions may occur in the future.
As Hebb pointed out, “Google will have trouble getting this for everyone, because the devices must be online to receive it. In addition, this means that you will have to build updates for other devices that fall soon.”
Google has not yet confirmed whether preventive updates will be issued for these upcoming expirations.
Despite the opposite, Google was surprisingly fast to develop a solution for a nearly ten-year-old device. The new firmware update would have been compiled only two days after the problem was first identified, demonstrating Google’s continued – though limited – support for inherited hardware.
