[Solved] No Detected Applications & Enumerating Drive Stall
-
@scottsan It is the next thing on our todo, we have an update we need to push later this week. And after that we will dedicate some time to improve some things in the agent, which we believe will fix your issue.
-
@Tom Any progress on my issue? The SecTeer VulnDetect software flat out does not work for me now. It did work fine for me a few months back. So meanwhile I have installed SUMo Software Update Monitor at https://kcsoftwares.com/files/sumo_lite.exe . It just works and even though it is a little more complicated to use.
-
@Tom My E: drive is one of 3 storage partitions (D:, E:. and F:) on a Western Digital 1 GB spinning hard drive....nothing special. I let the software run for about for 4 hours and it just sits at Enumerating 'e:' . See results below
C:\Program Files (x86)\SecTeer VulnDetect>secteer.exe --immediate --path=e:
[2019-01-05 00:14:39.814-0360] SecTeer Agent v0.10.11.0 starting in immediate mode
[2019-01-05 00:14:39.814-0360] Starting SecTeer Agent in immediate mode
[2019-01-05 00:14:39.817-0360] Running immediate inspection
[2019-01-05 00:14:39.817-0360] Configuration:
version:: 0.10.11.0
authToken : cfc90742-f4ea-45d8-8bc8-xxxxxxxxxxxx
server : agent.vulndetect.com
guid1::
guid2::
guid3::
checkInInterval:: 3600 seconds
checkInRetryDelay:: 360 seconds
maxCheckInRetryCount:: 10
dataRetryDelay:: 1800 seconds
inspectionWindow:: 21600 seconds
timezoneOffset : -360 minutes
checkInNow:: false
inspectNow : true
inspectionPath : e:
noFilesystem:: false
noRegistry:: false
noWinUpdate:: false
noSystem:: false
noPackage:: true
[2019-01-05 00:14:39.817-0360] Starting system inspection
[2019-01-05 00:14:39.817-0360] Fetching inspection rules from server
[2019-01-05 00:14:39.843-0360] Connecting to server: agent.vulndetect.com
[2019-01-05 00:14:40.620-0360] Server returned 200 => OK
[2019-01-05 00:14:40.624-0360] Found 'computerName' = 'LIVERNUGGET'
[2019-01-05 00:14:40.679-0360] Enumerating Win32_OperatingSystem
[2019-01-05 00:14:40.750-0360] Enumerating Win32_Bios
[2019-01-05 00:14:40.781-0360] Searching updates: IsInstalled=0
[2019-01-05 00:15:05.867-0360] Found 1 updates
[2019-01-05 00:15:05.872-0360] Searching updates: IsInstalled=1
[2019-01-05 00:15:17.961-0360] Found 70 updates
[2019-01-05 00:15:18.132-0360] Filesystem redirection status: Redirection disabled
[2019-01-05 00:15:18.132-0360] Enumerating 'e:'
^C
C:\Program Files (x86)\SecTeer VulnDetect>secteer.exe --immediate --path=e:
[2019-01-05 04:31:50.170-0360] SecTeer Agent v0.10.11.0 starting in immediate mode
[2019-01-05 04:31:50.170-0360] Starting SecTeer Agent in immediate mode
[2019-01-05 04:31:50.174-0360] Running immediate inspection
[2019-01-05 04:31:50.174-0360] Configuration:
version:: 0.10.11.0
authToken : cfc90742-f4ea-45d8-8bc8-xxxxxxxxxxxx
server : agent.vulndetect.com
guid1::
guid2::
guid3::
checkInInterval:: 3600 seconds
checkInRetryDelay:: 360 seconds
maxCheckInRetryCount:: 10
dataRetryDelay:: 1800 seconds
inspectionWindow:: 21600 seconds
timezoneOffset : -360 minutes
checkInNow:: false
inspectNow : true
inspectionPath : e:
noFilesystem:: false
noRegistry:: false
noWinUpdate:: false
noSystem:: false
noPackage:: true
[2019-01-05 04:31:50.174-0360] Starting system inspection
[2019-01-05 04:31:50.174-0360] Fetching inspection rules from server
[2019-01-05 04:31:50.205-0360] Connecting to server: agent.vulndetect.com
[2019-01-05 04:31:51.040-0360] Server returned 200 => OK
[2019-01-05 04:31:51.044-0360] Found 'computerName' = 'LIVERNUGGET'
[2019-01-05 04:31:51.099-0360] Enumerating Win32_OperatingSystem
[2019-01-05 04:31:51.171-0360] Enumerating Win32_Bios
[2019-01-05 04:31:51.194-0360] Searching updates: IsInstalled=0
[2019-01-05 04:32:15.667-0360] Found 1 updates
[2019-01-05 04:32:15.672-0360] Searching updates: IsInstalled=1
^C
C:\Program Files (x86)\SecTeer VulnDetect> -
@scottsan
What kind of drive is the E drive?
Could you try to leave it running for hours and use
secteer.exe --immedate --path=e:\
without the " as I wrongly suggested initially.At the moment we don't have very good options for debugging this. But we do have plans to improve the inspection and the debugging / logging of what is going on, so we can troubleshoot this better. But we have another task that we need to complete first. And then I believe this is the highest priority.
-
@Tom Hi...I have tried scanning my e: drive by itself and the program stalls. Any ideas?
-
@Tom Tried the command and the program stalls when enumerating e:\ drive. See results below.
C:\Program Files (x86)\SecTeer VulnDetect>secteer -v --immediate --path e:
[2019-01-01 16:25:09.635-0360] SecTeer Agent v0.10.11.0 starting in immediate mode
[2019-01-01 16:25:09.635-0360] Starting SecTeer Agent in immediate mode
[2019-01-01 16:25:09.637-0360] Running immediate inspection
[2019-01-01 16:25:09.637-0360] Configuration:
version:: 0.10.11.0
authToken : ba0b2e67-f4ec-4b88-80ae-xxxxxxxxxxxx
server : agent.vulndetect.com
guid1::
guid2::
guid3::
checkInInterval:: 3600 seconds
checkInRetryDelay:: 360 seconds
maxCheckInRetryCount:: 10
dataRetryDelay:: 1800 seconds
inspectionWindow:: 21600 seconds
timezoneOffset : -360 minutes
checkInNow:: false
inspectNow : true
inspectionPath : e:
noFilesystem:: false
noRegistry:: false
noWinUpdate:: false
noSystem:: false
noPackage:: true
[2019-01-01 16:25:09.637-0360] Starting system inspection
[2019-01-01 16:25:09.637-0360] Fetching inspection rules from server
[2019-01-01 16:25:09.669-0360] Connecting to server: agent.vulndetect.com
[2019-01-01 16:25:10.542-0360] Server returned 200 => OK
[2019-01-01 16:25:10.547-0360] Found 'computerName' = 'LIVERNUGGET'
[2019-01-01 16:25:10.609-0360] Enumerating Win32_OperatingSystem
[2019-01-01 16:25:10.668-0360] Enumerating Win32_Bios
[2019-01-01 16:25:10.700-0360] Searching updates: IsInstalled=0
[2019-01-01 16:25:29.020-0360] Found 1 updates
[2019-01-01 16:25:29.026-0360] Searching updates: IsInstalled=1
[2019-01-01 16:25:40.697-0360] Found 70 updates
[2019-01-01 16:25:40.892-0360] Filesystem redirection status: Redirection disabled
[2019-01-01 16:25:40.892-0360] Enumerating 'e:' -
Thank you.
Could you try to do a:
secteer -v --immediate --path e:\If it reveals path and filenames that you don't want to share on the forum, then you are welcome to send the log via email to tom [at] vulndetect [dot] com
-
I also tried the command C:\Program Files (x86)\SecTeer VulnDetect>secteer --check-in --immediate and monitored the memory usage when it got the e: drive. It did not change at all.
-
@Tom said in No Detected Applications & Enumerating Drive Stall:
secteer.exe --immediate --path="c:"
Hi Tom,
C drive is my system drive. I tried your command and it scanned for less than a minute. Below are the results.
C:\Program Files (x86)\SecTeer VulnDetect>secteer.exe --immediate --path="c:"
[2019-01-01 03:22:00.423-0360] SecTeer Agent v0.10.11.0 starting in immediate mode
[2019-01-01 03:22:00.423-0360] Starting SecTeer Agent in immediate mode
[2019-01-01 03:22:00.426-0360] Running immediate inspection
[2019-01-01 03:22:00.426-0360] Configuration:
version:: 0.10.11.0
authToken : ba0b2e67-f4ec-4b88-80ae-xxxxxxxxxxxx
server : agent.vulndetect.com
guid1::
guid2::
guid3::
checkInInterval:: 3600 seconds
checkInRetryDelay:: 360 seconds
maxCheckInRetryCount:: 10
dataRetryDelay:: 1800 seconds
inspectionWindow:: 21600 seconds
timezoneOffset : -360 minutes
checkInNow:: false
inspectNow : true
inspectionPath : c:"
noFilesystem:: false
noRegistry:: false
noWinUpdate:: false
noSystem:: false
noPackage:: true
[2019-01-01 03:22:00.426-0360] Starting system inspection
[2019-01-01 03:22:00.426-0360] Fetching inspection rules from server
[2019-01-01 03:22:00.478-0360] Connecting to server: agent.vulndetect.com
[2019-01-01 03:22:01.271-0360] Server returned 200 => OK
[2019-01-01 03:22:01.276-0360] Found 'computerName' = 'LIVERNUGGET'
[2019-01-01 03:22:01.340-0360] Enumerating Win32_OperatingSystem
[2019-01-01 03:22:01.419-0360] Enumerating Win32_Bios
[2019-01-01 03:22:01.457-0360] Searching updates: IsInstalled=0
[2019-01-01 03:22:14.714-0360] Found 1 updates
[2019-01-01 03:22:14.718-0360] Searching updates: IsInstalled=1
[2019-01-01 03:22:26.621-0360] Found 70 updates
[2019-01-01 03:22:26.828-0360] Filesystem redirection status: Redirection disabled
[2019-01-01 03:22:26.828-0360] Examining file 'c:"'
[2019-01-01 03:22:26.828-0360] Skipping file 'c:"' because it is not interesting
[2019-01-01 03:22:26.828-0360] Finished enumerating filesystem, found 0 interesting files
[2019-01-01 03:22:26.828-0360] Inspecting interesting files
[2019-01-01 03:22:26.828-0360] Enumerated filesystem in 0.000ms
[2019-01-01 03:22:26.828-0360] Read file version information in 0.000ms
[2019-01-01 03:22:26.828-0360] Inspecting registry
[2019-01-01 03:22:26.968-0360] Inspected registry in 0.139ms
[2019-01-01 03:22:26.968-0360] Sending inspection data to server
[2019-01-01 03:22:26.974-0360] Connecting to server: agent.vulndetect.com
[2019-01-01 03:22:27.360-0360] Server returned 202 => Accepted
[2019-01-01 03:22:27.365-0360] SecTeer Agent exiting -
Hi,
Thank you for reporting this.
It sounds similar to another issue that was reported.
Can you try to monitor the memory usage of the agent with Task Manager (taskmgr.exe) or similar when it enumerates the e: drive.
We could also try to change the log level of the agent, but that requires a change to the registry, but that may reveal more about what is going on.
Also, you can try to do a
secteer.exe --immediate --path=c:\that should give you a result for the C drive, which I assume is your system drive.
Happy New Year,
Tom