Loading custom DLLs instead of original DLLs
<p><strong>The question below is for educational purposes only and the discussed featured are not meant to alter registered DLLs or develop a malware but for learning and experiencing.</strong></p>

<p>Recently I've been exploring few methods to load my own custom DLLs instead of an application's original DLLs.
One of the methods that came up was the <code>&lt;exe&gt;.local</code> method.</p>

<p>After experiencing with this method a little bit and after I removed the <code>KnownDlls</code> entry from the registry I managed to replace some system DLLs with my patched DLLs successfully.</p>

<p>These are the DLLs:</p>

<p><a href="https://i.stack.imgur.com/hGUTD.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hGUTD.png" alt="enter image description here"></a></p>

<p>However, the DLLs are IN the local folder:</p>

<p><a href="https://i.stack.imgur.com/0FuUo.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0FuUo.png" alt="enter image description here"></a></p>

<p>However, there are still some DLLs that insist loading from the <code>system32</code> directory, although they are present in the local folder.</p>

<p>Is there any way I can force the DLL's to load from the local folder instead of the system32 folder?</p>