Win 10 - v1909
Hey All,
I've search the internet long & hard for answers, trying different things & solutions others have had success with; However; no single suggestion worked permanently, until now....
So, after much testing, I thought i'd share what worked for me.
To start with, make sure your Network is set to Private.
(if not, Set it & then Reboot)
so, If you have any versions of videostream, Uninstall them (including removing Chrome extensions etc)
Reboot
Download Videostream (0.3.6) from the VS website
Install/Run Setup (in Win 8 compatability mode)
After Install, Navigate to:
C:\Users\ 'Your Folder' \AppData\Local\Videostream\videostream.exe - Set to run in Win 8 compatability mode
C:\Users\ 'Your Folder' \AppData\Local\Videostream\app-0.3.6\videostream.exe - Set to run in Win 8 compatability mode
Reboot
(I'm currently using Windows Defender Firewall after a ground up software rebuild)
Delete all Inbound firewall rules regarding videostream
Reboot
Open Windows Firewall with Advanced Security > Inbound Rules
create the following 3x Firewall rules
C:\Users\ 'Your Folder' \AppData\Local\Videostream\videostream.exe - Private Network Only / TCP / work on specific ports: Range - 5556-5558
C:\Users\ 'Your Folder' \AppData\Local\Videostream\app-0.3.6\videostream.exe - Private Network Only / TCP / work on specific ports: Range - 5556-5558
C:\Users\ 'Your Folder' \AppData\Local\Videostream\app-0.3.6\videostream-native\videostream-native.exe - Private Network Only / TCP / Port set to 'Any'
Reboot
While the pc is rebooting, go unplug the Chromecast from the tv & the power supply.
Reconnect the Chromecast to the Tv, then connect the power to the Chromecast - wait a couple of minutes for it to have rebooted.
Launch Videostream
I'm currently on day 4 & it's still working...
I'm gonna email the boys at VS to get diffinitives on these firewall rules. I've already sent one, but they're not very good at responding.
Hope that helps someone
Update: 29th Feb, '20
I ran a couple of Windows Updates last night (28th Feb, '20) - 1x build update & 1x .net update... it's still working...
Spoke too soon... later that afternoon... back to 5557 error
Even later in the afternoon:
Reboots didn't work...
CMD (as administrator)
- ipconfig /flushdns >Press Enter
Turn Private Firewall Off > OK > Warning Message for Firewall to turn On again > Click that... Firewall turns back on > Reboot
Working Again
UPDATE: 09.03.20
OK, with my last testing... I found that Videostream would randomly work, or more the case, not work.
A simple reboot sometimes made it work or stop working. I tried all sorts, logging the changes etc.
In the end, The answer was to uninstall & delete all files regarding Videostream.
So,
Ensure Chrome is already installed.
I already had 3x Firewall Rules created prior to the following actions:
a) Videostream-native.exe to run 'specific ports' > 5556-5558 C:\Users\MJBiz\AppData\Local\Videostream\app-0.3.6\videostream-native\videostream-native.exe
b) Videostream.exe to run 'specific ports' > 5556-5558 C:\Users\MJBiz\AppData\Local\Videostream\Videostream.exe
c) Videostream.exe to run 'specific ports' > 5556-5558 C:\Users\MJBiz\AppData\Local\Videostream\app-0.3.6\Videostream.exe
1a) I Uninstalled Videostream Desktop
1b) Uninstall VS Extensions from Chrome
Rebooted
2) Search C drive for 'Videostream' - Deleted all files/traces
(I didn't touch/cleanse the registry)
Rebooted
3) Installed Videostream Desktop 0.3.6 - No Compatability settings
Rebooted
4) Right click the VS shortcut on the desktop - Set Compatability to 'Windows 7'
5) Launch Videostream
Various Reboots / Powered up & down - Still consistantly working after a week, no failures