Google Chromecast Users Face 'Untrusted Device' Error – What You Need to Know
Google Chromecast users have reported a widespread issue with their devices displaying an "Untrusted Device" error message. This problem appears to primarily affect older models, including the Chromecast (2nd Gen) and Chromecast Audio. Google has acknowledged the issue and is currently investigating potential fixes.
What’s Causing the Issue?
The "Untrusted Device" message indicates that Chromecast is unable to verify the device’s status, which could be due to outdated firmware or other technical reasons. Given that Google officially ended support for older Chromecast models in August 2024, some users are now questioning whether their devices will continue to function in the future.
What Users Should (and Shouldn’t) Do
If you are experiencing this issue, here are some important steps to take:
✅ Do NOT reset your device – A factory reset may make the issue worse and could prevent Chromecast from functioning altogether. ✅ Ensure your Chromecast and phone are on the same Wi-Fi network – Some connection errors can be resolved by ensuring both devices are properly connected. ✅ Wait for Google’s official response – Since the company has acknowledged the issue, a software fix may be on the way.
Will Older Chromecast Models Stop Working?
Since Google discontinued software updates for older Chromecast models last year, there is concern that these devices may no longer function reliably in the long term. While Google has stated that security updates will continue for newer models, there’s no clear timeline on whether they will extend support to affected older devices.
What’s Next?
Google has yet to provide a firm resolution, but users experiencing this issue should stay tuned for further updates. In the meantime, affected Chromecast owners are encouraged to monitor Google's official support pages and avoid unnecessary troubleshooting steps that could worsen the problem.
If you're experiencing the "Untrusted Device" error, let us know in the comments. Have you found any workarounds? We’d love to hear from you!

