The PC blue-screens before it reaches the login screen, but you still want its exact drivers before wiping it. Boot a WinPE USB, point DISM at the sleeping Windows with /image:, and the drivers export offline — no working Windows required.
The familiar command uses /online, which means 'the Windows I am currently running in'. When the running system is WinPE, that is the wrong Windows entirely. The offline form of the same command reads the driver store of the Windows lying on the disk — which works even when that Windows cannot start, because reading files never required it to boot.
Example command. D: and E: are the letters in this WinPE session; verify yours before running anything.
Boot your WinPE USB — Strelec, NHV Boot, or the Windows installer's own recovery command prompt via Repair your computer → Troubleshoot → Command Prompt. Then find where Windows actually lives in this session:
diskpart, then list volume, and note the letters and sizesdir D:\Windows — the letter that lists the Windows folder contents is your targetDo not trust habit here. WinPE assigns letters fresh, the recovery partition often takes C:, and exporting from the wrong target produces a tiny, useless folder that looks like a driver problem but is really a letter problem.
dism /image:D:\ /export-driver /destination:E:\DriversBackup — substituting your verified lettersA suspiciously short list — three drivers from a full Windows — almost always means the /image: path points at a recovery partition or the wrong disk. Re-check the letter with dir and run it again. The export produced this way has the identical structure to an online one and restores exactly the same way.
The DISM doing the reading should be the same Windows generation or newer than the offline image it reads. A Windows 11-based WinPE reading a Windows 10 image is comfortable. A very old WinPE build reading a much newer Windows can refuse, misread, or quietly export less than the store holds.
Practical version of the rule: keep your WinPE boot USB reasonably current. If the offline export errors in ways that make no sense, rebuilding the boot USB with a current WinPE is the fix more often than any command variation.
Two honest dead ends. First, a physically failing drive — clicking, beeping, vanishing from the BIOS, or freezing the WinPE session itself. Stop: data recovery comes first, because drivers are replaceable and the user's files are not, and heavy reading of a dying drive can finish it.
Second, a BitLocker-locked volume. DISM cannot read an encrypted Windows until it is unlocked. From the WinPE prompt, unlock it with the recovery key — manage-bde -unlock D: -RecoveryPassword followed by the 48-digit key — confirm you can browse the volume with dir, and only then run the export. No key means no export; that is BitLocker working as designed, not a fault to route around.
Nothing about the restore changes because the export was offline. Install Windows, then restore from the folder with the bulk command — pnputil /add-driver E:\DriversBackup\*.inf /subdirs /install — or device by device in Device Manager, chipset first on stubborn machines, and finish with the top-to-bottom Device Manager check.
Keep the salvage in proportion, though: offline export is the tool for a Windows that cannot boot. If the machine still starts, the ordinary online export from inside Windows is simpler, and its result is easier to verify against the living system.
The online version of this export is the video's one command — watch it to see the healthy run this salvage method mirrors.
▶️ Watch Full VideoYes. Boot the installer, press Shift+F10 for a prompt at setup — or go through Repair your computer to the Command Prompt — and the DISM there runs the same /image: export. A full WinPE USB is more comfortable, not more capable, for this job.
Take what exports cleanly, write down which drivers are missing, and plan to fetch those few from the maker's site for that exact model after the install. A corrupt store usually means a partial salvage — still far better than none.
Yes — it reads the same driver store from the same Windows, just without that Windows running. Third-party packages export identically; Windows in-box drivers are skipped the same way, because they return with the fresh install.