# How to Add a NIC Driver to boot.wim for PXE Boot Failures

> Inject a missing NIC driver into the WinPE boot image when PXE boot fails on a particular hardware model.

Source: https://docs.capaone.com/capainstaller/knowledge-base/how-to-add-a-nic-driver-to-boot-wim-for-pxe-boot-failures/  
Product: CapaInstaller — a separate CapaSystems product; do not apply this page to any other.

## Overview

When PXE booting a device into CapaInstaller, the process may fail because the WinPE boot image (`boot.wim`) does not include the NIC driver for that hardware model. This article explains how to inject the correct NIC driver into the boot image and redistribute it to all OSD servers.

For the standard console procedure without troubleshooting context, see [How to add NIC to boot.wim](/capainstaller/the-capainstaller-console/os-deployment/how-to-use-osd/how-to-add-nic-to-boot-wim/).

## Prerequisites

- Access to CapaInstaller Console with OS Deployment permissions.
- The correct NIC driver package extracted on the CapaInstaller server. The extracted folder must contain an `.inf` file — do **not** use a `.exe` installer directly.
- Windows Assessment and Deployment Kit (Windows ADK) and the Windows PE add-on installed on the CapaInstaller server. Both components must be the **same version**.

## Step-by-Step Instructions

### 1. Download and extract the NIC driver

Obtain the NIC driver for your hardware model from the manufacturer's support site. Extract the package to a local folder on the CapaInstaller server. Confirm the extracted folder contains an `.inf` file — this is what WinPE requires. Do not point to the `.exe` directly.

The following vendor WinPE driver pack pages are a good starting point:

- **Dell**: [Dell Command Deploy WinPE Driver Packs](https://www.dell.com/support/kbdoc/en-us/000107478/dell-command-deploy-winpe-driver-packs)
- **HP**: [HP WinPE Driver Pack](https://ftp.ext.hp.com/pub/caps-softpaq/cmit/HP_WinPE_DriverPack.html)
- **Lenovo**: [SCCM Package for Windows PE 11/10 64-bit (ThinkPad)](https://support.lenovo.com/us/en/downloads/ds561550-sccm-package-for-windows-pe-11-10-64-bit-thinkpad)

**Alternative — pre-placing drivers on the server**: If you have a large number of drivers to inject, you can place them directly into the following folder on the CapaInstaller server before running the Create Boot File wizard:

```
<OSD POINT>\MediaMaster\Kit\uefi\amd64\driver
```

Any drivers placed in this folder will be picked up automatically during the boot image build, without needing to add them individually through the **Additional Drivers** step in the wizard.

### 2. Open the Create Boot File wizard

In CapaInstaller Console, navigate to **OS Deployment** in the left panel.

![OS Deployment panel in CapaInstaller Console](/attachments/capainstaller/fd3e2a17-8c4b-4e9f-a12d-5b7c891d0e3f.png)

Right-click your OSD point (e.g., `OSDDev` or `OSDProd`) and select **Boot Image → Create boot file…**

![Right-click context menu showing Boot Image submenu](/attachments/capainstaller/a8c5f290-3d71-4b6e-9f84-2e1a7c3d5f6b.png)

### 3. Configure the WinPE settings

On the **WinPE Configuration** screen, set the following:

- **Target Point**: Select your deployment point (e.g., `OSDDev`).
- **Keyboard Layout**: Select the layout used in your environment (e.g., `en-US`).
- **Scratch Space**: `256` MB is a safe default.
- **Wallpaper**: Optional — leave blank or select an image.

Click **Next** to continue.

![WinPE Configuration dialog](/attachments/capainstaller/b7d4e391-5c82-4a7f-8e95-1f2b3c4d5e6f.png)

When prompted for architecture, select **Create Boot Image for 64-bit UEFI systems** unless your environment requires 32-bit.

### 4. Inject the NIC driver

On the **Additional Drivers** step, click **Add…** and browse to the folder containing the extracted `.inf` driver file. Confirm the driver appears in the driver list before proceeding.

![Additional Drivers step showing the driver list](/attachments/capainstaller/c6e3f482-4b91-4b8e-7d84-0e1f2a3b4c5d.png)

Click **Next** to begin the build.

### 5. Build the boot image and update all OSD servers

Wait for the build to complete. When the wizard reports that the boot image build is complete, click **Update servers** to push the new `boot.wim` to all configured OSD/PXE servers immediately.

![Build completed dialog with Update servers option](/attachments/capainstaller/d5f2e573-3a80-4c7d-6c93-9d0e1f2a3b4c.png)

Alternatively, you can trigger this later by right-clicking the OSD point → **Boot Image → Update OSDClient Bootfiles on all Servers…** → **Yes**.

### 6. Test PXE boot

Attempt a PXE boot on the affected device. It should now acquire a network connection in WinPE and proceed with the CapaInstaller OSD workflow.

## Troubleshooting

- **PXE boot still fails after injecting the driver**: The most likely cause is that the wrong driver version was used, or the driver was not correctly added during the wizard (e.g., the `.exe` was selected instead of the extracted folder containing `.inf`). Re-run the wizard, verify the driver appears in the **Additional Drivers** list, and rebuild. It may be necessary to rebuild and redeploy more than once.

- **ADK version mismatch**: Verify that both the **Windows ADK** and the **Windows PE add-on** installed on the CapaInstaller server are the same version. A mismatch can prevent drivers from loading correctly in WinPE. Uninstall both, restart the server, then reinstall matching versions before rebuilding the boot image.