-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to fix KbLdrStatus::KbLdrImportNotResolved at MapDriverFile? #18
Comments
Show your driver dependencies in export table |
Im not exactly sure what you mean so here is a dumpfile of my driver its 1:1 the above code. PE signature found
|
WDFLDR.SYS
It seems that they're not exported by MmGetSystemRoutineAddress that uses to resolve dependencies of your driver. You can find a minimal working sample in KbLoadableModule folder. Or you can add your own resolving routine in KbMapDriverFile function. |
Hey thanks <3 can you maybe give me some keywords to learn more about why this happens. (Is it because I include #include <ntddk.h>) and maybe what i need to care about when writing my own driver that will be mapped with the kernel bridge framework. Sry for taking your time away and thanks again |
Hm, I don't know why does exactly it happen... Is it a WDM-driver? Maybe it links something from WDF in a linker command line? |
Mapping any driver even the simplest.
auto test = KbRtl::KbRtlMapDriverFile(L"C:\\dummy.sys", L"KBFM"); fmt::print("test {0} ", test);
Produces KbLdrImportNotResolved can someone provide me a dummy driver example or explain to me what this error means and how to fix it?
The text was updated successfully, but these errors were encountered: