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
Unable to load kernel driver (not yet supported on this kernel version) #1823
Comments
I have the same with I assume it is related to recent |
I only have
I'm adding Windows Server 2022 offsets soon. |
E-mail sent. |
Thanks for getting me the build @ge0rdi - like you mentioned in the email symbols are also not yet published for 3391 yet. Once they are I'll make sure dyndata gets updated. @MarekKnapek I added dyndata for Server 2022 here: 03f5c8c - it'll get picked up in the next build |
Microsoft released KB5029331 first as 19041.3391 and 2nd version is 19041.3393 in Release Preview/Insider version which is now also releaded to public in version 3393. |
Thank you @MagicAndre1981 . |
ok, on 1809 LTSC 17763.4737 I also miss the ++ , so no driver is loaded for System Informer version 3.0.7029, but I dont get the messagebox |
Out of curiosity: What is this |
They're undocumented offsets used for both protections and APIs from the client: systeminformer/KSystemInformer/include/dyndata.h Lines 31 to 75 in 4c28c8f
The driver can't function without them. They're required for the protections to function correctly. The old driver would load without them, but it was arguably mostly useless without them. There was some functionality without them, but it was a bit non-obvious why some things would work and some wouldn't. So, during the rewrite we opted to make it a requirement. This come with the benefit that we know where we don't have support/visibility. Obviously the cost is we have to work harder to have more compatibility.
Because they're undocumented offsets that are version-specific. |
I hope this helps. I am experiencing the same issue after installing KB5029351. Before this update, I only got that message once when I installed Build 3.0.7029, but now I get it every time I launch System Informer. |
137cc3a adds support for Will be in next build 👍 |
I can confirm that with latest SI driver loads on |
@MagicAndre1981 when I was scraping to rebuild the offsets I missed three builds: I just went over them and the offsets didn't change from 10.0.17763.4377 - I updated dyndata here: f733df4 - will be in next build 👍 |
Thanks for letting me to @poqdavid - I'm grabbing the new versions now. |
22621.2283 |
Symbols are not yet available for |
d859dad will be in next build 👍 |
as expected I also get the warning again for 1809: and 1904x.3448: |
@jxy-s out of curiosity when you guys update System Informer for newer kernels does it lose its compatibility with older kernels? |
No, it doesn't break compatibility. We support older kernels. We support release builds for Win10+ x64/ARM64. The supported kernel versions are specified in https://github.com/winsiderss/systeminformer/blob/master/kphlib/kphdyn.xml
We do not yet support preview builds. Updates to those kernels are too frequent for me to keep up with manually. I'm hoping to finish some automation eventually to support them. |
I noticed I have an older SI Rev.6806 running on another Win10 17763 and here I see the ++ so driver is loaded on 17763.4851 🤔 🤷♂️ |
See: #1823 (comment) Dyndata format had to change and I went to rebuild all the offsets using some tooling. I missed a few versions. I've corrected it already, once a new build is out that kernel will be supported. Older releases supported it with the older format. But there were bugs. |
the + and ++ show that both have different driver usage levels while ++ is the best |
3.0.7148 fixed it on 19045.3448, but NOT for 17763.4851 |
Windows Server 2022 x64 10.0.20348.2402
|
10.0.22621.3527 |
|
Is that insider version? |
26100.x will be 24H2, but they finished it already so that OEMs can preinstall new Devices with that version. |
Just as a little tidbit of info for those who may have been on the release channel like I was, Version 3.0.7579 is on the Canary update channel so if you currently have 3.0.7578 installed and are getting this error, go to Help > Switch Update Channel > Canary and allow it to check for updates and authorize the install which will automatically download 7579. Hope this helps anyone who may have still been stuck on this. In my specific case, this applied to Windows 11 23H2 with Kernel version 10.0.22621.3527. Hadn't seen this mentioned so I figured I'd help out for the sake of people maybe googling the issue. |
Windows Server 2022 x64:
|
|
latest version is 7643 |
check for update doe snot give me 7643 also not on https://systeminformer.sourceforge.io/downloads |
change update channel to canary. |
how i change the channel to canary? |
and with process hacker 2? |
uninstall it and install system informer. |
There is a hotfix/Out of Band Update for 1809: KB5039705 (OS Build 17763.5830) Out-of-band |
Steps preceding reproduction:
Steps to reproduce:
Details:
b09759778099468188434408f929d675ce289b97
.ae6b8522ca5205b4cef89606ea6c7d043e81dc4f
.4ffc26a940dffa2931923c345eb9824f76dcfca4
.ecbad74c2629f4dd516c35887b8e5d0b7032b135
.[1]
[2]
The text was updated successfully, but these errors were encountered: