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

[Bespoken]

My ASUS Zenbook 14 requires drivers to be added to the WinPE boot disk as the keyboard and WiFi6E does not function without them. The drivers were added to the Emergency Disk rebuild with this new beta version, but the keyboard does not work, and the PE Network start but does not present the network window. Same issue when running from either the Boot Menu or the ED.

Any suggestions?

[admin]

@Bespoken, Version 5.9 does not include any changes to the features related to creating WinPE, so I can only recommend that you ensure the correct drivers are injected when creating WinPE.

Additionally, I recommend that you do not select the “Download WinPE components” option when creating WinPE. Doing so will create WinPE directly from WinRE.wim, which typically includes the drivers for the current computer.

[Bespoken]

Extensive testing has identified that the problem started after Windows Security update (KB5101650) was installed yesterday.

No variation of WinPE build works:
- do not Download WinPE Components
- Download WinPE Components
- use WPE.OPE
- HBS V5.9 or V5.8

The previous ED version created prior to the Windows Security Update works fine.

Seems next step will be to examine the drivers in the failing WinPE compared to those in the working WinPE, and if some additional drivers need to be included. Having a batch load for drivers would be very handy.

[admin]

Extensive testing has identified that the problem started after Windows Security update (KB5101650) was installed yesterday.

No variation of WinPE build works:
- do not Download WinPE Components
- Download WinPE Components
- use WPE.OPE
- HBS V5.9 or V5.8

The previous ED version created prior to the Windows Security Update works fine.

Seems next step will be to examine the drivers in the failing WinPE compared to those in the working WinPE, and if some additional drivers need to be included. Having a batch load for drivers would be very handy.

Technically speaking, Windows Security updates should not affect the WinPE created using "Download WinPE Components" and WINPE.OPE, which is what confuses me. On the other hand, as long as the correct drivers are injected when creating the WinPE, the corresponding hardware should work properly.

[Bespoken]

The only difference with the drivers included in the old and new WinPE is the versions of acpi.inf

Old WinPE: 10.0.26100.8737
New WinPE: 10.0.26100.8875

On another PC with the latest Windows update and a recreated ED, the PE Network Manager also fails. It works with an older ED.

Next test, extract acpi.inf from a mounted old Windows System backup and add it to the build of an ED. Tried this with an created ED with Download WinPE Components not selected, and one with WPE.OP. Both had the same problem.

I am out of ideas. Any suggestions?

Maybe these post should be moved to a separate thread.

[al3x]

Maybe these post should be moved to a separate thread.

Good idea! I have moved the posts related to this issue to this new thread

[Bespoken]

Thanks for moving the posts @al3x.

Some additional testing.

1. Tried an ED build with "Automatic driver injection" deselected and WPE.OP used. Same problem
2. New ED build on a third PC with the latest Windows updates. The PE Network Manager also fails here, while the version prior to the WU worked.

[al3x]

I'm not sure about your keyboard driver but I can confirm the problems with PE Network Manager.
It starts up and then just quits without any error message:



That's from a fresh HBS rescue image with Win11 26200.8875.
Something seems to be broken there, hm...

[al3x]

On a side note: I also get this error popup the first time I start PC Network Manager.
But this is nothing new and happened in earlier versions as well. PE Network Manager still used to start fine.

[Bespoken]

Yes, I reported that error popup some time ago, but that code is from a 3rd party.

Would like to hear if anyone has been successful with a new ED build after the latest WU was installed. I expect many will need networking for ED/BM. Is this isolated or widespread?