How to include a driver in a Windows Provisioning Package

adr 46 Reputation points
2024-05-13T11:19:48.72+00:00

Hi,

We have implemented Autopilot in our environment. However, we have found some user devices that have either a corrupt OS or recovery partition so fail when trying to RESET and redeploy to a new user.

One solution we have in these case is to install a fresh Windows OS from the Microsoft Website (https://www.microsoft.com/software-download/windows11) and ask users at remote offices to just reinstall. Autopilot should configure these devices when they reach the oobe and connect to the internet.

We have mostly surface devices (Pro 6/7/7+/8, Laptop 2/3/4/5, Laptop Go 2) which work with no issues when installing from the USB (created from the link above).

Now we have Surface Laptop Go 3 devices. When building from the USB it fails, as the Windows 11 23H2 image does not contain the WLAN drivers to connect to the network.

I have tested injecting the WLAN drivers into the install.wim and replacing whats on the USB, but is it posssible to include a driver in a provisioning package? I've seen it done on some older documentation , but not on any newer (2020+) docs when using the Windows Configuration Designer. Is this still possible as its alot easier to send a ppkg file to our remote office (where they do not have technical staff)

Windows Autopilot
Windows Autopilot
A collection of Microsoft technologies used to set up and pre-configure new devices and to reset, repurpose, and recover devices.
417 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Pavel yannara Mirochnitchenko 12,061 Reputation points MVP
    2024-05-14T16:09:58.08+00:00

    Is that Surface Laptop Go 3 so new, that recent Windows OS media does not have built-in driver for it? Sounds interesting. Have you tried to open a case about this? Or maybe wait for next month Windows OS media update, if you use creation media tool for this? I am suprised if that latest Windows 11 media does not cover driver for Microsoft's own hardware model.

    0 comments No comments