Videostream does not start after updating to Windows 10 1903
Hello, I recently update my Windows Home to version 1903; after that, Videostream does not start anymore.
It worked as expected before, but now I see the processes start (Videostream.exe, videostream-native.exe), but they close and the browser opens on an error page.
I haven't been able to find any useful log.
Can you help?
fueleh last edited by
same 2 me cant use videostream at all on windows 10 1903, the ui dont load at all in chrome, just standard cannot find page error in chrome.
Re: Videostream does not start after updating to Windows 10 1903
The same happens to me!
I contacted videostream yesterday and they told me that this is a known bug and that they are working on a solution.
I hope they will come up with something soon!!
There is nothing we can do at the moment, except from waiting or using another application of course!
damo666smith last edited by
I'm glad it's not just me. This has been driving me crazy. Other apps aren't working after updating to Windows 1903. I'm restoring back to a previous version and hope that works for now.
loconz last edited by
i cant believe there has been no response from videostream... looks like that the end....
Hopefully not. I bought lifetime premium :D
I'm pretty sure they are working on a fix.
@Rockschuppen I am also a lifetime member. I also contacted them yesterday, for the third time, but still, no answer. Kind of strange since they answered quite fast the two previous times.
Anyway, I suggest we keep on "bothering" them, if you have not sent an email yet, please let them know that you are facing this problem and you want it solved soon (mail firstname.lastname@example.org)
Let's wait and see.
In the mean time, what are you doing as an alternative solution for streaming your content to chromecast?
Rockschuppen last edited by Rockschuppen
There are some alternatives:
But in my opinion only Videostream was the only good way to stream video media from PC to Chromecast.
In the meantime I will use an external SSD as my TV supports several codecs and drives. Hope they can fix it soon. Don't want to end up with a solution like building a NAS station.
Today it's working again.
Today, it stopped working again -.-
Thanks for the heads up! I was already using Airflow, it works like a charm, most of the time!!
I just tried the "chrome store" videostream app. It is working, but the subs are not loading, still...
What can I say...!
Yesterday I just tried to start it and the browser opened has expected... I hope this is permanent now!
arangaran last edited by
@pdario i just tried it today and no go, anyone got a solution for this?
Mick Fox last edited by
FOR THOSE HAVING PROBLEMS:
Try reinstalling Videostream for me? First go to Chrome://extensions and remove Videostream.
Then, reboot your computer, after you do that, download it again from here: https://chrome.google.com/webstore/detail/videostream-for-google-ch/cnciopoikihiagdjbjpnocolokfelagl?hl=en
Finally, pin it to your desktop.
Let me know if this solves your problem!
Works. THX for the help. I uninstalled desktop version, rebooted and then installed chrome extension and ALL good now.
Wulfgang last edited by
Was using the VS desktop app but I also got the "localhost:5557 ERR_CONNECTION_REFUSED" error after the latest windows update. I tried the github "videostream port fix", disabling firewall, disabling anti-virus, uninstalling / reinstalling VS and Chrome, running the installer in Win7 compatibility mode - what finally worked for me was abandoning the desktop app and installing the VS app in Chrome from the Chrome Store.
@pdario Nope! Yesterday Videostream broke again! What can I do??
wrapperNo1 last edited by
It works again now. Not sure how..
wrapperNo1 last edited by
@wrapperNo1 Not anymore!! Support sucks!
metroieud last edited by
Win 1903, Chrome 76+.
I solved the connection problem by using the tool VideostreamNetworkRepair.exe
But, network must first be set to Private !
I didn't pay attention, mine was set to Public and the rules created by the tool in the firewall only applied to public network.
After I manually changed it to Private, it works flawlessly.
Hope it helps !