Update your Win 7 installation media

how can we set Doupdate=NO to skip running updatepatch (if there is no UpdatePack7R2) and UpdatePack7R2 even if the user selected install simplix?

I don't understand the question.


1. If Updatepack is already present, it askes if you want install the updates from the pack.
Answer yes or no.
Therefore if you answer no - it does not run Updatepack.

2. If Updatepack is not present but Updatepatch is present, it asks if you want to run Updatepatch ( running the Updatepatch just downloads the 700mb Simplix Updatepack ).
Answer yes or no.
Therefore if you answer no - it does not run Updatepatch.

3. It checks to see if the user has put drivers into DRIVERS\Boot%wimarch% and/or updates into UPDATES\Boot%wimarch% folders.

i) If so, it asks if you want to mount boot.wim (presumably you do because that is why you put the drivers or updates in those folders)

ii) It integrates any DRIVERS\Boot%wimarch% and/or UPDATES\Boot%wimarch% into boot.wim image 2.

iii) It exports boot.wim image 2 into a new winre.wim file - which now has the user placed drivers/updates integrated.

iv) If you included the MS nvme updates, the new setup files are copied into the %wimdir%\sources folder - which is where they need to be.

4.It asks which image from Install.wim you want to process.

i) It integrates any DRIVERS\Install%wimarch% and/or UPDATES\Install%wimarch% into the selected install.wim image.

ii) It inserts the new winre.wim that has been created into the selected install.wim image.

There are 3 ways to use 7Updater.

METHOD 1.

Use it to download and Install Simplix updates.

You can optionally also add extra drivers and (recommended ) the ms nvme updates by placing them in DRIVERS\Boot%wimarch% and updates into UPDATES\Boot%wimarch% as well as DRIVERS\Install%wimarch% and UPDATES\Install%wimarch%.

It is not necessary to put any usb3 drivers into Install.wim - Simplix does that. But Simplix does not add anything to boot.wim - so you might want to put USB3 drivers into DRIVERS\Boot%wimarch%.

It is recommended to put the MS nvme Updates into UPDATES\Boot%wimarch% AND UPDATES\Install%wimarch%. That is because neither Simplix nor Dism++ install them correctly.



METHOD 2.

Just use it to install your own selected drivers and updates.

Say No when asked to d/l or install Simplix updates - just use it to integrate any of your drivers or updates - by placing them into
DRIVERS\Boot%wimarch% and UPDATES\Boot%wimarch% as well as DRIVERS\Install%wimarch% and UPDATES\Install%wimarch%


METHOD 3

Fastest method for having ALL images updated.

Integrate Updates into Image 1 of Install.wim using Dism++

Say No to downloading/installing Simplix updates ( because you already used Dism++)

Put any extra drivers or updates you want into DRIVERS\Boot%wimarch% and UPDATES\Boot%wimarch% as well as DRIVERS\Install%wimarch% and UPDATES\Install%wimarch%.

Recommend you put MS nvme updates into UPDATES\Boot%wimarch% AND UPDATES\Install%wimarch% - because Dism++ does not install them correctly.

Select to Process ALL images.

You will end up with ALL images containing the Dism++ updates you already put into Image 1 - as well as anything extra you added to the folders.

This is the quickest method for getting ALL images updated.

If I understood right, you save the UpdatePack7R2 date to install.wim

No. It uses the current date.

You can use the Updatepack date instead if you really want - you need to remove the :: from the front of

::for /f "tokens=1,2 delims=- skip=1" %%a in ('bin\ConvertDateHex.exe /d%ndat% /t22:26:11') do set "HP=%%a"& set "LP=%%b"

How can we extract this date from install.wim and compare to the UpdatePack7R2-19.4.10.exe on the 7UPDATERvXX folder and set Doupdate=No so I can jump the simplix update?

I have no idea. Never thought about it.

Can probably be done by using wimlib-imagex info to extract the date from the wim.
WIMINFO

If you run Simplix against an image that already contains pending cumulative updates, it will just tell it can't run because of that.

So it won't work if you have run Simplix or Dism++ on that image already. It used to - but Simplix has changed it.
Though it should work on an image that has been updated, applied to a partition, then sysprepped and captured.

New version 22D.
Cleaned up the cmd file. Messages are better. Prompts to download latest version dism if using win7 host.
Split-wim and Optimize-wim cmd files now use the host architecture version of wimlib ( allegedly quicker on x64 system). Bootorder.txt is adjusted for non en-US wims when using create-iso.cmd

I was wondering if using your update script would it be possible to exclude certain updates from being incorporated (e.g. meltdown or telemetry tracking)

1. If you select to download simplix there is no telemetry included.
Meltdown protection is not activated.

Also how would one add drivers for the recovery console? Would adding them to the two directories make them available in the recovery console?

2. Any drivers you put in DRIVERS\bootx64 ( or DRIVERS\bootx86 if you updating x86 image) will be integrated into both boot.wim and winre.wim ( which is where the recovery options are).

If you want the same drivers in Install.wim, place them in DRIVERS\Installx64 folder.

[Note: Simplix automatically takes care of usb3 drivers for Install.wim. So you only need to put usb3 drivers in the DRIVERS\bootx64 folder.]


3. If you have added drivers/updates (e.g. the MS nvme updates on first post) to those folders, then the script will ask if you want to mount boot.wim.

Obviously, the answer is Yes.

V22 now on first post has added messages to make it more obvious to the user.