lamar

What nice news. I also received Internet Protection Module #1376 (build Aug/06) on the regular update channel, so the long awaited #1375 seems to remain unreleased forever. It was a great honor for me to participate in this conversation. Best wishes to all.

Thank You ESET team. Whatever you did finally fixed the issue with Chromecast not working. 
Today is the first time in almost a month that I can view movies from my browser again. I'm so happy, as I felt uncomfortable trying to do those things about changing those HTTPS Ports and all.
So once again, Thank you Very Much. 

These workarounds are easy for most of us here, but please see that there are a lot of customers who simply does not dare to make any modifications in the default settings since they are afraid of causing an untraceable or even irreversible mistake by mistyping or misclicking while they are performing such technical steps they do not understand clearly. Therefore impatience is a natural reaction of them. On the other hand I agree that unproven hurrying would not be a good way as well. Both standpoints are reasonable.

Not so easy as it sounds. Valid only if you watch only free stuff  via your Chromecast. If you pay US$ 20-50 per month for online movie channels, then three weeks of black screen due to another paid product's malfunction makes you impatient relatively fast. That is the natural behavior of customers.

Right. But when you disable pre-release updates, you immediately fall back to #1372.2. So at this moment the official fix is still unavailable for the average user. And well, average user is getting impatient according to @Vader's post.

Internet Protection Module #1375 is rolled out on the pre-release update channel, and it works fine for me with the default Eset settings. There is no more need of  whitelisting port 8009. Hopefully it will be rolled out soon on the  regular update channel as well.

Internet Protection Module #1375 is rolled out on the pre-release update channel, and it works fine for me with the default Eset settings. There is no more need of  whitelisting port 8009. Hopefully it will be rolled out soon on the  regular update channel as well.

I truly hope the bugfix will come soon. However you really do not need to wait for that. Do the following step by step:
01. Open Eset console | 02. Click "Setup" | 03. Click "Advanced setup" | 04. Click "Web and email" | 05. Click " Web access protection" | 06. click "Web protocols" | 07. Now you are on the right place | 08. Focus on "Ports used by HTTPS protocol" | 09. You have to see the text "443, 0-65535" in the input field. | 10. Replace the text with "443, 0-8008, 8010-65535" (of course, without quotes) (you can copy-paste) | 11. Press "OK" | 12. If Windows asks for permission, press "Yes" | 13. Close ALL instances of Chrome | 14. Reopen Chrome | 15. Connect to your Chromecast | 16. Success!
After the bugfix will have been rolled out, you can reset the original text you modified.
 

I truly hope the bugfix will come soon. However you really do not need to wait for that. Do the following step by step:
01. Open Eset console | 02. Click "Setup" | 03. Click "Advanced setup" | 04. Click "Web and email" | 05. Click " Web access protection" | 06. click "Web protocols" | 07. Now you are on the right place | 08. Focus on "Ports used by HTTPS protocol" | 09. You have to see the text "443, 0-65535" in the input field. | 10. Replace the text with "443, 0-8008, 8010-65535" (of course, without quotes) (you can copy-paste) | 11. Press "OK" | 12. If Windows asks for permission, press "Yes" | 13. Close ALL instances of Chrome | 14. Reopen Chrome | 15. Connect to your Chromecast | 16. Success!
After the bugfix will have been rolled out, you can reset the original text you modified.
 

You are right from the technical point of view. From the valued customer's point of view the phrase "bug" is simply a synonym to ... "problem" ...  "issue" ... "unexpected behavior" ... etc.
I would rather highlight the fact that Eset did not belittle the importance of this question, and did promise an urgent solution.

Gentlemen, I have just received a private message from an Eset employee, that investigating the logs I sent they localized the bug, and a fix will be rolled out soon. Until that, please use one of the temporary workarounds mentioned here in the forum thread.