Chris's community posts

I believe Windows 10 has a lot more animations (menu's fading in an out) than previous versions. So you have to wait for each step in the animation to be captured.  You can turn off animations under Control Panel (search for animation). Or right click on "This PC" in the file explorer, choose Properties, then Advanced System Settings, then Performance, and choose Best Performance.

I have Webroot installed on all the PC's that won't connect anymore with the beta. The one new PC has Avast on it and it stays connected.  Do I need to email you the log? It doesn't show much, about the same as the non-beta version. The beta host failed @ 9:55AM and the last log available (date modified) is dated 9:40AM (which is when the service started). The log shows when it connects then nothing after that. I removed the IP, hostname, and internet ID below since this is a public forum.

03.10.2016---09:40:51:854 34 RUT Host 64002 is started. Windows 10.0 64bit
03.10.2016---09:40:52:323 96 Internet-ID: Connection established ID: ***-***-***; Server: ***.ddns.net (***.***.***.***); Port: 5655; Try count: 1

So I shut down Webroot, started the service and it's been connected now for more than an hour! Although I do have to report a few minutes ago the icon for the host is no longer in my taskbar, though the service is still running and I can connect/logon.  I do have rutserv.exe, rfusclient.exe, ripcserver.dll, and rwln.dll all on the Allow list in Webroot.  I restarted Webroot and within a couple minutes the service crashed.

I restarted the service and it ran for 11 minutes and quit (webroot running).

Shut down webroot, started the service and it ran as long as I wanted (an hour or more), or at least until I started Webroot again (would stop within minutes).  Watching the process in Webroot, not much is said when it exits but this:
Process ID: 12340
Thread ID: 3544
Event Type: Process
Access: Kill
Target Process ID: 12340

Correct, I completely uninstalled, rebooted, and reinstalled the beta host. My PC does have all the latest updates, including the anniversary and several beyond that (checked 4 times yesterday for updates). The last update was ver1607 KB3194496. I tried several times to get a clean install. Once I used Windows control panel to remove the host, and when I reinstalled the beta it already had the old internet-ID and custom host. So I ran the install for the host, which uninstalled and I was able to check the remove all settings button. Rebooted, installed the beta host and it still had the internet-ID and custom server. I was hoping if I could get back to a clean system and put the beta on it would stick (reason below).

I added the beta host to a PC that has never had the host installed before and it's staying connected, 2 days so far. Several other (remote to me) PC's were updated this weekend from 6.3 to the beta and they all stopped connecting (just like my local PC). They are all W10 w/anniversary/all updates. All of my 6.3 hosts are staying connected to my beta RU server OK, and the one PC that has the beta host (but has never had a 6.3 host installed before).

So I just tried again, and I noticed that I forgot to mention I was not installing the printer or screen driver on the beta. I installed the beta again and this time chose the screen/blank driver (but not the printer). It's been running and connected over 10 minutes now so I think the problem is because I did not install the new monitor/screen driver? I do not want to install any extra drivers than necessary on my host PC's, especially gaming/HTPC's. You guys must be looking for the status of the driver or something and crashing the host service if it's not found? Odd, the one new PC I installed the beta host (that had never had a host installed) does not have the screen driver installed and it's staying connected.

sorry for the continual updates...it stayed connected for 15 minutes then dropped so I guess it wasn't the screen driver (but did help stay connected longer).

I uninstalled the beta host and put 6.3 back on and it stays connected just fine. Stinks as the next W10 update will kill the connection. If there's anything I can do to help test the beta host let me know.

Can I not run both the viewer and host at the same time on the same PC? This PC is different from my RU server, but when I'm running the Viewer my host is not connected and if I restart the host it'll stay connected for maybe 5 minutes then drop. When I say drop I cannot see it connected to the RU server in idle connections plus the dot next to whatever the blue thing is in the icon is no longer there. It still shows running still in the taskbar.  I left for the weekend and could not connect to this host and I was using the viewer before I left. Something doesn't seem right, not with it dropping every 5 minutes and never reconnecting.
And FYI, Webroot is blocking/quarantining the rutserver.exe files now. I was trying to manually install the beta host on a few PC's running the older version and I had a heck of a time getting it to install (had to run multiple times, even when I figured out I needed to disable webroot while I installed). And it seems all those PC's I installed the beta host onto this weekend had connected for 5 minutes but now do not show connected to my server.

I see this in regarding the host service crash in my event log (stayed connected only 1 minute)...
- <System>
 <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
 <EventID Qualifiers="49152">7034</EventID>
 <Version>0</Version>
 <Level>2</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x8080000000000000</Keywords>
 <TimeCreated SystemTime="2016-10-03T03:05:09.574288600Z" />
 <EventRecordID>4706</EventRecordID>
 <Correlation />
 <Execution ProcessID="920" ThreadID="304" />
 <Channel>System</Channel>
 <Computer>Monty</Computer>
 <Security />
 </System>
- <EventData>
 <Data Name="param1">Usoris - Host</Data>
 <Data Name="param2">1</Data>
 <Binary>52004D0061006E0053006500720076006900630065000000</Bi­nary>
 </EventData>
 </Event>