DISM, a beginner's question

gpriatko

Ars Tribunus Militum
1,562
I haven't used DISM before (been out of the game a very long time).

My goal is to extract the drivers from a recovery partition (Dell Inspiron 13 7378). The problem that I'm trying to resolve is that that laptop either crashes or hangs after it blanks it screen(s). Blank time when testing was set to one minute. It recovers properly if you bump the mouse (or keyboard) in less than 40 seconds. Debug just tells me that the kernel is unhappy because of some timers.

Anyway, I wanted to know what video driver Dell put on the recovery partition. I've got a full disk image on a portable USB drive.

1. Attach the USB drive to my laptop (not the one having the problem)
2. Assign a drive letter to the remote recovery partition
3. Use file mangler to give my account access to that drive letter (it's owned by SYSTEM when it gets built)
4. Create a folder on my laptop to receive the extracted drivers.
5. Mount the .wim file on the remote recovery partition
6. Extract the drivers
7. Dismount the remote recovery .wim file

Seems easy. I'm suspicious that I'm not using the correct dism commands. Reason being that what gets extracted includes more than drivers and the drivers look like they came from my laptop and not the remote .wim file. I say that because some drivers include 'TigerLake' in their title. The machine that I'm trying to repair is Kaby Lake. I would have thought that it's restore partition shouldn't know anything about Tiger Lake.

The dism commands that I use are:
Code:
dism /Mount-Image /ImageFile:z:\Recovery\WindowsRE\Winre.wim /Index:1 /MountDir:c:\dell\driver-export
dism /online /export-driver /destination:C:\dell\driver-export
dism /Unmount-Wim /Mountdir:c:\dell\driver-export /discard
Admittedly I know essentially zero about dism, but this seems like Babies First DISM exercise.

I tried /commit rather than /discard and got the error that there's not enough room on the drive. That suggests to me that I'm really using the .wim on the remote recovery partition.

EDIT: OK, maybe this is a silly work-around but here's what I just did to get a copy of the drivers off of the Dell Factory Restore flash drive,

1. Create yet another folder in the Dell directory to act as the mount folder for DSIM
2. Mount the .wim file on the flash drive using DISM
3. Use File Explorer to navigate over to the mount folder
4. Copy all of the drivers in the MountDir (Windows> System32 > drivers > DriverStore) to some other folder on the C drive
5. Unmount MountDir without saving

Code:
makedir c:\dell\Windows10MountDir
DISM /Mount-image /imagefile:e:\sources\sos.wim /Index:1 /MountDir:c:\dell\Windows10MountDir

{ Use File Manager to copy files }

DISM /Unmount-image /MountDir:C:\dell\Windows10MountDir /discard


Someday I'll figure out how to make this work from the command line using only DSIM but for now, this is good enough.

Advice gladly accepted.
 
Last edited:

dbwillis

Ars Tribunus Militum
2,643
All your drivers should be in C:\Windows\System32\DriverStore\FileRepository
I believe that's how we make model specific driver packages.
Install Windows, mostly everything in f repository has the same date.
Install needed driver's to clean up device Manager.
Sort the f repository by date and the driver files with today's date are whats needed in addition to in build driver's.
 
Last edited:
  • Like
Reactions: continuum

Entegy

Ars Legatus Legionis
17,702
Seems easy. I'm suspicious that I'm not using the correct dism commands. Reason being that what gets extracted includes more than drivers and the drivers look like they came from my laptop and not the remote .wim file. I say that because some drivers include 'TigerLake' in their title. The machine that I'm trying to repair is Kaby Lake. I would have thought that it's restore partition shouldn't know anything about Tiger Lake.
It is a mix of Windows and Dell drivers, not everything in the recovery partition will be relevant to that exact machine. It is a bit more generalized than that.
 

gpriatko

Ars Tribunus Militum
1,562
Right, I expect that their ISO has the Windows Basic Video Adapter plus a newer Intel driver. The more that I dig in to this, the more it becomes clear how unclear the configuration process is. I can build a bootable flash drive with Microsoft's latest ISO and another flash drive with Dell's (recovery tool) ISO and get rather different looking combinations of services and drivers.