Trending issue is known for ThreatLocker versions 7.0 to 7.4 where a service restart that is sent from the ThreatLocker portal via the computers page does not successfully stop the driver leaving it in a pending or suspended state. This will also cause the service to not check in to the portal making the computer appear offline despite the service runnning. The current workaround for this issue is a system restart, and is recommended to be done as soon as possible to correct functionality in our service. This is known to only affect specific computers, however we are unable to replicate which types of machines or Windows OS versions are affected.
<h2>The ThreatLocker Solution:</h2>
This is fixed for ThreatLocker version 7.6. You can view the release notes here:
&nbsp;<a href="https://threatlocker.kb.help/threatlocker-version-76-release-notes/" target="_blank">ThreatLocker Version 7.6 Release Notes | ThreatLocker Help Center (kb.help)</a>&nbsp;
How to update your machines:
<a href="https://threatlocker.kb.help/updating-the-threatlocker-version-on-a-single-computer/" target="_blank">Updating the ThreatLocker Version on a Single Computer | ThreatLocker Help Center (kb.help)</a>&nbsp;
<a href="https://threatlocker.kb.help/updating-threatlocker-to-the-latest-version/" target="_blank">Updating ThreatLocker to the Latest Version | ThreatLocker Help Center (kb.help)</a>&nbsp;

Trending issue is known for ThreatLocker versions 7.0 to 7.4 where a service restart that is sent from the ThreatLocker portal via the computers page does not successfully stop the driver leaving it in a pending or suspended state. This will also cause the service to not check in to the portal making the computer appear offline despite the service runnning. The current workaround for this issue is a system restart, and is recommended to be done as soon as possible to correct functionality in our service. This is known to only affect specific computers, however we are unable to replicate which types of machines or Windows OS versions are affected.
The ThreatLocker Solution:
This is fixed for ThreatLocker version 7.6. You can view the release notes here:
 ThreatLocker Version 7.6 Release Notes | ThreatLocker Help Center (kb.help) 
How to update your machines:
Updating the ThreatLocker Version on a Single Computer | ThreatLocker Help Center (kb.help) 
Updating ThreatLocker to the Latest Version | ThreatLocker Help Center (kb.help) 

Known Issue: Driver Not Restarting on Versions 7.0-7.4

Known Issue: Simulated Denies Not Showing When Network Control is Enabled Without Policies

Known Issue: Powershell Will Not Open When the Option MonitorPowerShell is Enabled

Windows Agent Known Issues by Build Number

Known Issue: Syncplicity Preventing Machines from Checking-in

Known Issue: Applications May Not be Able to Run as Admin when Updating from Agent Version 7.8.x 

Known Error with PowerShell ConstrainedLanguage Mode

Known Issue: Performance Issues with ThreatLocker and Deep Instinct

Known Issue: DNS Caching on Versions 7.0-7.6.2

Known Issue: Some ActiveX .ocx Files Not Recognized as Executing Pre 7.9 

Known Backup Issues with Tamper Protection on Agent Version 7.7.*

Known Issues

Search our Knowledge Base