<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[if log-File C:&#x5C;Windows&#x5C;Logs&#x5C;SecTeer&#x5C;secteer.log stopps after &quot;Enumerating MSI data&quot;]]></title><description><![CDATA[<p dir="auto">Not really a bug with secteer but may be a problem with some older/rare msi-Files and so more a hint:</p>
<p dir="auto">I observed on my machines, that the agent stopped working after "Enumerating MSI data". exe/agent were still running (so no "die" of process/service).</p>
<p dir="auto">As the agent is running as a service it can't display windows to the users (silent).<br />
When running from a Admin-CMD the Windows Installer comes up with message-windows and i had to fix 2 msi -files: "Windows Installer: The feature you are trying to use is on a network resource that is anavailiable. --&gt; Browse...". One was located on a DVD and one on "C:\Users...\AppData\Local\Temp....". Both from programs i would not request from you to be detected!!</p>
<p dir="auto">I re-created the files, put them to a persistant location on HDD, followed the instuctions of windows installer and on next run secteer runs on the MSI-Topics with success.</p>
]]></description><link>https://vulndetect.org/topic/678/if-log-file-c-windows-logs-secteer-secteer-log-stopps-after-enumerating-msi-data</link><generator>RSS for Node</generator><lastBuildDate>Fri, 06 Mar 2026 14:16:39 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/678.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 27 May 2019 21:32:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to if log-File C:&#x5C;Windows&#x5C;Logs&#x5C;SecTeer&#x5C;secteer.log stopps after &quot;Enumerating MSI data&quot; on Sat, 08 Jun 2019 18:00:55 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/cdqeaw67" aria-label="Profile: cdqEAW67">@<bdi>cdqEAW67</bdi></a> Awesome and thank you</p>
]]></description><link>https://vulndetect.org/post/3025</link><guid isPermaLink="true">https://vulndetect.org/post/3025</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Sat, 08 Jun 2019 18:00:55 GMT</pubDate></item><item><title><![CDATA[Reply to if log-File C:&#x5C;Windows&#x5C;Logs&#x5C;SecTeer&#x5C;secteer.log stopps after &quot;Enumerating MSI data&quot; on Sat, 08 Jun 2019 13:54:43 GMT]]></title><description><![CDATA[<p dir="auto">After making my special-msi unavailiable the 1.0.7.0 is continuing the scan and submits the data (checked with agent and --immediate).<br />
So it's OK now!! :+1:<br />
Thx</p>
]]></description><link>https://vulndetect.org/post/3023</link><guid isPermaLink="true">https://vulndetect.org/post/3023</guid><dc:creator><![CDATA[cdqEAW67]]></dc:creator><pubDate>Sat, 08 Jun 2019 13:54:43 GMT</pubDate></item><item><title><![CDATA[Reply to if log-File C:&#x5C;Windows&#x5C;Logs&#x5C;SecTeer&#x5C;secteer.log stopps after &quot;Enumerating MSI data&quot; on Wed, 05 Jun 2019 06:54:58 GMT]]></title><description><![CDATA[<p dir="auto">We have made some changes to how we handle the enumeration of MSI data, we hope this will prevent this behavior.</p>
<p dir="auto">You can download the latest agent here:<br />
<a href="https://vulndetect.com/dl/secteerSetup.exe" rel="nofollow ugc">https://vulndetect.com/dl/secteerSetup.exe</a></p>
<p dir="auto">Again, thank you for reporting these issues.</p>
]]></description><link>https://vulndetect.org/post/2994</link><guid isPermaLink="true">https://vulndetect.org/post/2994</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Wed, 05 Jun 2019 06:54:58 GMT</pubDate></item><item><title><![CDATA[Reply to if log-File C:&#x5C;Windows&#x5C;Logs&#x5C;SecTeer&#x5C;secteer.log stopps after &quot;Enumerating MSI data&quot; on Tue, 28 May 2019 18:21:33 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Thanks for reporting this. Sounds like an interesting issue.</p>
<p dir="auto">Will look at it and see if we can reproduce and work around it.</p>
<p dir="auto">/Tom</p>
]]></description><link>https://vulndetect.org/post/2935</link><guid isPermaLink="true">https://vulndetect.org/post/2935</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Tue, 28 May 2019 18:21:33 GMT</pubDate></item></channel></rss>