MID Server startup fails when Cortex XDR service is running on MID server hostDescriptionMID Server startup fails when Cortex XDR service is running on MID server host. There is no indication on the agent log or wrapper log as to why the service crashedIn agent logs, we see the startup stops at 2021-05-01 02:13:44 (372) StartupSequencer PowerShell version result: full_version:5.1.14393.4350, major_version:52021-05-01 02:13:44 (372) StartupSequencer verify Powershell major version 5 against compatible version requirement (v3 - v5)2021-05-01 02:13:44 (372) StartupSequencer PowerShell path is set to "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe", version 5.1.14393.4350 The next line on the startup would be the following, however the MID server never gets to it 2021-05-01 02:14:17 (955) StartupSequencer The service name is detected as snc_mid_midServiceName In the windows event viewer, we see error with id 7034 and description The ServiceNow MID Server_nameOfService service terminated unexpectedly CauseService "Cortex XDR" does not allow MID server to start threads.ResolutionStopping the Cortex XDR service and restarting the MID server has been seen to workaround the issue. The vendor has introduced a new CU 179-57935 (Content update, like a patch, released weekly), which addresses this issue.Additional InformationKB0961505 - MID server service is terminated unexpectedly on startup (error id 7034), causing MID Server to go Down, due to third party security software Cortex XDR