Hi all. I posted in another thread about this problem but the original poster said this wasn't the issue on his end. Therefore I'm posting this as its own thread.
I upgraded to 1.3.0.0 the night before last, and I'm having terrible hang times. This is happening on both my computers and there's plenty of speed and memory available. It's all running cabled (no wi-fi usage) to a fiber gigabit symmetrical connection. The cpu processor still shows very low usage and both systems show plenty amount of resources available. I've attached a screenshot below and I'll re-attach the log files for this post. This is on Win10 enterprise and everything is fully updated. I could understand it possibly being related to my computer if I was only running one copy of anystream, but I'm not. I'm running anystream on two different computers, both hardwired and updated with latest windows 10 updates. I've rebooted everything from the computer, down to the main fiber connector outside multiple times, enabled & disabled VPNs, firewalls, anti-virus software, changed IPs and still having these issues. Any ideas if this is a bug or if I'm the only one having this problem?
I upgraded to 1.3.0.0 the night before last, and I'm having terrible hang times. This is happening on both my computers and there's plenty of speed and memory available. It's all running cabled (no wi-fi usage) to a fiber gigabit symmetrical connection. The cpu processor still shows very low usage and both systems show plenty amount of resources available. I've attached a screenshot below and I'll re-attach the log files for this post. This is on Win10 enterprise and everything is fully updated. I could understand it possibly being related to my computer if I was only running one copy of anystream, but I'm not. I'm running anystream on two different computers, both hardwired and updated with latest windows 10 updates. I've rebooted everything from the computer, down to the main fiber connector outside multiple times, enabled & disabled VPNs, firewalls, anti-virus software, changed IPs and still having these issues. Any ideas if this is a bug or if I'm the only one having this problem?