Win Image Driver Integrator — Free, DISM-Based Driver Injection for Windows Images (Public Beta v0.24)
Download here: Win Image Driver Integrator (Public Beta v0.24)

If you build Windows deployment images, you already know the dance: download the OEM driver pack, wrestle DISM, mount the WIM, inject, rebuild a bootable ISO, test, repeat. I do this constantly across lab boxes and demo units, so I wrapped the whole workflow into one small Windows app — and I’m releasing it as a free public beta.
Win Image Driver Integrator (WinIDI) takes driver packs and injects them — using DISM — into either an offline Windows image (WIM/ESD) or a Windows installation ISO, extracting the ISO, injecting the drivers, and rebuilding a fresh bootable ISO in a single pass. It can also provision the image for demo and lab use in the same build.
It’s free to download and evaluate, and I’m genuinely open to feedback. This is a beta — real-world reports from other practitioners are exactly what it needs to mature.
What it does
WinIDI builds deployment-ready Windows images with the right drivers baked in. It takes driver packs — Dell Family Driver Packs automatically, or extracted HP / Lenovo / Surface packs — and injects them via DISM into an offline Windows image (WIM/ESD) or a Windows installation ISO, then rebuilds a fresh bootable ISO.
Beyond drivers, it can prep the image for demo and lab scenarios: create a local administrator account, bypass OOBE, set a default wallpaper, deploy BGInfo, and apply regional settings — all in the same build.
Key features
- Driver sources: the online Dell catalog (KB000180534) with feature-update labels (24H2 / 25H2) and a search filter, or a local
.zip/.cab/ folder for any vendor. - Detect (optional): the online list loads with nothing pre-ticked — click the Detect button whenever you want to auto-tick the pack matching the machine you’re on.
- Targets: offline image (WIM/ESD) or ISO (extract → inject → rebuild bootable ISO).
- Edition picker: reads the editions straight from the image; inject one or more.
- Provisioning: local admin account, OOBE bypass, auto sign-in, regional/keyboard, default wallpaper, and BGInfo.
- Resumable downloads that survive Wi-Fi drops, with a cached
.zipso rebuilds skip the download. - Automatic cleanup of temporary folders after each build (the
.zipcache is kept). - Auto-named output ISO —
Windows_<version>-Build-<timestamp>.iso— or pick your own with Output…
New: a built-in driver-pack downloader (Lenovo now; HP & Surface coming soon)
Fresh in this beta is a standalone Download drivers utility, deliberately kept separate from image creation. Pick a vendor, load its catalog, tick the packs you want, choose a save folder, and it pulls them down with the same resumable downloader that survives Wi-Fi drops. You then extract the pack yourself and point WinIDI’s Local source at the extracted folder to build — clean separation, no surprises.
Lenovo is live now. It reads Lenovo’s SCCM/MDT catalog and lists every machine-type pack, each row tagged [full SCCM] or [NVIDIA only] so you don’t accidentally grab the incomplete GPU-only pack (a classic Lenovo trap, since those are often dated newer).
HP and Surface are coming soon — they’re stubbed in the vendor list and on the roadmap. Until then, those vendors work through the manual route below, same as always.
Driver pack sources
The DISM core is vendor-blind — it injects any folder of .INF drivers. Dell packs download (and extract) automatically; for other vendors, grab the pack, extract it yourself, then point the app at the extracted folder.
| Vendor | Driver pack | Get it & extract |
|---|---|---|
| Dell | Family Driver Packs (.cab/.zip) | Auto-downloaded & extracted by the app — just pick your model. No manual step. |
| HP | SoftPaq .exe (INF-based) | HP Driver Pack matrix → double-click the SoftPaq to extract → point the app at the folder. |
| Lenovo | SCCM/MDT pack .exe (by machine type) | Use the new built-in downloader (or the Lenovo SCCM/MDT index) → run the .exe to extract → point to the folder. Choose the full pack, not the NVIDIA-only one. |
| Microsoft Surface | Per-model .msi (drivers + firmware) | Surface driver/firmware page → extract with msiexec /a file.msi /qn TARGETDIR=C:\extracted → point to the folder. |
| Acer / Asus | Individual per-model drivers (no consolidated pack) | Download from the vendor support site, gather the extracted .INF drivers into one folder, then point the app at it. |
Tip: keep only the OS-matching subfolder (e.g. the Windows 11 / x64 set) to keep the image lean and the build fast.
How to use it — build a driver-injected bootable ISO
- Driver packs: choose Online or Local. The online list starts empty — tick the pack(s) you need, optionally click Detect to auto-tick this machine’s model, or type in the search box (e.g.
25H2) to filter. - Inject into: choose ISO file, then SELECT your base Windows ISO. Tick the edition(s) to inject (e.g. Windows 11 Pro). Match the ISO’s feature update to the pack.
- Optional — Provisioning…: enable and configure DemoAdmin, OOBE bypass, wallpaper, and BGInfo.
- Optional — Output…: name or relocate the ISO; otherwise it’s auto-named.
- Click START and confirm. The tool mounts the ISO, exports the selected edition(s), injects the drivers, applies provisioning, rebuilds the ISO, and cleans up.
- Write the finished ISO to USB with Rufus (NTFS, GPT, UEFI non-CSM).
Prefer to service an offline image instead? Choose Offline image, SELECT the install.wim / install.esd, tick the edition(s), and START — provisioning is written straight into the image, no ISO produced.
Provisioning for demo / lab
Open it from the Provisioning… menu; a check mark shows it’s enabled. Settings apply to both ISO and offline-image builds.
- Local admin account: creates the account (default
DemoAdmin) in the Administrators group, optionally passwordless with auto sign-in. - Bypass OOBE: skips the out-of-box screens straight to the desktop.
- Regional / keyboard: sets locale and keyboard (UI language stays
en-USunless you add a language pack). - Default wallpaper: a JPG, minimum 1920×1080 (3840×2160 recommended). It becomes the system default theme wallpaper and turns off Windows Spotlight desktop rotation, so it shows even before activation — yet stays fully changeable, with no “managed by your organization” banner.
- BGInfo: copies your BGInfo folder to
C:\BGInfoand adds an all-users Startup launcher so it paints the desktop at every logon.
A passwordless administrator account is for demo / lab use only — it is not a production posture.
Requirements
Run WinIDI on a 64-bit Windows 10/11 machine with local administrator rights (it self-elevates via UAC on launch).
| Component | Needed for | Notes |
|---|---|---|
| .NET Framework 4.8+ | Running the app | Built into Windows 10 (1903+) and Windows 11. |
| DISM | All injection | Built into Windows — no install required. |
| Windows ADK — Deployment Tools | Building bootable ISOs | Provides oscdimg.exe. Install separately. Offline-WIM injection works without it. |
| Rufus | Writing the ISO to USB | Use NTFS + GPT + UEFI (non-CSM). |
Match the servicing host to the image. WinIDI uses the host’s built-in DISM, which can only service a Windows image that is the same version as, or older than, the host. Build on a machine whose Windows is at least as new as the image you’re injecting (e.g. service 24H2 from a 24H2+ host). Servicing a newer image from an older host fails with “requires the latest version of the DISM” — the fix is a newer host, or install the matching Windows ADK and run from its Deployment Tools. Keeping the ADK current is good hygiene regardless.
Download & run it
Download: Windows-Images-Public-Beta-v0.24.zip — free to download and evaluate.
There’s no installer. Just extract the zip and run the executable. A couple of things to expect, because the app is not code-signed:
- SmartScreen may show “Windows protected your PC.” Click More info → Run anyway.
- It needs administrator rights and self-elevates, so you’ll get a UAC prompt on launch. If it doesn’t elevate on its own, right-click the exe and choose Run as administrator.
That’s expected for an unsigned community tool — but as always, only run software you’re comfortable with, and ideally test it on a throwaway lab VM first.
Feedback welcome
This is a beta and a one-person, best-effort project, so I’d love to hear how it behaves on your hardware and image workflows — what worked, what broke, what’s missing. Drop a comment. The Lenovo downloader in particular is brand new, so reports there are gold.
Disclaimer
This application is developed by an individual and is not an official tool of, nor affiliated with or endorsed by, any hardware vendor (Dell, HP, Lenovo, Microsoft, etc.). Its purpose is to assist with integrating driver packs into Windows 10 and Windows 11 builds for demonstration and lab use. It may be applied to production images provided they go through your organisation’s proper testing and certification process. The software is provided “as is”, without warranty of any kind, express or implied; use it at your own risk. It is free to use and best suited to lab environments and demo machines. It is maintained by the developer, Jay-R Barrios (www.jayrbarrios.com), on a best-effort basis, with no guarantee of updates, fixes, or support.




Leave a Reply