HBS ED and KB5101650: Issues with keyboard driver and PE Network

[admin]

@al3x,

After replacing Mrxsmb.sys and Ksecdd.sys, I confirmed that PENM runs on my ARM64 computer and that Wi-Fi works properly. Thanks.

Best regards,

[admin]

@Bespoken,

Please try the following version to see if PE Network Manager can run normally.
https://www.easyuefi.com/backup-software...260719.exe

Have a nice day!

Best regards,

[Bespoken]

Partial good results.

ASUS Zenbook
- PE Network Manager started, no error popup, access to wifi
- touchpad unresponsive, keyboard works
(previously adding drivers ialpss2i_gpio2_bxt_p, ialpss2_uart2_mtl, ialpss2_spi_mtl, ialpss2_spi_mtl, ialpss2_i2c_mtl, and ialpss2_gpio2_mtl activated the touchpad)

HP Desktop
- PE Network Manager started, no error popup, no access to wifi, ethernet works
- keyboard and mouse works

HP X360
- PE Network Manager started, no error popup, access to wifi
- touchpad and keyboard works

May need to add some drivers to the build on the HP Desktop to get it working.

[al3x]

Hi,

After replacing Mrxsmb.sys and Ksecdd.sys, I confirmed that PENM runs on my ARM64 computer and that Wi-Fi works properly. Thanks.

was that a typo or does PENM actually run on ARM64? If yes, that would be good news!

Please try the following version to see if PE Network Manager can run normally.
https://www.easyuefi.com/backup-software...260719.exe

PENM also works for me with that updated version, thanks!

[admin]

@Bespoken,

Thank you very much for your prompt and detailed test feedback.

From your test results, it appears that the new version no longer pops up an error message when starting PE Network Manager, confirming that the solution of replacing Mrxsmb.sys and Ksecdd.sys is effective.

Regarding the unresponsive touchpad on the ASUS Zenbook, this likely involves other serial IO or GPIO driver dependencies, but it is difficult to determine exactly which files need to be replaced.

Regarding the HP desktop's inability to use Wi-Fi, this should be because the required wireless network card driver is not installed in the WinRE image.

Thank you again for your continued collaboration.

Have a nice day!

Best regards,

[admin]

@al3x,

was that a typo or does PENM actually run on ARM64? If yes, that would be good news!

It was not a typo. I did indeed use a Windows ARM64 computer for the testing, because my x64 laptop could not reproduce the issue. That might require installing a fresh Windows 11 system.

PENM also works for me with that updated version, thanks!

Glad to hear that.

Have a nice day!

Best regards,

[Bespoken]

Regarding the unresponsive touchpad on the ASUS Zenbook, this likely involves other serial IO or GPIO driver dependencies, but it is difficult to determine exactly which files need to be replaced.

Copilot suggests " with WinPE/WinRE from Windows 11 25H2 (build 26200.8894), the old Meteor Lake Serial‑IO stack (the ialpss2\_* drivers you listed) is no longer sufficient to make the ASUS Zenbook UX3405MA touchpad enumerate. You now need additional Intel Platform Framework (IPF) ACPI + GPIO + HID‑I2C support drivers, because Microsoft changed the WinPE driver baseline in 25H2 and removed several low‑level ACPI bus enumerators that used to be present."

I am exploring the process for injecting those support drivers into the .iso.

Regarding the HP desktop's inability to use Wi-Fi, this should be because the required wireless network card driver is not installed in the WinRE image.

An older version of the winpe.iso did not need that. That PC is ethernet connect and does not need to use wifi. It was only a test to see if the PE Network Manager was working.

Thanks for your response.

[admin]

@Bespoken,

Thank you again for your in-depth analysis.

From the current situation, it appears that Microsoft has made significant updates or underlying adjustments to WinRE. As for the issues we are currently encountering, whether it's the changes in touchpad driver dependencies or network component compatibility, it is still difficult to determine whether they are bugs on Microsoft's part or intentional design changes in the new version.

With that in mind, perhaps the most prudent approach for now is to wait and observe for a while, to see if Microsoft will address or clarify these issues through subsequent cumulative updates or patches.

Of course, we will continue to follow and test your progress on driver injection. If you have any new findings in exploring IPF driver integration, please feel free to share them at any time.

Thank you again for your continued collaboration!

Best regards,

[Bespoken]

The process for injecting the support drivers has been interesting but has hit a road block.

By installing Windows ADK I have been able to develop a script that will inject selected drivers into a new winpe.iso. This would be an alternative to the Add driver step in the create process. For touchpad support it seems that KMDF and UMDF packages, part of the Windows Driver Frameworks (WDF), may be required. These are only available as part of a VisualStudio subscription which I do not have.

My USB mini touchpad/keyboard works, but it is not as convenient as the laptop hardware.

[admin]

@Bespoken,

Thank you for your continued in-depth research and experimentation, especially your approach of developing a script through the ADK to inject drivers, it shows great exploratory spirit.

KMDF and UMDF are two driver development models under the Microsoft Windows Driver Framework (WDF). They are toolkits and frameworks that help developers write Windows drivers, but they are not drivers themselves. Therefore, they are not something you need to inject into WinPE. WinPE, as a pre-installation environment, already includes the necessary runtime components to run these framework drivers and does not require additional injection of development frameworks.

The core of the current problem lies in the missing or incompatible drivers or services that the hardware drivers depend on. It is entirely possible that this is a BUG in Microsoft's latest WinRE, rather than a lack of driver development frameworks. I would suggest that you temporarily use a USB mini touchpad/keyboard for now, and wait for Microsoft's next update to see if the related issues are resolved.

Have a nice day!

Best regards,