I’ve recently started trying to use my 4C again and like the OP, I’m still getting random disconnects until the device stops working all together until I have to reboot the system to sometimes get it working again.
In the Windows event viewer, the following Error Event ID 10016 occurs in direct correlation to the 4C attempting to connect and then subsequently disconnecting.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
I have tried giving the DCOM Configuration permission as outlined here: (process still applies to Windows 10)
The other error that also occasionally occurs is:
Faulting application name: Tobii.EyeX.Engine.exe, version: 1.24.1.7398, time stamp: 0x5ae6bf76
Faulting module name: tobii_stream_engine.DLL, version: 2.0.1.2323, time stamp: 0x59f73c97
Exception code: 0xc0000409
Fault offset: 0x00087c24
Faulting process id: 0x31f8
Faulting application start time: 0x01d4e5484444770f
Faulting application path: C:\Program Files (x86)\Tobii\Tobii EyeX\Tobii.EyeX.Engine.exe
Faulting module path: C:\Program Files (x86)\Tobii\Tobii EyeX\tobii_stream_engine.DLL
Report Id: 37c258df-16a1-4e0c-8ba1-4eb9ca2a7bd2
Faulting package full name:
Faulting package-relative application ID:
From memory, these disconnection errors only seemed to start occurring when I updated to the Core Software 2.13 branch whenever that was released. The Core Software version that was available February 2018 did not have these issues.