> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/foundry-deploy/driver-pack.md).

# Select a driver pack

On **Drivers**, the third step of the wizard, you choose where Foundry Deploy gets the drivers it adds to Windows for this device.

<figure><img src="https://64695594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdn0pr5zia6oG2DU1R1Pn%2Fuploads%2Fgit-blob-ad6f1101da0a61a7a9f0cb356b43ed5c9ef7b2a8%2Ffoundry-deploy-driver-pack-01-selection.png?alt=media" alt="Drivers step with Dell selected as the driver source, and a model and a version chosen"><figcaption><p>Choose the driver source, then the model and the version when the source needs them.</p></figcaption></figure>

## Choose a driver source

1. Check the pre-selected **Driver source** against the table below and change it if needed.
2. For a manufacturer source, check **Model**. It must name the device in front of you.
3. In **Version**, keep the pre-selected pack version unless you were told to use another one.
4. Select **Next**.

| Driver source                               | What you get                                                                                                                                  | Pre-selected when                                         |
| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| **None**                                    | No drivers are added. Windows uses the drivers it already contains.                                                                           | The device is a virtual machine                           |
| **Microsoft Update Catalog**                | Drivers for the storage controllers, disks and network adapters detected on this device. Nothing else: no graphics, audio or chipset drivers. | The device model has no pack in the manufacturer catalogs |
| **Dell**, **Lenovo**, **HP**, **Microsoft** | The manufacturer's driver pack for the model and Windows version you select. **Microsoft** covers Surface devices.                            | The device model has a pack in that catalog               |
| **Custom drivers**                          | A driver set your administrator added to the media. You pick the set under **Driver set**.                                                    | The media has a default set, also on a virtual machine    |

**Model** and **Version** appear only for a manufacturer source. **Driver set** appears only for **Custom drivers**, which is listed only when driver sets are available: on the media, or on the share of the device when the [network cache](/foundry-osd/network-cache.md) is on. Without the network cache, Foundry Deploy started over PXE does not list it.

{% hint style="warning" %}
When Foundry pre-selects a manufacturer, the model matches the device. When you switch to a manufacturer source yourself and the device is not in its catalog, **Model** shows the first entry of the list, which is another machine. Select the right model, or go back to **Microsoft Update Catalog**.
{% endhint %}

## What the deployment does with your choice

| Driver source                                                      | During deployment                                                                                                                                                                                                                                      |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **None**                                                           | No driver step runs.                                                                                                                                                                                                                                   |
| **Microsoft Update Catalog**                                       | **Download driver pack**, then **Extract driver pack**, **Install Windows drivers** and **Install recovery drivers**. The drivers are in Windows before the restart.                                                                                   |
| A pack Foundry can unpack: Dell, HP, and any `.cab` or `.zip` pack | The same four steps. The drivers are in Windows before the restart.                                                                                                                                                                                    |
| A pack that is an installer: Lenovo `.exe`, Surface `.msi`         | **Download driver pack**, then **Stage driver installer**. The installer runs in Windows after the restart, before your organization's post-installation actions.                                                                                      |
| **Custom drivers**                                                 | **Stage custom drivers**, which copies the set to the target device and verifies every file, then **Install Windows drivers** and **Install recovery drivers**. The drivers are in Windows and in the Windows recovery environment before the restart. |

The search and the download need the network. Manufacturer packs are large, so allow time for the download. Foundry Deploy looks for the pack first in the [cache of the USB drive](/foundry-osd/media.md#what-each-media-type-carries), where Foundry keeps downloaded images and packs between deployments, then on the [network cache](/foundry-osd/network-cache.md#how-a-device-uses-the-cache) share when the media uses one, and downloads it from the Internet only when neither has it. A pack found in a cache is verified and reused.

If Microsoft Update Catalog cannot be reached, or returns no driver for the device, **Download driver pack** is skipped and the deployment continues without those drivers. The step shows the reason, for example "Microsoft Update Catalog is not reachable; skipping driver lookup." Check the step before you hand over the device: without a storage or network driver, Windows may not start or may have no network.

For a custom image, Foundry matches packs to the Windows release of the image build, as it does for a catalog image.

## Custom drivers

Foundry Deploy does not match a driver set to the device: you choose it, and it injects the INF files of the set. INF files that do not apply to the device or to the media architecture are skipped. Use the set your administrator prepared for this model. How sets are made is in [Custom drivers](/foundry-osd/customization/custom-drivers.md).

<figure><img src="https://64695594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdn0pr5zia6oG2DU1R1Pn%2Fuploads%2Fgit-blob-24812ac5246b6b9607161f4bb419103021797f81%2Ffoundry-deploy-driver-pack-02-custom-drivers.png?alt=media" alt="Drivers step with Custom drivers selected as the driver source and a driver set chosen in the Driver set box"><figcaption><p>With <strong>Custom drivers</strong>, choose the set in <strong>Driver set</strong>; no model or version is needed.</p></figcaption></figure>

When the media carries no driver sets, the step behaves as without this feature. When the driver sets of the media fail the integrity check, a warning reads "The custom drivers on this media failed the integrity check and are not offered. Choose another driver source or rebuild the boot media." and the usual pre-selection applies. If **Stage custom drivers** cannot verify a file, the deployment stops: "The selected custom drivers are unavailable or failed verification. Reconnect the deployment media, or restart deployment and choose another driver source."

## If something stops you

* The summary shows "\<manufacturer>: no matching model or version" and **Deploy** stays unavailable.
* **Download driver pack**, **Extract driver pack** or **Stage driver installer** fails.

The first is covered in [Before the deployment starts](/troubleshooting/deployment/before-deployment-starts.md), the second in [After the disk is erased](/troubleshooting/deployment/after-disk-erase.md). The catalogs themselves are described in [Catalogs](/reference/catalog.md).

Next: the [Windows Autopilot step](/foundry-deploy/autopilot.md) or the [Domain Join step](/foundry-deploy/domain-join.md) when the wizard shows one, otherwise [Review and deploy](/foundry-deploy/review-and-deploy.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.foundryosd.com/foundry-deploy/driver-pack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.