Vader

I fully support this comment as well - same issue and if this did not exist in the previous version means, something has been missed during the testing or planning the update and must be resolved. We pay for the service and expect the product to function correctly. Responsibility altering network protocols and potentially leaving our machines vulnerable is not the way it works. Chromecast is a widely used product so I epxect this to be fixed pretty quick.