 Microsoft Windows checks the registry to determine the proper place to load DLLs that implement COM objects, but for other DLLs it will check the directories in a defined order.First, Windows checks the directory where it loaded the program ("private DLL"); any directories set by calling the codice_1 function; the System32, System, and Windows directories; then the current working directory; and finally the directories specified by the PATH environment variable.Applications written for the .NET Framework framework (since 2002), also check the Global Assembly Cache as the primary store of shared dll files to remove the issue of DLL hell.