10-02-2021 01:48 PM
This is Chrome on PC specific. I am connected using my Pixel and Android to the TV Chromecast but get this message when I try to connect on my Surface using Chrome ver: Version 94.0.4606.71 (Official Build) (64-bit) on a Surface PC running Version 10.0.19042 Build 19042
This connection has work previously. I believe it is the latest Chrome update that broke the connection.
I have updated Chrome and relaunched. I have rebooted the Surface.
I have two Chromecast adapters neither of which can be seen my the Chrome on my Surface but both available on my Pixel. I have restarted the adapter. This appears to be specific to the latest version of Chrome.
10-02-2021 03:44 PM
Sounds like a TV specific error, quick search found that people who have this issue Went into the TV's setting, under the apps section there is an option to "view system apps.", choose "Chromecast Built In" and chose to uninstall all updates and restore to the factory version.
10-02-2021 04:11 PM
I saw that too. None of the people who did that had a Roku. I don't have a "view system apps" section of my Roku setup that I could find.
The difference is that mine is working, just not with the Surface Chrome. It works fine with Android.
10-02-2021 04:19 PM
Can you check your system date and time on your surface ? That has also been known to cause issues
10-02-2021 05:12 PM
Yeah, did that.
10-02-2021 05:27 PM
Really odd I can't replicate this on our surface laptop. Does it happen if you go YouTube and try to cast a video ? Not from the crome bar but from the video itself ?
10-03-2021 07:19 AM
The problem is fixed without a solution. I did bring up Youtube this morning and it did connect but I should have tested to see if the problem still existed before I did that. Apparently it had cleared as it is working correctly now with everything (OS and Chrome updates the same) exactly as it was. It just magically works now.
So nothing was learned. But I'll at least test it with YouTube should it happen again.
Thanks for the input.
10-07-2021 09:08 AM
Hey there!
I'm glad the issue was resolved, but it's strange that nothing seems to have changed. For now, I'm locking the thread, however, feel free to make a new thread if you run into this issue again, so we can take another look into it.
Thank you for your help, Ashepherdson!
Best regards,
Jeran