Skip to content
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

Failed to Map Driver #1

Open
null-lnp opened this issue Apr 9, 2024 · 5 comments
Open

Failed to Map Driver #1

null-lnp opened this issue Apr 9, 2024 · 5 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@null-lnp
Copy link

null-lnp commented Apr 9, 2024

After boot, valthrun driver fails to map with Error: Mapping callback has never been called. I've checked sigs on bootmgfw.efi, seems all is ok but still doesn't seem to work.

For context, after fails, F10 doesn't work either and I'm forced to remove USB and manually turn off my computer.

SB is off
TPM is off

error-valthrun

@WolverinDEV
Copy link
Member

Hey,
what's the output of winver?

@null-lnp
Copy link
Author

null-lnp commented Apr 9, 2024

Hey, what's the output of winver?

20H2 (OS Compilation 19045.4170)

@null-lnp
Copy link
Author

null-lnp commented Apr 10, 2024

On VM (22H2 OS Compilation 19045.4170) the following happens;

Tested on both valthrun-driver.sys and my own crafted driver with no imports, etc. both had same result.

image

@WolverinDEV
Copy link
Member

null address reference is an interesting error 🤔
I'll have a look

@WolverinDEV WolverinDEV added bug Something isn't working good first issue Good for newcomers labels Apr 11, 2024
@null-lnp
Copy link
Author

null address reference is an interesting error 🤔 I'll have a look

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants