1298 - Warning: "Non Daemon Thread"

Symptom

The backup service is shut down during a backup or an Insight scan, and the following errors are presented:

WARN : 19:03:41 Non Daemon Thread pool-1-thread-1 still active. Interrupting...
 WARN : 19:03:41 Non Daemon Thread HttpClient@7bc52ba7-46 still active. Interrupting...
 WARN : 19:03:42 Non Daemon Thread HttpClient@7bc52ba7-47 still active. Interrupting...
 WARN : 19:03:42 Non Daemon Thread HttpClient@7bc52ba7-48 still active. Interrupting...
 WARN : 19:03:43 Non Daemon Thread HttpClient@7bc52ba7-49 still active. Interrupting...
 WARN : 19:03:43 Non Daemon Thread HttpClient@7bc52ba7-50 still active. Interrupting...
 WARN : 19:03:44 Non Daemon Thread HttpClient@7bc52ba7-51 still active. Interrupting...
 WARN : 19:03:44 Non Daemon Thread HttpClient@7bc52ba7-53 still active. Interrupting...
 WARN : 19:03:45 Non Daemon Thread HttpClient@7bc52ba7-scheduler-1 still active. Interrupting...
 WARN : 19:03:45 Non Daemon Thread HttpClient@1f0f3316-94 still active. Interrupting...
 WARN : 19:03:46 Non Daemon Thread HttpClient@1f0f3316-95 still active. Interrupting...
 WARN : 19:03:46 Non Daemon Thread HttpClient@1f0f3316-96 still active. Interrupting...
 WARN : 19:03:47 Non Daemon Thread HttpClient@1f0f3316-97 still active. Interrupting...
 WARN : 19:03:47 Non Daemon Thread HttpClient@1f0f3316-98 still active. Interrupting...
 WARN : 19:03:48 Non Daemon Thread HttpClient@1f0f3316-99 still active. Interrupting...
 WARN : 19:03:48 Non Daemon Thread HttpClient@1f0f3316-100 still active. Interrupting...
 WARN : 19:03:49 Non Daemon Thread HttpClient@1f0f3316-101 still active. Interrupting...
 WARN : 19:03:49 Non Daemon Thread HttpClient@1f0f3316-scheduler-1 still active. Interrupting...
 WARN : 19:03:50 Non Daemon Thread InsightScan 1594663377083 still active. Interrupting...
 WARN : 19:03:50 Non Daemon Thread HttpClient@7bc52ba7-173 still active. Interrupting...

Cause

This can be caused by antivirus software, an Agent update, or a scheduled reboot.

Solution

Check that the appropriate antivirus exclusions are in place, and check the Windows event logs to see if a reboot or service restart is visible there which could explain the shutdown.