Windows 7 Unofficial Update Rollup (WIP)

[bphlpt]

If you're trying to install Windows 7, then no.  Leave everything where it is.  If you use abbodi1406's installer script, which you can find here - http://forums.mydigitallife.info/threads/44645-WHDownloader-Support-and-chat/page259?p=1169513#post1169513 - it will get what it needs from the correct folder.

You have two methods you can choose:

A) Use the convenience update, (which I didn't think you wanted to do), in which case use "WHD-W7UI.cmd" which will ignore everything in the "Extra\WithoutKB3125574" folder.

B) Install the classic way, (which was what I thought the whole purpose of this project was), and use "WHD-W7UI_WithoutKB3125574.cmd" which will pull from "Extra\WithoutKB3125574" as it needs to.

You can read both scripts to see exactly what they do, they're just batch commands.

Basically, you are correct that without KB3125574 it will use the updates in both "Windows7-x64\Security" plus "Windows7-x64\Extra\WithoutKB3125574\#Security" etc.  Everything in "Extra\WithoutKB3125574" is what is included in KB3125574, but since you're not going to use KB3125574 then you'll have to include those updates.  Remember, there are still various telemetry updates scattered about which you might or might not want to include in your project. Whatever you don't want to include, simply move that update out of the regular location into somewhere that the install script won't pick it up.  On my last install I left everything where it was and just did not select the option to install WAT and Windows 10 related updates,  only about 7 in total if I remember right. Your project might appeal to more people and be more flexible if you also remove the telemetry updates. They can always be installed later if they are wanted/needed.

I thought your project's intention was to basically do the same thing as the installer script, but instead of installing the updates, they would be combined into a single "rollup" that could be more easily installed by the end user.  In any case, I thought the installer script would be a good staring point for you.

You will also have to discover any additional updates that WUI/MU finds after you boot your installed system.  I was surprised how many updates were found, but it was nowhere near the number that would have been found without the help of WHDownloader and the install script. Remember, using WHDownloader includes most of the "request only" hotfixes that you would have had to search for manually otherwise.

I'm glad you have had good success downloading the updates using WHDownloader.  It was quick and easy, wasn't it?

Cheers and Regards

[bphlpt]

By the way, here is a complete list of all Windows 7 updates that should be excluded that i think would satisfy even the most paranoid.

KB971033 
KB2882822
KB2902907
KB2922324
KB2952664
KB2976978
KB2977759
KB2990214
KB2999226
KB3012973
KB3014460
KB3015249
KB3021917
KB3022345
KB3035583
KB3042058
KB3044374
KB3046480
KB3050265
KB3058168
KB3064683
KB3065987
KB3065988
KB3068708
KB3072318
KB3074677
KB3075249
KB3075851
KB3075853
KB3080149
KB3081437
KB3081454
KB3081954
KB3083324
KB3083325
KB3083710
KB3083711
KB3086255
KB3088195
KB3090045
KB3093983
KB3102810
KB3102812
KB3112336
KB3112343
KB3118401
KB3123862
KB3135445
KB3135449
KB3138612
KB3138615
KB3139929
KB3146449
KB3150513
 

This includes everything in Dencorso's current list of what to exclude to prevent being updated to Windows 10 against your will, along with additional updates that Yzowl feels are important to prevent sharing anything with MS.  This list is current as of the May updates.  I don't know for sure if either of them thought that there are any updates from the June list that should also be excluded or not.  The update that fixes the MU/WU delay, KB3161608, comes to mind.  Some might not want it, I don't know.

Cheers and Regards

Edited June 29, 2016 by bphlpt

[LightAlpha263]

4 hours ago, bphlpt said:

I thought your project's intention was to basically do the same thing as the installer script, but instead of installing the updates, they would be combined into a single "rollup" that could be more easily installed by the end user.  In any case, I thought the installer script would be a good staring point for you.

More or less. I was looking into it the other way, as the installer itself being the rollup, but I have found ways to merge .msu files together. If these ways prove to work, then:
 

1. There will be a universal .msu for security with updates added to it when needed etc.

2. The installer will use wusa.exe to install each .msu.

3. The last update will be separate from the combined updates, and have a different switch to warn the user of an eminent restart.

If anyone can tell me of ways to merge .msu files (so I have less searching of the internet to do), then feel welcome to tell me about it.

[abbodi1406]

.msu files are digitally signed, you can't merge, modify or create a new one that the system would accept
 

[LightAlpha263]

4 hours ago, abbodi1406 said:

.msu files are digitally signed, you can't merge, modify or create a new one that the system would accept

Welp, of course.

However, if you extract the .cab files inside the .msu, can anyone merge them?

Also, here's a guide to installing updates via DISM: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows. It installs .cab and .msu files, but part of this guide involves extracting the .msu file and installing via the .cab inside the .msu. If there's no way of merging these .cab files, then I'll go back to simply creating an installer script. I will decide by Tuesday.

Edited July 2, 2016 by LightAlpha263

[abbodi1406]

Sure you can extract cabs and combine them, each will need it's own folder

then, point dism to update.mum (or update-bf.mum)

that's how simplix pack works acrually
 

[LightAlpha263]

I have decided what I will do.

The installer will be via .msu for ease of uninstallation. It will be an installer script. I will begin writing it soon.

[LightAlpha263]

I have decided to instead use the DISM application to install updates. I will begin work on the scripts tomorrow, and I'll release a test version of the scripts for security updates only.

[LightAlpha263]

I apologize for inactivity. I haven't worked on the project in months and there's a bad reason why.

Even after saying "Oh I'll use this method to install the updates", I can't figure out the very best way to install all the updates while making it easy to uninstall them all too. I can confirm that the parts of the scripts where the user can select which categories of updates are installed work. The parts that haven't been made is the part where the central script (a batch script) launches each individual update script for each update category. The part where the central script launches these scripts does exist. However, the individual update scripts do not have any code in them other to echo something like "not done".

So, why?

I already said. I can't figure out how to make the pack easy to install and uninstall. I have two ideas. Either I have an uninstaller which literally uninstalls each update that was added if it was installed, or if I do use DISM to install the update just accept the fact that the updates are non-uninstallable.

I'm again sorry for the inactivity on this project and I will get back to it sooner or later, but due to a very busied life, I haven't been able to. Just in case, expect a few more updates coming soon.

[Tarun]

Were you aware of the availability of WSUS Offline Update?

[LightAlpha263]

I am now aware of it existing, and I see how it basically serves the function of what I desire to make with this package. I will not entirely rule out getting back into finishing this project because I want to make a package that will serve as working to incorporate unofficial packages after Windows 7 becomes unsupported and to allow users to either use the software itself or use it as an update repository. I wish the person making WSUS Offline Update good luck in making his software, but I hope that I will be able to finish mine as well if I soon get back into finishing it.

[pointertovoid]

In case Wsus doesn't allow the user to pick what updates he wants or not (like telemetry), an alternative updater with this feature still looks interesting.