Problem

We kept getting the same issue after reset: no WiFi in OOBE. On some HP models, touchpad and audio were also missing.

In a distributed endpoint setup, local IT staff handle resets close to users. When WiFi is missing, Autopilot cannot continue and the device needs escalation. That turns a short task into a long delay.

Constraints

  • Windows 11 24H2
  • HP ProBook and EliteBook devices
  • Intune + Windows Autopilot
  • Distributed environment with local IT support

Decision

  1. Reset a test HP laptop with a standard Microsoft ISO.
  2. Confirmed WiFi adapter was not usable in OOBE.
  3. Confirmed touchpad/audio issues on the same model group.
  4. Verified that enrollment resumed only after a working network.
  5. Cross-checked driver servicing method against Microsoft guidance.

Implementation

  1. Download a clean Windows 11 ISO from Microsoft.
  2. Run my script to inject targeted HP drivers into install.wim.
  3. Replace sources\\install.wim on the USB media.
  4. Reset device using the updated USB.
  5. Continue enrollment and verify status in Windows enrollment.

Outcome

.\inject-wifi-drivers.ps1 -ISOPath "C:\\ISO\\Win11_24H2.iso" -OutputPath "C:\\ISO\\Modified"

# Full script: https://github.com/Thugney/eriteach-scripts/blob/main/deployment/inject-wifi-drivers.ps1

Trade-offs

  • Inject real .inf drivers, not just setup EXE wrappers.
  • Be careful with broad /Recurse driver folders. It can bloat the image fast.
  • Test one model family first before rolling to all sites.
  • Keep a fallback USB in case one model needs an extra Softpaq.