In this article:

    Symptoms

    • The Twingate Client appears to freeze after clicking join network
    • The below log snippet in %LOCALAPPDATA%\Twingate\logs\Twingate.Service.log is seen:
    2022-07-27 08:13:39.1962 [DEBUG] JoinNetworkViewModel.JoinNetwork User clicks join network
    2022-07-27 08:13:39.2223 [DEBUG] ControllerServerValidator.ValidateAsync ControllerServerValidator. Validate uri https://mynetwork.twingate.com/
    2022-07-27 08:13:39.7912 [INFO] JoinNetworkViewModel.JoinNetwork Join Network validation status = Ok. Model: network = mynetwork url = https://twingate.com
    2022-07-27 08:13:39.8087 [DEBUG] JoinNetworkViewModel.JoinNetwork User set a network
    2022-07-27 08:13:39.8087 [DEBUG] TrayConnectionRunner.UpdateConnectionAsync TrayConnectionRunner.UpdateConnectionAsync
    2022-07-27 08:13:39.8319 [DEBUG] ConnectionModel.UpdateFromState ConnectionModel.UpdateFromState newState = Authenticating
    2022-07-27 08:13:39.8319 [DEBUG] ServiceCommunication.RunPreconnectionChecks Run preconnection checks. 
    2022-07-27 08:13:39.8319 [DEBUG] DevicePostureDataProvider.GenerateClientData Start client posture data collection.
    2022-07-27 08:13:39.8319 [ERROR] ServiceCommunication.RunPreconnectionChecks Communication faulted. System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
    • Twingate errors are seen within Windows Event - Application view.

                mceclip3.png

                mceclip2.png

    • Unable to verify system information via powershell. i.e  The following command ran within powershell fails to return data gwmi Win32_DISKDRIVE | select *

    Cause

    • The twingate service is failing to start because it is unable to complete the required posture checks used to verify the identity of the operating system and hardware. The Twingate service uses the win32 repository within WMI (Windows Management Instrumentation) in order to pull the required system information. 
    • The WMI win32 repository among others can become corrupt from improper shutdowns, bluescreens, application crashes, etc.

    Resolution

    • From an administrative command prompt, use the following command to recompile the win32 MOF(Managed Object Format) within WMI.                                                                               mofcomp %windir%\system32\wbem\cimwin32.mof