Normal module with no errors. Normal module with no errors.
Duplicate module. This module has already been processed somewhere else in the tree. You can use the Highlight Original Instance Command to find the original instance of the module in the tree.
Forwarded module. This module is a dependency because the parent module has forwarded one of its functions to this module.
Delay-load module. This module will be dynamically loaded if any of its exported functions are actually called at run-time.
Dynamic module. This module was detected during profiling and was dynamically loaded or used by its parent module. If the module has no parent, then Dependency Walker was unable to determine who loaded the module. See Using Application Profiling to Detect Dynamic Dependencies for more information.
This module was dynamically loaded by a call to the LoadLibraryEx function with the DONT_RESOLVE_DLL_REFERENCES flag. This flag causes the module to get mapped into memory without loading its dependent modules or calling the module’s DllMain function.
64-bit module. This module is designed to run on a 64-bit versions of
Windows. Modules are assumed to be 32-bit if this image is not present.
Missing module. This module could not be found in the search path. See the Configure Search Order Command for more information.
Invalid module. See the Module List View for an error message describing the module error.
Module with one or more missing export functions that are required by its parent module. The Parent Import Function List View will list the actual unresolved functions that are causing the problem. For implicit dependencies, this is an error that will cause the parent module to fail to load.
Delay-load module with one or more missing export functions that are requested by its parent module. The Parent Import Function List View will list the actual unresolved functions that are missing. For delay-load dependencies, this is most likely not an error since one reason developers
use delay-load modules is when they are unsure if a particular function exists in dependent module. Parents of delay-load modules have techniques for recovering from missing exports in the delay-loaded dependent module.
Dynamic module with one or more missing export functions that the parent module attempted to locate using the GetProcAddress function. The Parent Import Function List View will list the actual functions that are
parent module could not locate. For dynamic dependencies, this is just a warning, since it is perfectly valid for a module to dynamically check for the existence of a function in another module, even if the function does not exist.
Resolved C import.
Resolved C++ import. C++ functions can be viewed in their native decorated form or in a human readable undecorated form. See the Undecorate C++ Functions Command for more information.
Resolved ordinal import.
Resolved dynamic C import (similar images also exist for C++ and ordinal functions). The parent module of this module called the GetProcAddress
function to dynamically get the address of this function. This does not necessarily mean the parent module actually used the function address to call the function.
Unresolved C function (similar images also exist for C++ and ordinal functions). This function is called by the parent module, but it is not exported from the current module. This is often referred to as an "unresolved external function". If this module is an implicit or forwarded dependency, then the parent module will fail to load. If this module is a delay-load dependency, then the parent module will most likely recover from the missing dependency, as that is a feature of using delay-load dependencies.
Unresolved dynamic C function (similar images also exist for C++ and ordinal functions). The parent module of this module called the GetProcAddress function to dynamically get the address of this function, but the current module does not export the function. This is not necessarily an error since one of the reasons modules call GetProcAddress is to see if a function exists in a module.
ID C export function that resides in the selected module.
@3 C++ export function that resides in the selected module. C++ functions can be viewed in their native decorated form or in a human readable undecorated form. See the Undecorate C++ Functions Commano:lfor more information.
Ordinal export function that resides in the selected module.
ID C export function that is called at least once by any module in the current module session
(similar images also exist for C++ and ordinal functions)
C export function that is called by the selected module in the Module Dependency Tree View (similar images also exist for C++ and ordinal functions). There will be a one-to-one relationshif between these functions and the resolved imports in the Parent Import Function List View. You can use the Highlight Matching Item command to quickly jump between the matching import and export.
Forwarded C export function that resides in a different module (similar images also exist for
C++ and ordinal functions). The module that the function truly resides in is listed in the Entry Point column.