As captioned. Case 2215216 has been raised to the Splunk support, who replied that the delay was caused by the failure of the script running as part of the TA for MS Windows Defender. As the issue belongs to a 3rd party add-on, Splunk will not support or try to fix it. We would like to know if there are other users who also experienced a similar problem with the TA before. Is there any workaround or resolution to it? Any comments or suggestions are greatly appreciated. Thanks a lot. Sunny Suen (Splunk CSM) ... View more