The linked article [1] has an explanation:<p><pre><code>  In simple terms if an application (e.g. Test.exe) loads
  a DLL (e,g. foo.dll) by just the name, Windows follows
  a specific search order depending upon whether
  “SafeDllSearchMode” is enabled or disabled to
  locate the legitimate DLL. 
</code></pre>
So it looks like the installer is legitimately attempting to load some DLL but either hasn&#x27;t fully qualified the name or hasn&#x27;t enabled this flag<p>[1]: <a href="http:&#x2F;&#x2F;blog.opensecurityresearch.com&#x2F;2014&#x2F;01&#x2F;unsafe-dll-loading-vulnerabilities.html" rel="nofollow">http:&#x2F;&#x2F;blog.opensecurityresearch.com&#x2F;2014&#x2F;01&#x2F;unsafe-dll-load...</a>