Skip to main content
Windows Agent 24.11.1460 (2024-03-28)
A
Written by Arick Disilva
Updated over a week ago

Bug Fixes

Windows Update Bug Causing the Agent to Crash

Due to a known Windows defect, after Windows Updates, in rare cases, the folder with certificates (catroot2 in the system32 folder) would become invalid. System calls that implicitly use this folder would lead to delays, as a result, failures in the normal operation of the Agent were observed.

The behavior of the agent has been corrected so that the Windows bug should not affect the operability of the Agent.

Other Improvements

  • Collect network logs via remote troubleshooting

  • Better handling of event data when multiple connections are initiated by a single Agent

  • Better process monitor reports with launcher user name and process name to diagnose Agent health status

  • Analysis of APM (Application Performance Monitoring) effect on network traffic

  • Improved codes to prevent hang-ups in MS Teams monitoring module,

Did this answer your question?