ThreatLocker 7.4 Release Notes
- Resolved an issue where excessive caching caused high memory usage.
- Resolved an issue some customers experienced with elevation mode not logging as elevated in the Unified Audit
- Resolved an issue some customers experienced with Ringfencing needing a process restart after the ThreatLocker service was restarted
- Reduced the number of logs generated by certain processes that scan files but windows identifies their scanning as executes
Did this answer your question?
Thanks so much for your feedback!
%s of people found this helpful.