Leaktrap - Google Code. The LoadLibrary Explorer. There is a lot of confusion about the way LoadLibrary and LoadLibraryEx work, especially given the various security changes made in Windows 2000, Windows XP, and Server 2003 Service Packs. I needed to get the correct information about how this worked, and consequently had to create a program that actually did these calls. The results are a bit surprising. Not only is there a lot of incorrect folklore and misinterpretation out there about what is going on, but the documentation itself appears to be incorrect. Appears to be lying it its teeth, to make an understatement. There are many factors that determine where a DLL is found during a load.
They include This program explores how LoadLibrary and LoadLlibraryEx work by allowing you to install a DLL in a specific place, or places, and then see from which place it was loaded. Here's the documentation from the LoadLibrary documentation in the MSDN: If SafeDllSearchMode is 1 (the default), the search order is as follows: Loading the DLL. Dependency Walker (depends.exe) Home Page. How to get rid of Microsoft Detours’ detoured.dll « coderrr. Shameless Plug: Use a Microsoft Compatible VPN Service to protect your privacy when working with public APIs. If you don’t know what DLL injection, API hooking, instrumentation, or the Detours library is, then you might wanna skip this post. The story Microsoft has a nifty library called Detours which helps you intercept function calls using something called inline-function-hooking or detouring.
Basically, it finds the target function, and overwrites its memory with a JMP instruction pointing to a different function. Anyway, Detours provides a nice little API to do this for you. Sucky thing is, it comes with a detoured.dll library which needs to be present for detours to work. This, in essence, flags whatever process you use Detours to detour. This may or may not be an issue for you depending what you’re trying to accomplish. Well it’s not necessary, and it’s really easy to get rid of.
Straight from the README.TXT: 4.5. Anyway, How to remove it Open up detours.cpp, Remove the line:Detoured(); Libase: Rebasing Win32 DLLs | December 1, 2000. NiftyLoadLibrary.