Update your Win 7 installation media

Page 12 of 144 FirstFirst ... 2101112131422112 ... LastLast

  1. Posts : 16,119
    7 X64
    Thread Starter
       #111

    DriverBackup! probably works ok, but dism++ is kept up to date and is more descriptive.
      My Computers


  2. Posts : 16,119
    7 X64
    Thread Starter
       #112

    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.


    Paul Black said:
    Hi SIW2,

    I see you have added bootwimupdates and installwimupdates, along with adjusting the registry hives and creating a WinRE.WIM [then optimised it and compressed it]. I noticed that you also added these two lines:

    IF EXIST "Import\Windows" XCOPY.exe "Import" "%TP%\MOUNT" /cheriky
    IF EXIST "%TP%\winre.wim" COPY /Y "%TP%\winre.wim" "%TP%\MOUNT\Windows\System32\Recovery"

    Does that setup the recovery options. I am just interested!

    Thanks in advance.

    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.
      My Computers


  3. Posts : 6,021
    Win 7 HP SP1 64-bit Vista HB SP2 32-bit Linux Mint 18.3
       #113

    Thanks for the explanations and detailed reply @SIW2, it is appreciated .
      My Computer


  4. Posts : 6
    Win 7 64bit Pro
       #114

    When all's said and done


    So the update [once it's done] is 700MB or at least 4GB?
      My Computer


  5. Posts : 54
    Win7 Pro x64 SP1
       #115

    Thank you for the informative response ...



    SIW2 said:
    1. You will only need to add 3rd party drivers. Place them in the folder 7UPDATER\Drivers\Bootx64 and 7UPDATER\Drivers\Installx64
    Left "in the box" unchecked in dism++ per your instructions.


    SIW2 said:
    2. Any drivers in the Drivers\Bootx64 folder will also be included in boot.wim and winre.wim
    So you probably don't want to put your printer drivers in there, for example.
    Not sure how to differentiate between drivers needed during install and drivers needed to boot ...


    SIW2 said:
    3. Any updates in the Updates\Bootx64 folder will also be included in boot.wim and winre.wim
    Don't believe I have any of these.



    SIW2 said:
    4. You can copy the folders in. It searches recursively.
    Thanx, that makes it easy.


    SIW2 said:
    5. The easiest way to export 3rd party drivers from a running OS is to use dism++. It tells you what they all are. (Don't tick Display Inbox Drivers so it only shows you 3rd party drivers)
    Yep this is far superior to DriverBackup. Thx for the tip.



    SIW2 said:
    If you want nvme support, you need to put the two MS nvme updates in the 7UPDATER\Updates\Bootx64 and 7UPDATER\Updates\Installx64 folders.

    Apparently those two MS updates are required to support any 3rd party nvme drivers.
    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 ...
      My Computer


  6. Posts : 16,119
    7 X64
    Thread Starter
       #116

    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... ]
    Yes, you shouldn't need to add the nvme updates again if you have already integrated them using the MSI tool.

    So the only open question I have is determining which drivers are considered "boot" and which "install"
    Yep.
      My Computers


  7. Posts : 54
    Win7 Pro x64 SP1
       #117

    Hello SIW2

    So the only open question I have is determining which drivers are considered "boot" and which "install"
    Yep.
    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 folder

    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:
    Update your Win 7 installation media-boot-install-folders-proces.jpg


    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:
    Update your Win 7 installation media-boot-install-folders.jpg


    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:
    Update your Win 7 installation media-boot-install-folders-files.jpg


    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
      My Computer


  8. Posts : 16,119
    7 X64
    Thread Starter
       #118

    "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.
      My Computers


  9. Posts : 54
    Win7 Pro x64 SP1
       #119

    Thank-you. It's what I hoped. Assistance much appreciated.
      My Computer


  10. Posts : 54
    Win7 Pro x64 SP1
       #120

    Worked great twice; now it doesn't


    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.
    Update your Win 7 installation media-7updater-problem.jpg
    Thanx in advance for your time and expertise ...
      My Computer


 
Page 12 of 144 FirstFirst ... 2101112131422112 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:03.
Find Us