Blackbox88

But for that there are two good workarounds. Also almost every paid service has a app which is already installed on TV or can be installed on tablets/phones. I do agree it is an inconvenience but there are ways around it. If there are no workarounds, agree I also had some impatience

Well everybody these days are impatient not only with SW updates, see road rage, socialisation etc. Same happens with my company, unfortunately not everything always goes as fast as some customers want, sometimes releasing new SW just takes time to smoke test it. Also why the impatiens there are multiple work arounds which are relatively safe. Just do any of the 2 good work arounds and be patient till the real roll out.

I just switched to pre-release and it automatically updated and went to the #1375: Just checked the chromecast is still visable after the update and returning the TLS/SSL range to the full range.

Oke makes sense so as soon as the update is roll out we need to make sure to revert the white listing of port 8009

That is good news! After the update do we have to revert the HTTP port selection or will it automatically be done by installing the update?

Can you screenshot the range of ports you exclude? Here it is still working.

Offcourse every exeception will leave you computer vulnerable however this wasn't in the previous version of ESET, which didn't gave any issues, also as you only open one port the risk from my point of view is still low. Have a good back up of your computer stored somewhere and you are good. I am running with the workaround and all is going good

Work around for everybody who doesn't want to read the whole thread! Please also upvote it! (On page 4) All credits go to Lamar!

Thank you Marcos for the update!

hahahaha so true

Turn Windows Defender OFF haha Uhmm sounds like a great advice! A bit like white listing Chrome.exe

All credits got to @lamar So should look like this:

Let us know if you need help

Same here! Only white listed port 8009 and chromecast works like a charm ' Did sent Taradise a PM hope she didn't whitelist Chrome.exe

As Merriam Webster defines the word bug: : an unexpected defect, fault, flaw, or imperfection https://www.merriam-webster.com/dictionary/bug

No VLC always worked even when the 8009 was still in the scanning range. Itman explained that VLC most likely uses a different method of communication:

I think you talked after me to the same person, as I went to the same extensions canary etc. She is true it is because of a change within ESET. Do you know which ESET program you have on your tablet (Mobile Security or Smart Security, etc)? Is the tablet and Andriod or an windows tablet? Maybe we can help you fix it so you can still enjoy your youtube via tablet while waiting for the full fix from ESET.

Ahh oke makes sense.

It seems to be using 8010: Current settings I have in ESET:

@itman how do i check which port it is using when redering with VLC to Chromecast?

Damm i am happy i found this thread. I tried a lot myself spent a lot of time talking to chromecast support, Videostream support unfortunatly nothing helped untill i did a full reinstall of Eset and Chrome. After that it all worked and I was happy as i could be, untill a few days later after mine vacation I tried to stream my rafting trips using videostream and we were back to the old "cant find the device trouble" Luckily with this thread there is new hope. The on thing which is strange for me is that Chrome + Videostream (plugin for chrome) both don't see the device but when I use rendering from VLC media player it does see chromecast and works fine. Maybe it is good to investigate for some one with more skills then me, how VLC and chromecast commincate. They are able to commincate with all the SSL/TLS scanning on.