New
#111
DriverBackup! probably works ok, but dism++ is kept up to date and is more descriptive.
Hi paul,
The bootwimupdates is mainly for the MS nvme updates ( it is complicated integrating those, so the .cmd file does it all for you).
The registry adjustments show hidden files and extensions. That allows you to see what you are doing if you need to browse from booted boot.wim or winre.wim. It also increases the scratch space to a usable size.
Instead of updating boot.wim and winre.wim separately, boot.wim is updated, then boot.wim image 2 is exported and used as winre.wim. Saves a lot of time and extra commands.
The Import folder is there so that you can add anything to be imported into the wim.
E.G. you can copy the contents of Atak's Import folder into it.
IF EXIST "Import\Windows" XCOPY.exe "Import" "%TP%\MOUNT" /cheriky
If you have put anything in the Import folder, it is copied to the mounted install.wim image
IF EXIST "%TP%\winre.wim" COPY /Y "%TP%\winre.wim" "%TP%\MOUNT\Windows\System32\Recovery"
That copies the newly created winre.wim ( which contains any updates\drivers) into the mounted Install.wim image. It replaces the bog standard winre.wim that is in MOUNT\Windows\System32\Recovery folder.
So the update [once it's done] is 700MB or at least 4GB?
Thank you for the informative response ...
Left "in the box" unchecked in dism++ per your instructions.
Not sure how to differentiate between drivers needed during install and drivers needed to boot ...
Don't believe I have any of these.
Thanx, that makes it easy.
Yep this is far superior to DriverBackup. Thx for the tip.
My "starting iso" for your process had USB3 and NVMe drivers/support inserted using the Gigabyte Windows USB Installation Tool; does that accomplish the same objective? [Not that I have NVMe yet... ]
So the only open question I have is determining which drivers are considered "boot" and which "install" (I googled "drivers to boot win7" but the results we're particularly informative) and then I can give this another whirl ...
Cheers for now ...
Yes, you shouldn't need to add the nvme updates again if you have already integrated them using the MSI tool.My "starting iso" for your process had USB3 and NVMe drivers/support inserted using the Gigabyte Windows USB Installation Tool; does that accomplish the same objective? [Not that I have NVMe yet... ]
Yep.So the only open question I have is determining which drivers are considered "boot" and which "install"
Hello SIW2
My apologies for being unclear; that was actually a solicitation for assistance in determining which of the drivers exported using dism++ should go in the boot folder & which should go into the install folderYep.So the only open question I have is determining which drivers are considered "boot" and which "install"
However, given your response I thought maybe doing that isn't a big deal. So I went googling for "win7 boot drivers". Finding scanty results I've taken a stab at it, which is sort of a "brute force/manual" process. I'd appreciate a "sanity check" ...
I have a test W7 install with all up-to-date drivers installed from mfg’s disks & downloads. I have a “virgin” install in VirtualBox for which I used the updated ISO resulting from the processes you've kindly shared. Bootlogging was activated for both installs. Below is a graphic depicting my approach:
The first compare I did in Excel, my theory being that – since the VM install has nothing added – all drivers loaded there (with the exception of VM specific drivers) are “in box” drivers. Any drivers not found in both bootlogs should be 3rd party.
The 2nd compare was done by searching the dism++ exported folders for each file deemed to be 3rd party. The original dism++ export I considered “for install”; if a file was found in the export the entire folder containing that file was moved to a new “for boot” folder:
When finished there were a large number of files loaded during boot of the test install – which are designated as being in the drivers folder – that are not found in either the dism export or in the VM bootlog:
At this point I don’t know where my logic has gone awry…
Any observations or advice will be appreciated.
Last edited by Ritjesman; 19 Sep 2018 at 10:34. Reason: added level of folders moved pic
"not in export":
Plenty of the current in box drivers that are supplied in the standard MS boot.wim will be loaded.
"in dism++ export"
If it works ok, then you have got it right.
A lot of people want to create a kind of universal install media that should work on almost any system. That obviously means integrating some things that are not needed on all systems. It doesn't matter, they won't be used if not needed.
Not sure where I've gone wrong. This worked flawlessly twice (only 8 additional updates needed post-install). Now when I select the folder containing the win 7 installation media the blue command prompt window looks like it is trying to progress to the next step and then it terminates itself.
The win 7 installation media folder contains the results from a successful run from which an ISO was created. The ISO contents were copied into the win 7 installation media folder (zw7Cont).
My intent was to add drivers to the ISO containing the updated Win7 installation media. Below is my folder structure. Any insights about what I've screwed up and how to fix it will be much appreciated.
Thanx in advance for your time and expertise ...