-
Notifications
You must be signed in to change notification settings - Fork 70
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
Windows 10 wdk-sys
Driver Compilation and Loading Error
#42
Comments
Hi @Juggle4247. Are you able to reproduce this issue when following the instructions at https://github.com/microsoft/windows-drivers-rs/tree/main/crates/sample-kmdf-driver#sample-kmdf-rust-driver ? One possible reason for this is that the current signing flow in |
Hello, I do not understand what you mean. Did you test this on Microsoft Windows 10? Can you please upload kernel driver template that works both on Windows 10 and 11? This would be great and lot easier for other people. |
I have the same issue, I also could not run it without signing both cat and sys files, but now it says The parameter is incorrect. |
Using the following
(Code taken from here: #32) |
Thanks Matthias again :) microsoft/windows-drivers-rs#42
Got some bandwidth to do some more debugging of this issue and was able to figure it out. @not-matthias 's workaround only works if you are fine using only non-WDF functions. it limits you to what's only available in WDM drivers. The reason it works is because it changes the linker flags to set the entry point to be WDF initialization is causing issues for you folks on W10 because various things in the default config of this crate (as currently available in v0.1.0 in crates.io) default to kmdf V1.33 which only supports W11 21H2 and newer. I've verified that when setting all references to v1.31 results in a correctly functioning sample_kmdf_driver and echo_2. These are the changes I had to make:
Unfortunately, these source patches are required to compile a driver for W10 right now, but should no longer be required once #82 (which is currently my main focus) is addressed. |
Hello friend,
I've noticed that a lot of people, especially in various Discord communities, are discussing an issue with the Windows 10 driver not working correctly for
wdk-sys
. Here's a step-by-step outline of the problem:Steps to Reproduce:
Observed Issue:
On executing the above steps, the following error messages are observed:
Additional Notes:
I'd appreciate any insights or solutions to resolve this issue on Windows 10.
Thank you!
The text was updated successfully, but these errors were encountered: