## TL;DR
Driver injection fails when the recovery tool cannot consume the drivers offered: wrong packaging such as installer EXEs instead of extracted INF drivers, wrong architecture, or drivers for the wrong boot controller. Extract vendor driver packs to INF form, match them to the target hardware and Windows version, load storage drivers first in the recovery environment, and retry the injection.

```text
bare metal restore driver injection failed
```

## Use this when
- The restore wizard reports driver injection failed or cannot add drivers.
- The recovery environment itself cannot see the target disks.
- Drivers supplied are vendor installer packages downloaded for normal Windows installs.

## Not for this skill when
- Injection succeeded but the restored system still blue screens. Boot configuration or mode may be the cause.
- The restore media will not boot at all. Media creation problem.

## Steps
1. Check the recovery environment device list to see which target devices lack drivers, starting with storage. Verify: missing driver devices are listed
2. Obtain the vendor driver pack for the exact target model and extract it to plain INF, SYS and CAT files. Verify: extracted driver folders exist in INF form
3. Confirm driver architecture and Windows version match the restored image. Verify: no mismatched architecture drivers are in the set
4. Load the storage driver in the recovery environment and confirm the target disks appear. Verify: disks are visible before restore proceeds
5. Run the restore with injection using the extracted drivers and confirm the injection step reports success. Verify: restore completes with drivers injected

## Variant phrasings
### driver injection failed recovery environment inf
The INF phrasing.
### bare metal restore cannot add drivers storage
The storage variant.
### recovery media missing drivers disks not visible
The visibility wording.

Compatibility: Veeam Recovery Media, Acronis bootable media and similar WinPE recovery environments for Windows 10, 11 and Server restores.

## Why it happens
Recovery environments are minimal WinPE systems with a small built-in driver set, and their injection tools consume raw driver files, not the installer bundles vendors publish for running Windows. Storage drivers gate everything else because without disks there is nowhere to restore to, so packaging and load order decide success more than driver version freshness.

## Edge cases / pitfalls
- Build recovery media on or for the target hardware class when possible. Its driver set then matches by construction.
- Keep a labelled USB of extracted storage drivers for each server model you operate.
- WinPE network drivers matter for repository access. Inject NIC drivers alongside storage when restoring over the network.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_R5PHvU8sXHEtjWe0IxW-jQ