Latest published driver updating only on Win11 24H2 client systems

Lately HLK certified and published Nth version of the Windows driver, but it is only updating on WIN11 24H2 clients (This driver HLK tested on Win11 24H2 system).

But it is not updating on Win11 IoT 23H2 systems, instead these systems are getting N-1th version of driver that was published an year ago.

Any idea why Win11 IoT 23H2 systems are not getting latest driver version N?

Thanks

Did you check all of the old versions when you published the update?

Thanks for your response Tim.

When I published the older versions (N-1 version) an year back, they all seem to work on all the systems at that time back in 2024 when Win11 23H2 was the latest OS available. The older version even worked on Win10 IoT back then.

Is there a chance the these 23H2 Iot system are locked-out/disabled by MSFT from updating the latest from WU, in order to make these system upgrade to 24H2 first and then WU.
I checked all WU update configuration they are configured to receive WU updates without any throttling.

3 units of Win11 24H2 systems get the latest Nth version of the driver through WU.
3 units of Win11 IoT 23H2 systems not getting Nth(this is the issue), instead they get N-1th version of the driver through WU.

Thanks,
Prasanna

Sorry, I asked that ambiguously. When you submit a driver package, there are checkboxes for all of the system versions that you support. That gets embedded into the CAT file. Did you check the older versions?

1 Like

Hi Tim,
I think I did that, same as previous submissions.
But I will need to double check one more time to make sure I did not miss anything and update you if I missed anything.

Thanks,
Prasanna



The partner site only provides Win11 24H2 options for publishing.

This is just my thought, let me know if you have any comments on this.
It appears that the the Win11 IoT 23H2 systems are locked from upgrading beyond 23H2, it only WU the N-1 version of the driver now.
To get latest driver which is Nth version from WU, it probably needs to get updated to Win11 24H2 first, which could be a DEPENDENCY for the Nth version of the driver.

BTW, we cannot certify the driver on Win11 23H2 since the most recent HLK tools are compatible with Windows11 24H2 systems only. Also it does not make sense to certify the deriver on Win11 23H2 when Win11 24H2 is latest available already.

Thanks,
Prasanna