systeminformer: Unable to load kernel driver (not yet supported on this kernel version)

ISSUE DESCRIPTION HAS BEEN REWRITTEN BY MAINTAINER @jxy-s:

image

For the latest kernel support, ensure you are on the latest Canary build of System Informer: Help > Check for updates > Canary > Check

This issue is for requesting support for new Windows kernel versions. The kernel driver will refuse to load on a Windows operating system running a kernel (ntoskrnl.exe) version that it does not recognize. This behavior is by design. The driver relies on specific data that must be updated and published to support new kernel versions. This data includes internal offsets within the operating system, which the driver uses to provide extended capabilities and system inspection. The data is signed using a cryptographic algorithm and verified by the driver before it is loaded. This signing process ensures that the data has been produced by the project maintainers and not by a third party, preventing potential misuse or abuse of the kernel driver.

To request support, please post a screenshot of the error dialog (see example above).

Please note: Support for new kernel versions may be delayed for various reasons. Usually, Microsoft makes the necessary information public within 24 hours of a new kernel version being released. However, on rare occasions, this information may take days or even a week to appear. In some cases, Microsoft may not provide sufficient information, requiring more effort on our part to update the data. Additionally, delays may occur if the maintainers are occupied with other tasks. While we typically respond to new kernel versions within 48 hours of their release, there are times when it may take up to a week. We are working on automating this process to improve our response time.

We appreciate your efforts in requesting support for new kernel versions and ask for your patience while we work through the necessary updates.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 2
  • Comments: 277 (178 by maintainers)

Most upvoted comments

Support for recent kernels was added here: https://github.com/winsiderss/systeminformer/commit/2375ee344ef8f64c41e34dc9189ec4a44b736681

As some of you might be aware we’re working on sorting out some issues with the updater and versioning, once that is taken are of we’ll publish another build with the recent kernel support. All of this effort is in support of an official fully stable release and version 3.1.x - thank you for your patience and understanding.

I would like to inform everyone involved in this thread that the next build will include significant changes to dynamic data. These changes were necessary to better support the automation of dynamic data generation. I have gone through and generated the dynamic data manifest for a large number of supported kernels.

As a result, we will be trialing support for ntkrla57 and preview builds 🎉. However, please note that for preview builds, Microsoft may not always provide the information needed to generate the dynamic data. Our long-term goal is to fully automate both the generation and validation of dynamic data, but we still have some work to do in fully vetting the current tooling.

That being said, since there are significant changes and a regeneration of dynamic data, there is a possibility that some kernels may have been missed or other issues could arise. I appreciate your patience as we work through these.

A new build will be available soon™️.

10.0.26100.1455, 10.0.22621.4036, 10.0.20348.2652, 10.0.19041.4780, 10.0.17763.6189, 10.0.14393.7254, 10.0.10240.20747 - https://github.com/winsiderss/systeminformer/commit/390c20cdee82c49e23f034dde2239479c1574f42

3.1.24232.0 - Help > Check for updates > Canary > Check - 👍

10.0.22621.3296, 10.0.20348.2340, 10.0.19041.4170, 10.0.17763.5576 - https://github.com/winsiderss/systeminformer/commit/fe48085c0642d2acfcda3bacffaf0f285f6b9564 3.0.7479 - Help > Check for updates 👍

https://github.com/winsiderss/systeminformer/commit/137cc3a698d5960d68f63b2968a5142e25023f9c adds support for 10.0.19041.3393 and 10.0.22621.2215

Will be in next build 👍

What is this dyndata thing for? … Maybe for communication between the user-space part of SI with kernel-space part? But why is it needed? What purpose it serves?

They’re undocumented offsets used for both protections and APIs from the client: https://github.com/winsiderss/systeminformer/blob/4c28c8f7ba396eab1fbc13960e9731203bd60f5d/KSystemInformer/include/dyndata.h#L31-L75

What would happen if it was not there? What are alternatives for it?

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.

Why is it needed to be Windows version specific?

Because they’re undocumented offsets that are version-specific.

Apologies for the inconvenience here folks, the back end was moved around and broke the tooling - it wasn’t picking up new platform support data in a timely manner. This has been fixed and I’ve just committed a chunk of updates, will be in the next build 👍 - https://github.com/winsiderss/systeminformer/commit/b75b9d964fb06fa6da9c281aca56b6af16d7b989

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.

10.0.22621.3527, 10.0.19041.4355 - https://github.com/winsiderss/systeminformer/commit/fc042be5774f278f515f32682b8f41bfd45a9b70

3.0.7579 - Help > Check for updates - 👍

10.0.19041.4123, 10.0.22621.3235 - https://github.com/winsiderss/systeminformer/commit/e904d245241276a6e0677d1283a53a6a6fc63d69 3.0.7474 - Help > Check for updates 👍

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: https://github.com/winsiderss/systeminformer/issues/1823#issuecomment-1693053377

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.

btw, there are now extra Hotpatch updates (updates that don’t require reboots, but require extra license) for Windows 11/Server 2025 24H2

Hotpatch KB5058497 (OS Build 26100.3981) https://support.microsoft.com/en-us/topic/may-13-2025-hotpatch-kb5058497-os-build-26100-3981-23bc4731-d39a-4478-8b4f-b64737fc2371

There is also an First Out of Band Update:

Hotpatch KB5061258 (OS Build 26100.3983) Out-of-band https://support.microsoft.com/en-us/topic/may-16-2025-hotpatch-kb5061258-os-build-26100-3983-out-of-band-6826d54b-8acd-4bc1-b8bf-c839ca8e77a0

Is your automatic fetching/updating able to include them?

Thanks - this is already on my radar.

From what I understand so far, the current hotpatches are limited to function-level changes and some global state. There’s no indication yet that Microsoft will ship hotpatches that alter internal structures in a way that would impact our dynamic data.

None of the files currently being hotpatched are relevant to our use of dynamic data. Even if they are in the future, it shouldn’t be an issue - dynamic data is matched against the image’s timestamp and size. To my knowledge, this mechanism is resilient to hotpatching: a hotpatched image remains mapped with the same values, so loading dynamic data should continue to function normally. The real risk would be if Microsoft changes the layout of internal structures that dynamic data targets, but I haven’t seen evidence of or intent to do that so far. If that does happen, we can temporarily disable dynamic data support for affected hotpatched versions while we work on an appropriate solution.

So at this time, I don’t see a need for System Informer to explicitly track or handle hotpatches. That said, I’ll continue monitoring them and will adjust as needed if they begin affecting structures we care about.

switch to the canary channel via Help -> Check for updates -> Canary -> Check as this version is already supported here.

And in a few minutes new Windows updates get released and the tool needs a new update.

10.0.26100.1591, 10.0.22621.4111, 10.0.19041.4842 - https://github.com/winsiderss/systeminformer/commit/c1798de12a7115f5ff11f6138ca89d0596a439c0

3.1.24244.0 - Help > Check for updates > Canary > Check - 👍

Could someone explain what is the deal with so many people having this error message because I have it too. I even tried SystemInformer on a fresh Win11 VM, and the same error occurs there. (This is the error from my host OS) image Is my Windows version out of date, or is it my kernel, or system informer?

The System Informer driver accesses undocumented windows Kernel structures, these may change with any new build of the kernel in a unforeseeable way, and using outdated offsets can easily lead to a BSOD, and that is not good. That said, these structures do not change that often, System Informer simply opts to be certain it will not cause a BSOD and only uses offsets it knows are valid for the current build. The alternative would be to assume the last known offsets are still valid and just YOLO it hoping for the best. The users would then come here and post that System Informer caused a BSOD instead of coming here and complaining about this error message. So being a everyone is responsible for them selves and sure give anyone the means to shoot themselves in the foot type of person I would greatly appreciate an option to dismiss the error message and try the last known offsets, if it crashes it crashes. So I would like this error to be turned into a dismissable warning. That said I already had to once re install a PC after a System Informer driver related BSOD as it caused File System corruption and it was a not yet backup ed new machine, sooo… may be being able to dismiss the Warning is not the best idea in the end LOL I think what one could do is to try to test if the last known offsets are valid, for example testing addresses read from the structures first with MmIsAddressValid, and alike… so that the users would be offered the option to dismiss the warning only if its exceedingly likely that the offsets will still work. I believe this would be a great usability improvement to System Informer, especially for users of insider builds.

I would appreciate an official statement on this suggestion if implemented it would eliviate a lot of the pain of users in the insider channels.

The suggestion to use MmIsAddressValid or to otherwise “try” validating internal offsets at runtime is fundamentally misguided. It reflects a misunderstanding of the problem space and demonstrates a disregard for the operating environment of the kernel. As we have communicated multiple times, the design of the System Informer driver and its dynamic data structure intentionally prevents loading or using unauthorized dynamic data with the associated kernel.

System Informer fully acknowledges the privilege of having a Microsoft-signed kernel driver, and we take every measure to uphold the architecture and security of the operating system. Allowing the bypass of this integrity check would compromise that privilege and the trust in the system.

Regarding support for preview builds, we are actively working on automating the process of generating, vetting, and signing dynamic data. At present, due to time constraints, we are unable to support all kernel builds and have chosen to limit the number of kernels we can accommodate. Once automation is in place, we aim to support a wider range of kernels. However, even with automation, there will be some delay in making data available for the latest builds, although this should be significantly reduced.

As the code is open source, you are free to modify it to bypass these checks if desired. You can build your own driver accordingly. If you cannot sign the driver, you will need to configure your operating system to load unsigned drivers. There are also instructions available for self-signing, which also requires building a new driver.

@DavidXanatos, this thread is not intended for suggesting changes, so I will mark your suggestions and comments here as off-topic. You’ve made suggestions on several occasions in different threads, and a more suitable place for this discussion would be issue #1963. I’m also happy to continue this conversation with you personally. Please feel free to email me or send a direct message on Discord.

3.1.24184.1 - Help > Check for updates - 👍

uninstall it and install system informer.

10.0.22621.3593, 10.0.20348.2461, 10.0.19041.4412, 10.0.17763.5820 - https://github.com/winsiderss/systeminformer/commit/4af54b68bdc77b144d3f7de34ba68aeaedc94584

3.0.7643 - Help > Check for updates - 👍

10.0.22621.3527 ntoskrnl.zip

image

10.0.22621.3374, 10.0.19041.4239 - https://github.com/winsiderss/systeminformer/commit/3de9d4bf4bb95e598fa4be6fb726f7ec6098ad71

3.0.7546 - Help > Check for updates - 👍

19041.4235

this is a Release Preview build which is not supported so this is expected.

the + and ++ show that both have different driver usage levels while ++ is the best

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

RP channel on Windows

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 can confirm that with latest SI driver loads on 19041.3393. Thank you very much.

SI build 3.2.25011.2103

@chrcoluk your build is out of date, switch to the Canary channel (current version is 3.2.25198.223). That kernel version is supported on the Canary channel. Did you happen to miss the instructions in the message box?

Image

Is it possible for you guys to auto build kernel driver, and push it out as a modular update so its always done right away and not without changing all of system informer?

It’s on the todo list to serve the dynamic data out-of-band with updates to the project as a whole. But I haven’t had time to go do that work.

Driver support is delayed due to instability on master, we’re working on getting that sorted. Thanks for your patience.

[Window Title] System Informer

[Main Instruction] Unable to load kernel driver

[Content] The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.

Windows 11 24H2 10.0.26100 Windows Kernel 10.0.26100.2605 System Informer 3.1.24298.0 Release

00-8664-4f6c47b9-0144f000

[ ] Don’t show this message again [ОК]

also [Window Title] System Informer

[Main Instruction] Unable to load kernel driver

[Content] The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.

Windows 11 24H2 10.0.26100 Windows Kernel 10.0.26100.2605 System Informer 3.1.24318.0 Canary

00-8664-4f6c47b9-0144f000

[ ] Don’t show this message again [ОК]

You’re not on the latest Canary build, but latest is also not working; this is a known issue as the build method is undergoing some changes (as stated in previous comments by the maintainer). Once a new Canary build surfaces with the new build method intact, we should see the kernel-mode driver functioning normally again.

can’t you simply create a new branch based on version 3.1.24333.0 (c5e25ca4) merge the kph update dyndata commits to support december updates and release a new version based on this branch?

// Edit: Merry Christmas to the whole team 🎄🎅

The ability to produce a build is blocked by some work @dmex is doing. Once he has straightened that out a new build will be available.

Recent KB Update (December 10, 2024—KB5048652) Seems to have broken kernel compatibility. Here is the error window below, looks like new compatible SI build is rolling soon, however, I thought I’d let you know in case you were not aware… Thanks!

image

I noticed that the latest DynData are not for the latest ARM64 Win11 yet:

grafik

Added a few more ARM64 kernels in these commits: https://github.com/winsiderss/systeminformer/commit/f247ebc4e7e09bdaa853fadefeb1fc13e11413bf https://github.com/winsiderss/systeminformer/commit/bf387c777ba21242fe645d84ecc5160707210578

Unsure exactly why those were not reported to me automatically, will investigate that - but they’ll be available in the next build 👍.

Also a small OT request: would it be possible to link with every canary release the exact git tag it was built from? Or may be that’s already the case and I just don’t know where to find that info LOL

In check for updates dialog you see the short git hash

image

image

Does this mean that you will be able to support Insider channels, such as Release Preview, as well?

Yes, as long as Microsoft provides the necessary information. There are two scenarios to consider. First, with the automated metadata we currently have access to, testing shows we achieve around 90% coverage of kernels. However, in some cases, we may need to manually retrieve the kernel binary, either through user submission or by other alternative means.

@User4716

Btw, is the start type supposed to be Disabled?

Yes. This is the correct settings. The start type is set to disabled after the driver loads because we don’t want the driver using any resources unless the application is running or any issues or bugs with auto-start from crashing the system.

Windows 10 22H2 also got a new preview update:

@MagicAndre1981

We added support for CI to automate new builds but Microsoft hasn’t published any metadata for those versions.

Btw, is the start type supposed to be Disabled?

same for me, so looks like default behavior

10.0.26100.1252, 10.0.19041.4717, 10.0.14393.7155, 10.0.10240.20708 - https://github.com/winsiderss/systeminformer/commit/d6a21858b530b101cc74faafc40e7325594aa1f9

10.0.22621.3958 - https://github.com/winsiderss/systeminformer/commit/ae1dd2f411b05a9344fdf089865a973b9b0413e0

3.1.24208.0 - Help > Check for updates > Canary > Check - 👍

10.0.26100.1150, 10.0.22621.3880, 10.0.20348.2582, 10.0.19041.4648, 10.0.17763.6054 - https://github.com/winsiderss/systeminformer/commit/16df3a4dc5d71dba4a16b59e97c725335f6d3b9c

3.1.24192.0 - Help > Check for updates > Canary > Check - 👍

Btw, do you also need the ntkrla57.exe which is used for systems that support Intel 5-level paging?

Eventually, but now right now. The driver supports it but the dynamic data format doesn’t - so YMMV on LA57. I’m hoping to eventually move all the dynamic data handling to a service which will solve this in a more elegant way.

i have the same problem, i have win 11

@sequencerr switch to the Canary channel.

Windows Server 2022 x64:

https://msdl.microsoft.com/download/symbols/ntoskrnl.exe/3A6EB0D31047000/ntoskrnl.exe
https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/C339CA26E8E26BB7F4C9BB7B8244A46A1/ntkrnlmp.pdb

Please keep comments on this issue on-topic.

10.0.17763.5202 - 3.0.7412 -> Help > Check for updates 👍

works fine 👍

ok, one 1 RS5 it it not working, telling me to do a reboot which I did but error is still the same:

image

After deleting the ksi.dll-old file error is gone (without any reboot).

ksi.dll-old is marked for deletion on reboot since it must remain loaded. My speculation is that one machine had the pending rename operation key corrupted or reverted. Which resulted in the file not being deleted. I can add some logic to try to delete the file if somehow the OS leaves it around after reboot. That should serve as a fallback without needing manual intervention.

I build mine from scratch with the exact settings as intended.

You need to follow the instructions here for generating your own keys for signing. The driver restricts callers unless you have the correct signatures. You can do plugin development (with restricted access), but realizing now that is somewhat broken with the new dyndata signing workflow 🤔.

Windows 10 21H2 LTSC x64 Kernel 10.0.19041.3693 System Informer 3.0.7310

Error kernel driver not supported on this kernel version.

I agree with earlier idea for error box to link to this issue, maybe it could even auto submit details.

Yep, thanks for calling that out @MagicAndre1981 - the setting names were normalized. Rather bite that bullet now then when we do a full release. Thanks.

Updated here: https://github.com/winsiderss/systeminformer/commit/bc98048099421785ea4a37670d7b57bfb924cda5 Available in: 3.0.7310 - Help > Check for updates

Support was added here: https://github.com/winsiderss/systeminformer/commit/d44e4d04651eafacc240e351482939f068f7c7d4

3.0.7270 is available with that commit.

@MagicAndre1981 send me 10.0.17763.4974 please. I’m looking into the others now.

ntoskrnl_17763.4974.zip

And race starts again with new updates:

image

Is it normal to have to reboot to replace ksi.dll?

Yes, but generally it doesn’t update. ksi.dll is a library used by the kernel driver. It can not be unloaded. The purpose of this DLL is to extend the kernel and provide functionality that would otherwise be unsafe or impossible. The updater will check the hash of the DLL to know if it needs replaced, if it does a reboot is requested for the update to finish.

We’re working on build pipelines. Two things here:

was not offered via updater

This is intended, deployment is disabled while we’re testing.

so I extraced the zip and this is the same error

Signatures files (.sig) aren’t in the zip. Use systeminformer-3.0.7254-setup.exe if you want, but probably best to wait until we’re done testing. These builds will be pulled shortly.

7251 works now fine in 17763.4851 with full driver support (++ in title)

10.0.22621.2361 and 10.0.19041.3516 are both on my radar, waiting for symbols to be published 👍

I’m not seeing a new build for Server 2022 yet.

@MagicAndre1981

I selfcompiled it at rev.1750 and now get this error message:

Could you try another build with the latest commits? I improved the error messaging so we can see the actual error code instead of just the localized string. My guess is you built yourself using your own signing keys outlined here. I now recognize that information is incomplete, I’ll update it, but I think you may have not rebuilt the dynamic data using your signing keys (.\tools\CustomBuildTool\bin\Release\CustomBuildTool.exe -dyndata). Note that both the dynamic data, kernel driver, and the user mode binaries need rebuilt after you generate and place your developer keys.

@JJRousseau

I’m on 10.0.22621.1928 but it seems to think it’s a preview build.

We have seen in the past that preview build and the kernel file version can diverge. My guess is your kernel version is actually 10.0.22621.1928 but the OS reported version is >10.0.22621. See the following, which checks the “OS reported version”, that might be different than what we print as the “Kernel version”: https://github.com/winsiderss/systeminformer/blob/8d8843eebfef43334c2eef60e91125c9d19a9538/phlib/global.c#L190-L199

I’ve updated the message box information displayed there to include more information about the environment in which the error occurred, here: https://github.com/winsiderss/systeminformer/commit/8d8843eebfef43334c2eef60e91125c9d19a9538

@badjawe

Since windows updates kb5030183 and kb5030180, I have the same issue

Based on that error message in the window, I think you might be running an older version. I’m also not sure what HKLM\System\CurrentControlSet\Control\WMI\Security\... has to do with this?

Latest prod version is 10.0.22621.2283 Update your system.

3.0.7148 fixed it on 19045.3448, but NOT for 17763.4851

Thanks for letting me to @poqdavid - I’m grabbing the new versions now.

@MagicAndre1981 when I was scraping to rebuild the offsets I missed three builds: 10.0.17763.4499 10.0.17763.4644 10.0.17763.4737

I just went over them and the offsets didn’t change from 10.0.17763.4377 - I updated dyndata here: https://github.com/winsiderss/systeminformer/commit/f733df42b4f20f9e938303e4231403d0fd29bd95 - will be in next build 👍

Thank you @MagicAndre1981 . After manual Windows update check I’m on .3393 too.