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

[MarekKnapek]

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

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.

[DARK7BEA5T]

please also mention how will it be fixed?
will i need to update app or windows?

[MagicAndre1981]

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.

[kotenok2000]

ntoskrnl.zip

[jxy-s]

10.0.26100.2605 was added yesterday: b71dc84

Holding on a build, we're finishing up some other work, will have another build soon.

[SPIKEYPUP]

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!

[thunderstone135]

KB5048753 Windows 11 Insider Beta Build 22635.4655 (23H2) - December 13, 2024

Even if I update to 3.1.24333.0, it won't work.

systeminformer/kphlib/kphdyn.xml

Lines 1358 to 1359 in 277a0a5

	<data arch="amd64" version="10.0.22621.4541" file="ntoskrnl.exe" hash="61b9596eae4484650cbc8fd0add025624074eeb2f89167c369c0cf09d36b7aee" timestamp="0x95494f9c" size="0x01047000">8</data>
	<data arch="amd64" version="10.0.22621.4541" file="ntkrla57.exe" hash="7acf1f634fcfe44d64eca9c44b875a5a126724bfedbcb7393ce2844af762836b" timestamp="0x3953b760" size="0x01041000">13</data>

Because it doesn't cover 22635.4655 or 22621.4655 according to the commit above.

systeminformer/kphlib/kphdyn.xml

Lines 1382 to 1383 in b71dc84

	<data arch="amd64" version="10.0.22621.4601" file="ntoskrnl.exe" hash="ab8ee9b6ed2670d5ceee6bde0a52a79e1c3c2e376bee2d17e7bedc84947d0ebe" timestamp="0x3abd2e6d" size="0x01047000">8</data>
	<data arch="amd64" version="10.0.22621.4601" file="ntkrla57.exe" hash="dc5ec2787e95c31de5cda17b210d784158da002a41f4558c123ebdfde63774c6" timestamp="0xf5b4b219" size="0x01041000">13</data>

I hope the latest commit gets updated to cover 22635.4655 or 22621.4655.

[stong]

Windows 10 21H2 10.0.19044
Windows Kernel 10.0.19041.5247
System Informer 3.1.24333.0 Canary

I'm not a maintainer so I have nothing else useful to add, but figured I'd chip in with a report.

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!

Same here.

[RafiOlo]

When will it be fixed?

[jxy-s]

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.

[MagicAndre1981]

can't you simply create a new branch based on version 3.1.24333.0 (c5e25ca) 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 🎄🎅

[jxy-s]

That would require undoing work elsewhere. @dmex is making changes to the pipelines we use for releasing. I would rather not undo his work there.

If it were only me I wouldn't put master or our pipelines in a state that prevents us from releasing. But I'm not the only maintainer. We appreciate your patience while this work gets completed.

[MagicAndre1981]

I get a new error (0xc000000d) with latest version:

[Main Instruction]
Unable to load kernel driver

[Content]
Unable to restart.

Einem Dienst oder einer Funktion wurde ein ungültiger Parameter übergeben. (0xc000000d)

Windows 10 22H2 10.0.19045
Windows Kernel 10.0.19041.5247
System Informer 3.1.24360.0 Canary
Process State 0x000003fa

this happens under Windows 10 22H2 and also happens after a reboot.

[ge0rdi]

this happens under Windows 10 22H2 and also happens after a reboot.

Happens on Windows 11 24H2 too :(

[Giantvince1]

Here's the English version of the first dialog:

I'm on the latest GE release of Win11 24H2 IoT LTSC, kernel 26100.2605. Just applied the updated build seconds ago, so I know I'm on latest Canary.