<![CDATA[Create Log-Folder before Scanning]]>I updated my Windows 10 from April 2018 update to 10 October 2018 Update.
I recognized that the log-folder (C:\Windows\Logs\SecTeer) is not existing.

While updating Windows moved the system files from *C:\Windows* to C:\Windows.old\WINDOWS.
So the old log folder is now the folder C:\Windows.old\WINDOWS\Logs\SecTeer
But VUlnDetect does not create the SecTeer folder in the Windows Log Folder.

When I uninstalled VulnDetect and reinstalled VulnDetect, then the folder (C:\Windows\Logs\SecTeer) is created.
So the log folder is only created at installation, not by executing a full system scan.

When I start a system scan then please check first if the log folder is existing and create it if needed.
Then start the system scan.
This prevents that users have to install VulnDetect again just because the log folder is not exiting.

]]>https://vulndetect.org/topic/412/create-log-folder-before-scanningRSS for NodeSat, 16 May 2026 05:13:21 GMTThu, 04 Oct 2018 18:39:52 GMT60<![CDATA[Reply to Create Log-Folder before Scanning on Thu, 04 Oct 2018 19:36:18 GMT]]>@tom said in Create Log-Folder before Scanning:

This is scheduled to be changed in one of the next two upcoming releases

Glad that you want to fix this...

]]>https://vulndetect.org/post/1622https://vulndetect.org/post/1622Thu, 04 Oct 2018 19:36:18 GMT<![CDATA[Reply to Create Log-Folder before Scanning on Thu, 04 Oct 2018 19:37:56 GMT]]>This is scheduled to be changed in one of the next two upcoming releases of the VulnDetect agent. Massive additions are planned for the agent in the coming weeks, but I can't promise that the log issue will be fixed in the first release.
You can always run it using secteer.exe -l c:\users\<youruser>\somefilename.log if you need the log or create the folder like you suggest.

]]>https://vulndetect.org/post/1621https://vulndetect.org/post/1621Thu, 04 Oct 2018 19:37:56 GMT