How to make a Windows 7 SP1 Convenience Rollup ISO with all updates up to 2016

[c627627]

How to make a Windows 7 SP1 ISO with updates up to OCTOBER 2016

Well the original post is in the spoiler at the end of this OCTOBER 2016 Edition of this topic:



Windows 7 Update is broken on all official Windows 7 installation media released by Microsoft.

If you have already installed Windows 7 and SP1, you will need four files to fix Windows 7 Update:
• April 2015 servicing stack update for Windows 7 file
https://support.microsoft.com/en-us/kb/3020369

• April 2016 Windows 7 SP1 Convenience Rollup update file
http://www.catalog.update.microsoft.com/Search.aspx?q=KB3125574
In case of any problems downloading that file, the same file can be downloaded using Microsoft Internet Explorer add-on from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574
You need to accept the installation of the Microsoft Update Catalog Add-on to be able to Add Microsoft downloads to the download "basket":
64-Bit Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB
[Or for 32-Bit Systems: (KB3125574) 5/16/2016 316.0 MB]


• May 2016 update rollup file
https://support.microsoft.com/en-us/kb/3156417
• July 2016 update rollup file (which includes June 2016 updates):
https://support.microsoft.com/en-us/kb/3172605

Applying these four downloads ↑ and after rebooting, your Windows 7 Update should be fixed.





Next, instructions on how to fix your own Windows 7 installation media. This will shorten the time you need to spend installing Windows 7 from scratch.
[If you are making a 32-Bit installation, you will need to use 32-Bit downloads instead of 64-Bit downloads. Initial set of instructions are for 64-Bit installation.]
Create a new folder called Updates on C: drive.
Download, rename and copy these files so that the contents of C:\Updates folder are these eight files:

• 64-Bit April 2015 servicing stack update for Windows 7 file:
https://support.microsoft.com/en-us/kb/3020369
Windows6.1-KB3020369-x64.msu

• 64-Bit April 2016 Windows 7 SP1 Convenience Rollup update file:
http://www.catalog.update.microsoft.com/Search.aspx?q=KB3125574
In case of any problems downloading that file, the same file can be downloaded using Microsoft Internet Explorer add-on from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574
You need to use IE and accept the installation of the Microsoft Update Catalog IE Add-on to be able to Add Microsoft downloads to the download "basket":
64-Bit Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB
AMD64-all-windows6.1-kb3125574-v4-x64.msu


• 64-Bit September 2016 servicing stack update for Windows 7 file:
https://support.microsoft.com/en-us/kb/3177467
Windows6.1-KB3177467-x64.msu

• May 2016 update rollup file:
https://support.microsoft.com/en-us/kb/3156417
Rename the downloaded file to may2016.msu

[SKIP JUNE 2016 because July 2016 includes all June 2016 updates.]

• July 2016 update rollup file:
https://support.microsoft.com/en-us/kb/3172605
Rename the downloaded file to july2016.msu

• August 2016 update rollup file:
https://support.microsoft.com/en-us/kb/3179573
Rename the downloaded file to august2016.msu

• September 2016 update rollup file:
https://support.microsoft.com/en-us/kb/3185278
Rename the downloaded file to september2016.msu

• October 2016 update rollup file:
https://support.microsoft.com/en-us/kb/3185330
Rename the downloaded file to october2016.msu

In addition to the eight files listed above, in order to make a fixed Windows 7 installation media, you will also need to download and install KB3AIK_EN.iso:
• Windows Automated Installation Kit (AIK) for Windows 7:
https://www.microsoft.com/en-us/download/details.aspx?id=5753
[Microsoft .NET is required to run it.]

MAKE SURE YOU HAVE AT LEAST 20GB OF EMPTY HARD DRIVE SPACE

Copy/paste command lines below and pay strict attention to command lines you are executing, and the process will take about 15 minutes. However, if you experiment with or make a single typo in the command lines below, the process may take several hours since you may have difficulty deleting the installation files from your system as they will get locked if you make a typo. This is why it's important to look over command lines two or three times before executing them.

00. The objective is to fix your own Windows 7 + Service Pack 1 integrated .iso
Owners of retail, non-OEM Windows 7 licenses can download the (now broken) Windows 7 + Service Pack 1 integrated .iso from:
https://www.microsoft.com/en-us/software-download/windows7

01. Extract your own Windows 7 + Service Pack 1 iso to C:\Win7SP1ISO
This means, go to C: drive and create a folder named Win7SP1ISO

02. Make a new folder C:\Win7SP1ISO\offline
This means, go to C: drive and inside a folder named Win7SP1ISO, create a folder named offline

03. Run this command from Command Prompt as an Administrator:
Dism /Mount-WIM /WimFile:C:\Win7SP1ISO\sources\install.wim /Name:"Windows 7 ULTIMATE" /MountDir:C:\Win7SP1ISO\offline

If you have a different version of Windows 7, then replace the word ULTIMATE with the version of Windows 7 you have.
If you do not know which version of Windows 7 you have, use this command to see what is next to Name:
Dism /Get-WIMInfo /WimFile:C:\Win7SP1ISO\sources\install.wim

04. Make sure that April 2015 servicing stack update for Windows 7 file and April 2016 Windows 7 SP1 Convenience Rollup update file are inside C:\Updates:
Windows6.1-KB3020369-x64.msu and AMD64-all-windows6.1-kb3125574-v4-x64.msu

05. Integrate April 2015 Servicing Stack Update:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3020369-x64.msu
[Change name of .msu file if you are integrating a 32-bit / different version file.]

06. Integrate Convenience Rollup update package:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\AMD64-all-windows6.1-kb3125574-v4-x64.msu
[Change name of .msu file if you are integrating a 32-bit / different version file.]

[This step takes a while.]

07. Windows 7 Update will still be broken, unless at least May 2016 through July 2016 rollups are included.
For the five renamed monthly rollup files included inside C:\Updates
may2016.msu, july2016.msu, august2016.msu, september2016.msu and october2016.msu

Execute these five lines:

Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\may2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\july2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\august2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\september2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\october2016.msu

08. Make sure that September 2016 servicing stack update for Windows 7 file is inside C:\Updates
Windows6.1-KB3177467-x64.msu

09. Run this command from Command Prompt as an Administrator:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3177467-x64.msu
[Change name of .msu file if you are integrating a 32-bit / different version file.]

10. Commit the changes and unmount the image:
Dism /Unmount-WIM /MountDir:C:\Win7SP1ISO\offline /Commit


= = = = =

Now you are ready to create a new Windows7Updated.iso which will include all monthly rollups through October 2016:

09. Download and install the Windows Automated Installation Kit (AIK) for Windows 7 under Windows Vista/7/8/10:
https://www.microsoft.com/en-us/download/details.aspx?id=5753
Microsoft .NET is required for Windows AIK to install.

10. Start > All Programs > Microsoft Windows AIK >
Run Deployment Tools Command Prompt as an Administrator.

oscdimg -m -u2 -bC:\Win7SP1ISO\boot\etfsboot.com C:\Win7SP1ISO\ C:\Windows7Updated.iso


Use any burning software to make a DVD using the Windows7Updated.iso which is already bootable.
You can also make a bootable USB, using the Windows7Updated.iso file and
https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool
or
https://rufus.akeo.ie/
[Click on the disk icon next to: Create a bootable disk using ISO Image.]





Original old August 2016 post:

Spoiler

Windows 7 SP1 Convenience Rollup contains all the security and non-security fixes released in more than five years since the release of Windows 7 Service Pack 1 in February 2011.
Here's how to make a single installation ISO which includes all Windows 7 updates up to 2016.


https://blogs.technet.microsoft.com...17/simplifying-updates-for-windows-7-and-8-1/
gives a download link which only works with Internet Explorer and not other browsers:

• http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574

[You need to install the Microsoft Update Catalog Add-on to be able to Add the downloads to download "basket"...]
Update for Windows 7 32-Bit (KB3125574) 5/16/2016 316.0 MB
and/or
Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB

• April 2015 servicing stack update for Windows 7 will be required:
https://support.microsoft.com/en-us/kb/3020369

• Windows Automated Installation Kit (AIK) for Windows 7 will also be needed:
https://www.microsoft.com/en-us/download/details.aspx?id=5753
(AIK can only be installed on a machine where Microsoft .net Framework is already installed.)


= = =


EDIT: DETAILED INTERNET EXPLORER INSTRUCTIONS:

This is the download link which only works with Internet Explorer and not other browsers:

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574

You should get an Internet Explorer pop-up at the bottom of the screen:
This website wants to install the following add-on: 'Microsoft Update Catalog' from 'Microsoft Corporation'.

Click on Install.

[You need to install the Microsoft Update Catalog Add-on to be able to Add the downloads to download "basket"...]

Click on Add next to these two entries:
Update for Windows 7 (KB3125574) 5/16/2016 316.0 MB
Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB

Click on view basket > Download > Browse.... to where you'd like to save these two files > OK > Continue >

The downloads will begin to your chosen directory destination.

= = =

Now rename and copy all the files from above to folder C:\Updates:

• 64-Bit April 2016 Windows 7 SP1 Convenience Rollup update file (KB3125574):
AMD64-all-windows6.1-kb3125574-v4-x64.msu

• 64-Bit April 2015 Servicing Stack Update for Windows 7 file:
Windows6.1-KB3020369-x64.msu

or

• 32-Bit April 2016 Windows 7 SP1 Convenience Rollup update file (KB3125574):
X86-all-windows6.1-kb3125574-v4-x86.msu

• 32-Bit April 2015 Servicing Stack Update for Windows 7 file:
Windows6.1-KB3020369-x86.msu


• Windows Automated Installation Kit (AIK) for Windows 7 file:
KB3AIK_EN.iso


MAKE SURE YOU HAVE PLENTY OF EMPTY HARD DRIVE SPACE


0. Download Windows 7 + Service Pack 1 integrated Disc Images (ISO Files) from
https://www.microsoft.com/en-us/software-download/windows7

Or use your own Win7+SP1 if you already have it.

1. Extract Windows 7 + Service Pack 1 iso to C:\Win7SP1ISO
[Look up how to extract contents of an .iso file if you don't know how.]

2. Make a new folder C:\Win7SP1ISO\offline [EDIT: this means go to C: drive and create a folder named Win7SP1ISO and inside it, create a folder named offline.]

3. Make sure that Windows 7 SP1 convenience rollup .msu file and April 2015 servicing stack update .msu file are in C:\updates

4. Run this command from DOS as an Administrator:
Dism /Mount-WIM /WimFile:C:\Win7SP1ISO\sources\install.wim /Name:"Windows 7 ULTIMATE" /MountDir:C:\Win7SP1ISO\offline

If you have a different version of Windows 7, then replace the word ULTIMATE with the version of Windows 7 you have.
If you do not know which version of Windows 7 you have, use this command to see what is next to Name:
Dism /Get-WIMInfo /WimFile:C:\Win7SP1ISO\sources\install.wim

5. Integrate Servicing Stack Update:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3020369-x64.msu
Change name of .msu file if you are integrating a 32-bit / different version file:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3020369-x86.msu


6. Integrate Convenience Rollup update package:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\AMD64-all-windows6.1-kb3125574-v4-x64.msu
Change name of .msu file if you are integrating a 32-bit / different version file:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\X86-all-windows6.1-kb3125574-v4-x86.msu

[This step takes a while.]


6a. Windows 7 Update is broken unless additional rollups are installed.

Download these three files for your system:

• May 2016 update rollup
https://support.microsoft.com/en-us/kb/3156417
Rename the downloaded file to may2016.msu

[SKIP JUNE 2016 because Microsoft claims it is superseded by July]

• July 2016 update rollup
https://support.microsoft.com/en-us/kb/3172605
Rename the downloaded file to july2016.msu

• August 2016 update rollup
https://support.microsoft.com/en-us/kb/3179573
Rename the downloaded file to august2016.msu

• September 2016 update rollup
https://support.microsoft.com/en-us/kb/3185278
Rename the downloaded file to september2016.msu

Copy your four files, which are now named may2016.msu, july2016.msu, august2016.msu and september2016.msu to C:\updates

Execute these four lines:

Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\may2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\july2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\august2016.msu
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\september2016.msu


7. Commit the changes and unmount the image:
Dism /Unmount-WIM /MountDir:C:\Win7SP1ISO\offline /Commit


= = = = =

Create a new Windows7Updated.iso installation which will include all updates through August 2016:

8. If you haven't already, download and install the Windows Automated Installation Kit (AIK) for Windows 7 on Windows Vista/7/8/10:
https://www.microsoft.com/en-us/download/details.aspx?id=5753
EDIT: Microsoft .net Framework must be already installed on the machine before installing AIK.

Select Windows AIK Setup to install.

9. Start > All Programs > Microsoft Windows AIK.
Run Deployment Tools Command Prompt as an Administrator.

oscdimg -m -u2 -bC:\Win7SP1ISO\boot\etfsboot.com C:\Win7SP1ISO\ C:\Windows7Updated.iso


Use any burning software to make a DVD, which should already be bootable.
Preferably make a bootable USB, using the .iso and
https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool
or
https://rufus.akeo.ie/


* * * * *








* * * * *

EDIT:
FOR ALREADY INSTALLED WINDOWS 7 on which Windows 7 Update is broken:

....However, we can now freely say, based on tests, that if you did not update Windows 7 since April 2015, your Windows 7 Update is very likely very broken.
You need four things to fix it:

• April 2015 servicing stack update for Windows 7 file
https://support.microsoft.com/en-us/kb/3020369

• April 2016 Windows 7 SP1 Convenience Rollup update file

• May 2016 update rollup
https://support.microsoft.com/en-us/kb/3156417

• July 2016 update rollup file (which includes June 2016 updates).
https://support.microsoft.com/en-us/kb/3172605



April 2016 Windows 7 SP1 Convenience Rollup update file can only be downloaded using Microsoft Internet Explorer and no other browser from
http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574

[You need to install the Microsoft Update Catalog Add-on to be able to Add the downloads to download "basket"...]
You need either a 32-Bit file or a 64-Bit file.
32-Bit Update for Windows 7 (KB3125574) 5/16/2016 316.0 MB
or
64-Bit Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB

 

[wagex]

thanks for the info, but are you going to give credit to the original author who took their time to write all this out and figure out how to put it together?

 

[c627627]

wtf wagex?
I didn't copy/paste this thing, I spent last night and this morning putting it together for myself, doing every step on my computer and making it as clear as possible and as usual, just shared my notes with people on the forums... Please post any and all sources if they are easier to follow, I don't think they are, I think my stuff is made so that a four-year-old can follow it.

Here are dozens of others:
https://www.google.com/search?q=How+to+make+a+Windows+7+SP1+Convenience+Rollup+ISO
Essentially the same thing, but mine is different because more people can follow it, I edited things significantly then what most sources posted. ANd they all got it from Microsoft's page, linked at the beginning of my post.
Everything I post on the forums is for myself only, and if it helps others - great.
I use ocforums is cloud storage and when I look stuff up, frequently I hit my own posts eight years down the road...
It's mostly computer stuff but when I needed to install a new stereo, I Googled
replace toyota speakers

and my write up from eight years ago was #1 on Google.
I used it to install a new stereo. My own instructions I wrote for myself. I would have never figured it out had I not written that and posted it.
If it also helped other people do the same for #1 selling car brand in the world, great. But I am not a professional installer.
Haha. What an exercise in vanity. All my posts, including this thread is because I look out for #1 - me.

 

[wagex]

oh lol sorry it just seemed almost exactly like the link you posted the other day my bad.

 

[knoober]

Thanks c627627! I have tried doing this at other times and been unsuccessful. It has been on my project list for a later day for some time. Ive tried a few different tutorials and the successor to nlite for win7 (RT7 lite ?) but still no joy. I have finished your method and am testing in VM as we speak. Under Windows Updates> Installed Updates I have 2 listed for this machine and they are: KB2534111 installed on 8/25 and KB976902 installed on 11/20/2010. Is this the appropriate result? I was assuming I would see a large list of all the updates since the beginning of windows 7?

 

[c627627]

The entire point is that if you correctly follow instructions, you end up with Windows installation media which immediately installs Windows 7 with Service Pack 1 with all the Patches already applied to your system through April of 2016.
When you connect to Windows Update you should only get patches from the last few months, and maybe a couple of others but certainly not hundreds as you would otherwise...

This is a huge deal that will save people hours of time and frustration.

 

[knoober]

The entire point is that if you correctly follow instructions, you end up with Windows installation media which immediately installs Windows 7 with Service Pack 1 with all the Patches already applied to your system through April of 2016.
When you connect to Windows Update you should only get patches from the last few months, and maybe a couple of others but certainly not hundreds as you would otherwise...

This is a huge deal that will save people hours of time and frustration.

Right, but I thought they would still be listed as having been installed. That is where my confusion was. Thank you again

 

[c627627]

It is kind of like after integrating SP1, installs Windows 7 through the beginning of 2011 but pre-2011 patches are not listed as installed because they were integrated and are there as a starting point.

Well with this, your starting point is April 2016. People waste untold number of hours just to get Windows 7 Update to list the hundreds of patches, which they usually can't since it's widely thought that Windows 7 Update is "broken" until you mess with it for hours.

With this you are golden because your starting point includes patches which address Windows 7's problems of actually connecting and listing anything on Windows Update.

If you get *anything* on Windows Update after you install this - you have it made in the shade compared to everyone else who just installed regular Windows 7+SP1 installation - let alone just Windows 7 with no integrated patches...


Depending on the system, you will still need to download and update certain number of updates, but not hundreds of them. Microsoft does not include every single update in their rollup files. But a lot of them are in there, most are in there with this .iso.

 

[Johan45]

Hey C6 would you know if that servicing stack will work with NLite or WinISO. I also wonder if there's any performance change or if it's mostly for security. I only have one motivation for such tasks and that's to score higher.

 

[TechWizard]

Thanks for posting a clear guide on how to do this for the general home user using Home/Pro/Ult Win 7.

I was able to use a similar process to get Windows 7 Enterprise to finally install SP1 and the Convenience Roll Up. Since Enterprise does not have a version with SP1 integrated already I had to download and manually extract the files from the .exe installer you get off of Microsoft's website.

I used this guide to do so.

I then used DISM just as you did to add the April 2015 Service Stack and the Convenience Roll Up. I also added USB3.0 drivers because many of the laptops I am ordering these days only have 3.0 ports and the installers for 7 do not contain them. I used this guide to do that.

So right now it looks like I can install Windows 7 Enterprise 64-bit on any machine with all of the updates till April 2016. However, trying to query for updates is still broken so I can't find any updates after that point without some strenuous troubleshooting on why the Updater is broken still. I let it try to find updates for over an hour after testing the build and it just wasn't going anywhere. I ran the UpdaterTroubleshooter and yet again it fixed the service registration from being missing or corrupt, but updates still ceased to be found. The Software Distrib folder reaches 978MB and freezes there, which I have seen hundreds of times now with how many machines I've seen get stuck.

I am now going to attempt to add June, July, and August Roll Ups as well and see how that goes. I really hope once I do that Windows will simply display that there are no newer updates available and I won't have to deal with the updater at all.

 

[trents]

So the basic problem of the broken updater has still not successfully been addressed yet. It has just been moved forward in time. So we will have to build a new ISO after every round of updates. If someone could figure out what the real problem is and then compile a script to deal with it they could probably make some nice cash. A lot of IT people would donate to that project I have a feeling.

 

[TechWizard]

So the basic problem of the broken updater has still not successfully been addressed yet. So we will have to build a new ISO after every round of updates.

I don't know. Maybe this is only an Enterprise issue? I wish I could say with certainty that it is, but I used an SP1 build at home without being connected to a domain (sometimes our domain has WSUS issues) and the updater was still broken with that version. So I don't see how that can be any different than using Home/Pro/Ult. As I said before, my hope here is that once I add the last 3 Roll Ups it'll bypass having to query looking for any updates at all. It'll just see that it has the latest update and display "There are no new updates available". I HOPE! So much. Because I am nearing my end with this and I absolutely need a way to install fresh copies of Windows on different machines old and new without running into issues that will take hours or days to solve.

 

[trents]

Am I correct in assuming that the automated update process is not broken? It's only when we manually try to install updates that we have this issue. Is that correct? Because it seems that machines that have already had Win 7 installed seem to still be getting the weekly updates without problem, or so it seems to me.

 

[c627627]

You end up with a 3.12GB 32-Bit or a 3.66GB 64-Bit 2016 Windows7Updated.iso file.

It is my belief that the .iso file from there on, can be treated as the original Windows 7.iso file and that the only difference, big picture wise, is that you have 2016 updates integrated.
Yours to modify from there on as you would any Windows7.iso file, using everything else.

It would be helpful if someone tried this and posted if that is not the case, but I certainly would use UltraISO or a similar program to further inject my @Instructions folder which I routinely do to all my .iso files.

Hey C6 would you know if that servicing stack will work with NLite or WinISO. I also wonder if there's any performance change or if it's mostly for security. I only have one motivation for such tasks and that's to score higher.

I believe that you would end up with an identical system if you installed Windows 7, applied SP1, went to Windows Update and applied hundreds of patches Johan45.
The only difference is hours (days?) of hair-pulling frustration that you avoid by installing the Windows7Updated.iso instead, straight away.

 

[Johan45]

OK so you need the files from the update catalogue, I was just asking if NLite or WinISO would integrate them for you? As an alternative?

 

[TechWizard]

Am I correct in assuming that the automated update process is not broken? It's only when we manually try to install updates that we have this issue. Is that correct? Because it seems that machines that have already had Win 7 installed seem to still be getting the weekly updates without problem, or so it seems to me.

No. The automated process is broken. That's how this adventure started in our first thread. Manually applying the updates is the ONLY way I have found around the Updater being broken. That's why I went through the trouble to write out that manual update-by-update guide in the other thread because currently that is the only 100% solution I have to get Windows 7 fully updated.

As I've said - it varies machine to machine. Some install the first few hundred or so updates just fine and then break after SP1. So the work around was to integrate SP1. I did that and now the updater is still broken. I can manually start to apply updates to get it to trigger the 230+ updates that are included in the Convenience Roll Up, but after it finishes whatever amount of updates are in that batch the automatic updater breaks YET again. Not to mention sometimes huge batches of updates fail and it reverts changes. It isn't consistent with any particular update other than after installing SP1 on installations without it.

 

[c627627]

OK so you need the files from the update catalogue, I was just asking if NLite or WinISO would integrate them for you? As an alternative?

I do not know and only someone who finds out the hard way can say so. I can only speculate.
I can tell you this, the many guides on the internet are rife with opportunities for a mistake and let me tell you something:
I copy-pasted a file name, and as you know, the file extension is not included if you try to copy a file name in newer Windows, so the very fact that the .msu was missing resulted in a messed install.

That is why my guide is better, I tell you to specifically rename the files for that reason. Do not deviate an iota from my instructions because after I forgot to include the extension, the many GB of files were locked. So they COULD NOT be deleted from any Windows operating system on my multi boot.
They could not be unlocked by taking ownership.
I had to take special measures to unlock them and delete them.

Therefore, I would not use anything else, I would pay strict attention to every single line of instructions, to end up with Windows7Updated.iso.
Once you have that, only experiment with modifying the final file.

But you are entering a mine field if you experiment on how to get to end result - the 2016 Windows7Updated.iso.
Take the process very seriously and pay attention, and it will be done in minutes.
Make one mistake, and you may end up with hours of fun trying to erase messed up setup files.

 

[TechWizard]

I can tell you this, the many guides on the internet are rife with opportunities for a mistake and let me tell you something:
I copy-pasted a file name, and as you know, the file extension is not included if you try to copy a file name in newer Windows, so the very fact that the .msu was missing resulted in a messed install.

That is why my guide is better, I tell you to specifically rename the files for that reason.

This is very true. Any of the guides you follow out there you have to take with a grain of salt. I basically used them to learn how to use DISM. If you miss the .msu extension using Windows 7 it won't find the file. I have resorted to ALWAYS typing the FULL PATH to the file, even if I'm working in the same directory as the install.wim and boot.wim.

I've played around with it so much now that I can get through the process of adding updates and drivers to my install.wim and boot.wim now in a matter of moments. The only part that is time consuming now is waiting for SP1 and the Convenience Roll Up to add; as well as un-mounting the image and committing the changes.

Honestly, if you are using DISM, just learn the commands and what they do. It is quite simple and once you get the hang of it you aren't bound to using these guides particular file/folder structure. You can just create your own names that make sense to you and put files where you need/want them.

 

[trents]

I do not know and only someone who finds out the hard way can say so. I can only speculate.
I can tell you this, the many guides on the internet are rife with opportunities for a mistake and let me tell you something:
I copy-pasted a file name, and as you know, the file extension is not included if you try to copy a file name in newer Windows, so the very fact that the .msu was missing resulted in a messed install.

That is why my guide is better, I tell you to specifically rename the files for that reason. Do not deviate an iota from my instructions because after I forgot to include the extension, the many GB of files were locked. So they COULD NOT be deleted from any Windows operating system on my multi boot.
They could not be unlocked by taking ownership.
I had to take special measures to unlock them and delete them.

Therefore, I would not use anything else, I would pay strict attention to every single line of instructions, to end up with Windows7Updated.iso.
Once you have that, only experiment with modifying the final file.

But you are entering a mine field if you experiment on how to get to end result - the 2016 Windows7Updated.iso.
Take the process very seriously and pay attention, and it will be done in minutes.
Make one mistake, and you may end up with hours of fun trying to erase messed up setup files.

What? Do you mean copying and pasting from an older to a newer version of Windows? It's certainly not so when copying and pasting within a newer version of Windows.

 

[c627627]

Well if you F2 a file, you only get the file name highlighted - not its extension, right?

Am I correct in assuming that the automated update process is not broken? It's only when we manually try to install updates that we have this issue. Is that correct? Because it seems that machines that have already had Win 7 installed seem to still be getting the weekly updates without problem, or so it seems to me.

Absolutely (most) already running Windows 7 installations are functioning fine and will continue updating until 2020.
I am of the opinion, however, that fresh installations of original Windows 7 [or original Windows 7 with SP1 integrated] would still result in hours of inability to get your Windows 7 up to 2016 state.

I do not think this has to do with manual vs automatic.
it has to do with whether your machine's starting point is 2016 (with instructions above) or 2009 (original Win7) or 2011 (Win7+SP1) - if your starting point is 2011 or earlier installation, you are likely in for a multi-hour problem situation because Windows 7 Update itself needs to be newer than that (updated) to get hundreds of patches through correctly.

That is why fresh install of 2016 Win7 iso is absolutely the quickest way set up Windows 7 on any machine.