Windows driver client

DriversCamp

Download the client for the Windows environment where it will run.

How to use DriversCamp ↓

Choose the client for the Windows or recovery environment running it. In WinPE/WinRE, match the architecture of WinPE/WinRE — not the offline Windows image.

A humorous Windows Drivers Camp scene with technicians, animals, and driver-themed cabins around a campfire.

Client guide

How to use DriversCamp

Use the graphical client for a normal run, or the command line for unattended deployment. The default service is already configured; no adjacent JSON file, client certificate, SignTool, SDK, or 7-Zip installation is required.

Default service: driverscamp.inpadi.dk

Choose a workflow

Installed Windows

Online sharing & repair

Uploads exportable OEM driver packages that the server does not already have, then finds and installs signed matches for devices missing a driver (Device Manager problem code 28).

This is not a general driver updater and does not automatically replace working drivers.

Windows / WinPE / WinRE

Offline injection

Reads the destination Windows version, architecture, and build; matches current or captured hardware; then downloads, verifies, and stages compatible drivers through DISM.

It does not export or install drivers in the running recovery environment.

Any supported environment

Hardware capture

Saves the current computer's device IDs to a JSON file. Use that file when servicing an image from another computer.

Capture needs no administrator token and no connection to the DriversCamp server.

Quick start

Repair missing drivers on installed Windows

  1. Download the client matching the computer: x64 for most PCs, ARM64 for Windows on ARM, or x86 for 32-bit Windows.
  2. Run DriversCamp.exe and approve the Windows UAC prompt.
  3. Leave Online sharing and repair selected, then click Start.
  4. Review the final summary and log. DriversCamp never restarts the computer automatically.

Inject drivers into offline Windows

  1. Apply or mount the Windows image and locate the root containing the Windows directory.
  2. Run DriversCamp as administrator and choose Inject into an offline Windows image. WinPE/WinRE selects and locks this mode automatically.
  3. Enter the destination root, for example W:\ or C:\Mount\OS. Leave the hardware file empty to scan this computer, or select a captured JSON file.
  4. Click Start, review the result, then commit/unmount a mounted WIM using your deployment tool.

Offline does not mean disconnected. The destination Windows installation is offline, but the client still needs network access plus working Windows TLS and driver-signature trust. The running Windows installation cannot be selected as its own offline target.

Unattended commands

/silent never opens a UAC prompt. Run online repair and offline injection from an elevated terminal or deployment process.

Online sharing and repair

Elevated PowerShell 
$run = Start-Process -FilePath .\DriversCamp.exe `
    -ArgumentList '/silent' `
    -WindowStyle Hidden -Wait -PassThru
$run.ExitCode

Offline injection from WinPE or WinRE

Command Prompt 
dir W:\Windows
start "" /b /wait DriversCamp.exe /silent /offline W:\
echo Exit code: %errorlevel%

Service a mounted image from a technician PC

Elevated PowerShell 
$run = Start-Process -FilePath .\DriversCamp.exe `
    -ArgumentList '/silent /offline C:\Mount\OS' `
    -WindowStyle Hidden -Wait -PassThru
$run.ExitCode

Capture target hardware

Command Prompt 
start "" /b /wait DriversCamp.exe /capture-hardware D:\Deploy\target-hardware.json
echo Exit code: %errorlevel%

Inject using captured hardware

Elevated PowerShell 
$run = Start-Process -FilePath .\DriversCamp.exe `
    -ArgumentList '/silent /offline C:\Mount\OS /hardware D:\Deploy\target-hardware.json' `
    -WindowStyle Hidden -Wait -PassThru
$run.ExitCode

Before hardware capture: create the output directory first. DriversCamp deliberately refuses to overwrite an existing hardware JSON file.

/silent
Run without the graphical interface or prompts.
/offline <root>
Inject drivers into the offline Windows installation at the specified root.
/capture-hardware <file>
Save the current computer's hardware IDs to a new JSON file and exit.
/hardware <file>
Use captured hardware IDs instead of scanning the current computer.
/config <file>
Load an optional client configuration file.
/dism <path>
Use a specific host-side DISM executable, such as a compatible ADK version.

Results and logs

Exit codes

Code Meaning
0 Completed successfully. Online mode has no errors or unresolved missing-driver devices. Offline mode may still report hardware for which no server match exists.
1 Error. Online mode also returns 1 for unresolved missing-driver devices. In offline mode, successful injections made before a later error remain applied.
3010 Successful; restart required. DriversCamp reports the requirement but never restarts Windows automatically.

Default log locations

  • Online: %LOCALAPPDATA%\DriversCamp\logs
  • Offline for W:\: W:\DriversCamp\logs
  • Offline working files: W:\DriversCamp\client-work

Offline runs create the main run log and, once servicing starts, separate DISM and DISM-output logs with the exact command and output.

Requirements and important notes

  • Supported installed systems are Windows 10 version 1607 or later, Windows 11, and Windows Server 2016, 2019, 2022, or 2025.
  • Online repair and offline injection require administrator access, network connectivity, a working Windows trust store, and enough temporary disk space.
  • Online sharing and repair is disabled in WinPE/WinRE. Use offline injection or hardware capture there.
  • DriversCamp verifies downloaded packages and checks destination compatibility before injection, but a match cannot guarantee that DISM accepts the driver or that the device works after first boot.
  • Only signed, exportable third-party/OEM packages are collected. Inbox Windows drivers are not copied from the running system.

Troubleshooting

Online operation is disabled in WinPE/WinRE

This is intentional. Locate the destination Windows installation and use offline injection, or run /capture-hardware.

No server package was found

Check the destination Windows version, architecture, build, and selected hardware source. Drivers that require a newer Windows build are excluded. An inbox Windows driver may already cover the device.

DISM injection failed

Read the run's DISM log and DISM-output log, then confirm that the host or ADK DISM version supports the target image. Passing DriversCamp's compatibility checks does not bypass Windows servicing requirements.

Offline storage could not be prepared

Make sure the destination drive is writable, supports Windows ACLs, and has sufficient free space. Use an explicit configuration if work and log files must be placed on another persistent disk.

401 Unauthorized

The client and server were built with different deployment identities. Use a client that belongs to the deployed DriversCamp server.