It happens through out the day here are two examples from event log Fault bucket 1338226281304151579, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: ViscosityService.exe P2: 1.7.16.1616 P3: 5cee4e8a P4: System.Management P5: 4.7.3056.0 P6: 5a8e5a11 P7: 8c P8: 3f ...

Hello,

We are having the same issue, on nearly every computer in our environment.

However, it does not seem to be causing any problems with the user actually staying connected to the VPN.