| Previous | Next |
| STATUS_DLL_MIGHT_BE_INSECURE | STATUS_STOPPED_ON_SYMLINK |
STATUS_DLL_MIGHT_BE_INCOMPATIBLE
Security and compatibility module choices disagree
This warning indicates that Windows has identified a module choice considered secure but potentially incompatible with behavior expected by older software. It is different from a missing DLL or architecture failure: the candidate can be loaded, yet exported behavior, version assumptions, or legacy shims may differ from the alternative.
Choosing the older file globally is risky because it can reintroduce insecure search or implementation behavior. Compatibility should be evaluated with the exact application, exported API set, and deployment context, preferably by updating the application or installing a vendor-supported build.
What to inspect
- Capture both candidate paths, versions, signatures, architectures, and the search rule that produced each choice.
- Compare required imports and exported symbol versions rather than relying only on the DLL base name.
- Test the secure module with representative workloads and collect loader snaps or dependency traces for failures.
- Avoid copying legacy DLLs into system directories or changing global search order to satisfy one application.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: dynamic-link library search order
- Microsoft: linking an executable to a DLL
- Microsoft: LoadLibraryEx
Looking for a different code? Search another status or error code.