• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

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

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

derniwi

New Member
Joined
Oct 19, 2016
Hi,

I found a work around.
First, I integrate Internet Explorer 11. Than the following update packages:
Code:
KB3020369
KB3125574
KB3156417
KB3172605
KB3179573
KB3185278
KB3185330

And finally:
Code:
KB3177467

Then I commit the changes and unmount the image. Now I got a working install.wim. With this one I boot the virutal machine and let Windows search for updates like before.
If everything is done, the VM shuts down.

Now I create the install.wim from scratch, starting again with IE11.
Than the following packages:
Code:
KB3020369
KB3125574
KB3156417
KB3172605
KB3179573
KB3185278
KB3185330

Now all the downloaded packages will be installed. Since the KB3177467 isn't integrated yet this seems to be no problem.
After this the KB3177467 will be integrated. Now the image can be commited and unmounted. And I get a complete install.wim with all current (on our WSUS) available patches.

It should be possible to integrate .NET framework, but since I have a software distribution system whit some applications depending on .NET, this will be installed there and not integrated - I had to to a lot of changes in the distribution system ;)

I haven't tested yet, but I will report the status here.

Thanks for the list.

Regards
Nils
 

trents

Senior Member
Joined
Dec 27, 2008
Seems like several variations on the theme are being worked out now by others.
 

trents

Senior Member
Joined
Dec 27, 2008
This is not new. I'm experimenting with formatting. I just want to see how a copy and paste from MS Word will affect the format of this document and what I could do in the way of altering that in a post window. Wordpress is just too clunky unless you have a lot of experience with it.
______________________________________________________________________________________________________________

Broken No More: A Fix for the Fractured Windows 7 Updater
By Harry Trent (“trents” is my handle on the forum)

Background: Since shortly after the appearance of SP1, the Windows 7 update process has been broken on and off. Not all have been affected by this problem (or are at least not aware of it) but many who do from scratch installations of Windows 7 and manual updating are very familiar with it. System builders and IT professionals needing to install Windows 7 with all current updates in an efficient manner have found this very frustrating. Microsoft has finally included a fix inside their Windows 7 July 2016 monthly update rollup. The catch is, if the updater is already broken you won’t get the fix online through the Windows auto update process or by using standalone updaters offered for download by Microsoft. The fix must be applied by alternate means. This tutorial will give you the information you need to do that and to build a custom slipstreamed Windows 7 SP1 installer. These directions do not apply to pre SP1 versions of Windows 7 install media. SP1 was released in March of 2010, only 5 months after the OS’s initial public release. That said, this tutorial will work for the vast majority of people possessing Windows 7 install media and could even be adapted for those who have pre SP1 install media.

Checking for a broken updater: To do this, go to Control Panel and click on Windows Update. When the Windows Update user interface window opens, click on "View update history" in the left viewing pain. Check the most recent date from the list of updates displayed. If the latest update is significantly behind the calendar them something is wrong with the Windows updater unless that is, you have had your computer turned off for a long time. Microsoft issues updates one or more times a month. In addition, a broken updater will manifest itself when you attempt to check for Windows 7 updates. None will be found, not even if you wait for a long time.

Purpose of the fix:
To build a slipstreamed installer (USB or DVD) with the fix for the broken updater built in. Slipstreamed installer media will significantly speedup subsequent reinstallations since many or most of the updates issued by Microsoft over the years since SP1 are already rolled in. Those wanting to fix the broken Windows 7 updater on an in place installation should look at WSUS offline, a tool many have found effective for this purpose. It can be downloaded here: http://download.wsusoffline.net/. Not any one fix for in place installations seems to work for everyone.

What the fix does not do: It does not include every single update available for your system. It only includes the updates Microsoft has made available for offline installation through October of 2016. After completing the installation via the slipstreamed installer as outlined in this tutorial, Windows 7 Update will still find many remaining updates available for your specific system. You may even find 100+ updates remaining but the slipstreamed .iso significantly reduces the size of that task. Most importantly, the Windows Updater will now work as it should!

Skill Level Needed for the Fix: There are actually two versions of this tutorial. The first version targets those with intermediate level computing skills. It is rather detailed and employs considerable hand holding. Those with advanced computing skills may find it rather tedious so there is a more “bare bones” version beginning on page 7. Script monkeys may want to take the fast lane and skip to that point.
Building a Custom Slipstreamed Windows 7 Installer DVD or USB Flash Drive

An overview of the process:
1. Folders are created on the host computer (the one used to make the new Windows 7 installation DVD/USB) to house the contents of your Windows 7 SP1 installation media. Updates will be included in the final customized DVD/USB installation.
2. Updates are downloaded and placed in the appropriate folder for integration into the new Windows 7 SP1 build.
3. Using the Windows Command Prompt Terminal, DOS commands are used to integrate the updates into the existing Windows 7 SP1 build. This is called "slipstreaming."
4. The new slipstreamed Windows 7 SP1 build is then burned onto either a DVD optical disk or a USB flash drive which will serve as the new installation media.
5. The new installation media build is then used to install Windows 7 on the target computer.
6. After completing the installation using the new slipstreamed installer, remaining updates are installed with the Windows Update tool which can be found in Control Panel.

FAQ: Can this custom slipstreamed ISO build process be executed from a Windows 10 computer?
Answer: Yes. The build process is independent of the version of Windows it is running. Note that if you are using a computer running a version of Windows previous to Windows 8 to do the build, the process is different at one point. Since earlier versions of Windows do not have native ability to mount an ISO you will need to use third party software to mount the "AIK" ISO for installation. There will be a note about this when you get to that stage.

Note: It is a good idea to read the entire tutorial before beginning the building process and installation. Know where you're headed before you start.

Preparation
1. Check your hard drive to make sure it is not almost full. You will be adding several large files to the drive during this process and you will also need some hard drive space for this process.

2. Check that you have an active internet connection.

3. Have either a writable DVD disk or a flash drive of at least 8GB on hand. The total size of your new slipstreamed ISO will be roughly 4GB. It will vary depending on what version of Windows 7 you are slipstreaming, whether Ultimate, Enterprise, Pro, Home Premium, 64-bit, 32-bit, etc. and how many upgrade elements you are adding. A single layer DVD writable disk will hold about 4,482 MB of data.

4. Create the following two folders in the root directory of the C drive: updates and Win7SP1ISO.

5. Create another folder inside of the Win7SP1ISO folder named offline.

So, the directory paths would look like this: c:\updates and c:\Win7SP1ISO\offline.

6. Download and install the Windows 7 SP1 Convenience rollup which can be found here: http://www.catalog.update.microsoft.com/Home.aspx.

In the update catalog search window type in KB3125574 and click on the search button. When the download basket window pops up, click on the download button at the far right end of the line showing the appropriate version of Windows 7 you are using. Another window will pop up. Click on the long file name. Another window will open with download options. Choose “Save.” Do not choose “Open with.”

If for some reason the link cited doesn’t work, try using Internet Explorer with the following older link to download and install the Windows 7 SP1 Convenience Rollup from Microsoft: http://catalog.update.microsoft.com...459594)(TnL5HPStwNw-VOVhO0Nm5L6mfziCkqwZHg)()

Note: Other browsers will not work with this link.

You will 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." Now you should be able to add downloads to the "basket."

Click on "Add" next to either the first or third entries: Update for Windows 7 (KB3125574) 5/16/2016 316.0 MB or Update for Windows 7 for x64-based Systems (KB3125574) 5/16/2016 476.9 MB.

(The first entry would be appropriate if you are running a 32-bit version of Windows 7 and the second if running a 64-bit version.)

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

Go to the location where you saved this file and double click on it to start the installation.

7. Download the appropriate bit version of the April 2015 servicing stack update: https://support.microsoft.com/en-us/kb/3020369 and move it to c:\updates.

8. Download the appropriate bit version of the September 2016 servicing stack update: https://support.microsoft.com/en-us/kb/3177467 and move it to c:\updates.

9. Download the Windows Automated Installation Kit (AIK): https://www.microsoft.com/en-us/download/details.aspx?id=5753 and move it to c:\updates.

STOP! Check and make sure these four files are in c:\updates:
X86-all-windows6.1-kb3125574-v4-x86.msu or AMD64-all-windows6.1-kb3125574-v4-x64.msu
Windows6.1-KB3020369-x86.msu or Windows6.1-KB3020369-x64.msu
Windows6.1-KB3177467-x86.msu or Windows6.1-KB3177467-x64.msu
KB3AIK_EN.iso

10. Install the AIK from the KB3AIK_EN.iso file. This will require that you have an earlier version of Net Framework installed on your computer. If your host computer is running Windows 10 you will likely not have this, but you can get it here: https://www.microsoft.com/en-us/download/details.aspx?id=6523.
• Once you have Net Framework installed, right click on the KB3AIK_EN.iso file in the c:\updates folder.
• In the menu that results, left click on "Mount." This will mount the ISO and allow you to see and access the files it contains. (Note: If you are on Windows 7 and need to mount an image you can use Virtual Clone Drive available at https://www.redfox.bz/en/virtual-clonedrive.html). Once Virtual Clone Drive is installed you can mount and unmount .iso files with Windows File Manager just like with later versions of Windows. A mounted .iso will show up as a new (virtual) optical drive in File Manager.
• Double left click on the startCD.exe file in that list. This will launch the installer user interface.
• From the user interface, left click on "Windows AIK Setup" in the menu at the left side. This will start the installation process. Just accept the default settings. If you check the list of programs installed from the Windows Start button you will now see "Microsoft Windows AIK" app in the list of programs. We'll use it later.

11. Download the May, July, August, September and October update rollups from Microsoft, rename them and put them in c:\updates:
https://support.microsoft.com/en-us/kb/3156417 Rename the downloaded file to may2016.msu
https://support.microsoft.com/en-us/kb/3172605 Rename the downloaded file to july2016.msu
https://support.microsoft.com/en-us/kb/3179573 Rename the downloaded file to august2016.msu
https://support.microsoft.com/en-us/kb/3185278 Rename the downloaded file to september2016.msu
https://support.microsoft.com/en-us/kb/3185330 Rename the downloaded file to october2016.msu

Note:
The June update rollup is not needed.

12. HALT! You should now have nine files in c:\updates. If not, go back reread the instructions from the beginning in this Preparation section.
AMD64-all-windows6.1-kb3125574-v4-x64.msu (or the 32-bit equivalent)
august2016.msu
• july2016.msu
• KB3AIK_EN.iso
• may2016.msu
• october2016.msu
• september2016.msu
• Windows6.1-KB3020369-x64.msu
(or the 32-bit equivalent)
Windows6.1-KB3177461-x64.msu (or the 32-bit equivalent)

13. Copy the files and folders from your existing Windows installation media to c:\Win7SP1IS0 using Windows File Explorer. If you don't have the physical Windows 7 installation media but do have a valid retail product key [OEM keys will not work for the download], download the ISO of the version you need from: https://www.microsoft.com/en-us/software-download/windows7.

14. Once downloaded, view the ISO's contents by right clicking on the file name and left clicking on "Mount" from the menu.

15. Select and copy all the files and folders contained in the ISO to c:\ Win7SP1ISO.

16. Unmount the ISO using Windows File Explorer to locate the virtual optical drive that mounting the ISO produced. It will be the one showing the Win 7 title. Right click on that item and then left click on "Eject" to unmount the ISO.

Building the new custom Windows 7 ISO
Now hear this! Now hear this! If any of the following Command Prompt scripts fail to execute then check your spelling. Either you have misspelled a folder name, a file name or the Windows product version name. Typos are incredibly easy to make! Check also to make sure you haven't chosen the incorrect bit version of a file in relation to the bit version of your intended build.

1. First, mount the offline Windows image for renaming and slipstreaming using the following string in Command Prompt with administrator privileges:
Dism /Mount-WIM /WimFile:C:\Win7SP1ISO\sources\install.wim /Name:"Windows 7 ULTIMATE" /MountDir:C:\Win7SP1ISO\offline

Heads UP! If you are using a different windows version than ULTIMATE, make sure you have changed the product name. Windows Home Premium should be rendered as one word, "HOMEPREMIUM."

After any necessary editing of the command string referred to in step 1 to make it correspond to your version of Windows 7, open the Windows Command Prompt terminal with administrator privileges. Then copy and paste the command string into the terminal window and hit the Enter key. When this operation finishes, don't close the terminal. We have some more commands to execute. Don't close the terminal until after step #5.

WARNING! Be very careful that when you go to do a copy and paste operation you get all of but no more than the entire DOS command string. Check that every time! It's very easy to chop off a character or two or add in an extra space.

2. Now, integrate the April 2015 Servicing Stack Update by executing one of these DOS command strings in Command Prompt terminal:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3020369-x86.msu

Or, if building a 64-bit custom ISO:

Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3020369-x64.msu

3. Next, integrate the Convenience Rollup update package with this command in terminal:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\X86-all-windows6.1-kb3125574-v4-x86.msu

Or, if you are building a 64-bit version custom Win 7 ISO:

Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\AMD64-all-windows6.1-kb3125574-v4-x64.msu

Note: This operation may take a while. Terminal will display a progress report but even that can take a bit to appear. Be patient. Wait for the DOS prompt before proceeding further.

3. Now, it's time to integrate the May, July, August, September and October updates by executing these four commands, which can be copied and pasted as a group into terminal. No need to hit the Enter key this time unless terminal seems to stall out before any of these monthly package integrations complete, which happens occasionally:
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


4. Next, we need to inject the September servicing pack update as we did in step 3 with the April 2015 counterpart with this terminal command:
Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3177467-x64.msu

Or, alternatively if building a 32-bit ISO:

Dism /Image:C:\Win7SP1ISO\offline /Add-Package /PackagePath:C:\updates\Windows6.1-KB3177467-x86.msu

5. Now we need to commit the changes and unmount the image with this terminal command:
Dism /Unmount-WIM /MountDir:C:\Win7SP1ISO\offline /Commit

When this operation has finished, close the Command Prompt terminal.

6. Finally, we need to build the new custom slipstreamed Windows 7 image and place it in the root directory of the system drive (c:\).
• Using the Windows Start button, locate the "Microsoft Windows AIK." folder in the list of programs installed on your computer.
• Left click on the drop down arrow to view the folder's contents.
• Right click on "Deployment Tools Command Prompt."
• Hover on "More" with the mouse pointer and left click on "Run as administrator" (Windows 8/8.1/10) or, if using Windows 7, just right click on the Deployment Tools Command Prompt and left click on "Run as Administrator."
• In the Command Prompt terminal window, copy and paste this command: oscdimg -m -u2 -bC:\Win7SP1ISO\boot\etfsboot.com C:\Win7SP1ISO\ C:\Windows7Updated.iso

When the operation is complete close the Command Prompt terminal.

Creating installation media from the new custom Windows 7 ISO

There are several excellent freeware tools available to create a bootable Windows 7 USB. For example, Rufus - a USB installation media creation tool: https://rufus.akeo.ie/

Leave the default settings as they are in Rufus and:
1. Select Device [target USB]

2. Make sure the box next to Create a bootable disk using is checked and that ISO image is selected and click on the disk icon to browse to Windows7Updated.iso > Open

3. Click on Start > OK

If you would rather make DVD installation media then you can do that with the Windows built-in ISO burner. Place the blank writable DVD disk in the drive. With Windows File Explorer, find the custom .iso file you created and right click on it. Left click on "Burn disk image" from the menu. When the next window pops up click on "Burn."

A word of advice is in order here, however. It might be a good idea, if you choose to make a USB installer, to also make a DVD installer just to cover all the bases. DVD-based install media seem to have fewer compatibility issues with various systems than do USB-based install media.

Installation of Windows 7 would proceed identically as with the original retail or OEM disk. A few thoughts here:
• It would probably be a good idea to disconnect the target computer from the internet and not reconnect until you are done with the installation and are ready to download any remaining updates. This will prevent Windows Update from asserting itself unexpectedly in a way that will sabotage the effort to create an unbroken update mechanism.
• Install the new custom ISO on a clean hard drive – either a new one or a formatted existing one.
• Disconnect all nonessential storage devices from the target computer, especially secondary hard drives and flash drives, until the installation is finished. Windows may sometimes spread the installation to non-system storage devices. Not having extra drives reduces the risk of accidental formatting.
• When prompted how you want to configure Windows updates, SELECT: "Ask me later".
• The updates which were injected into the build install transparently as if they were a part of the original SP1 version. You won't see them listed in the update history of the Windows Update tool.
• The slip-streamed updates that were injected are not all-inclusive. Depending on your system's hardware and whether or not you elect to include the optional updates Microsoft makes available, there may be many more that can be added. It may be advisable to avoid the optional updates and especially hardware driver updates… unless you are already having problems.
• Preventing future automatic update installation may be wise so you can be in control when they are installed. To that end, modify the default Windows Update settings so that updates are not automatically downloaded and installed.
rufus.jpg

Cleaning up: You now have the option to remove all project folders to recover the disk space they used. Since the project folders contain operating system components, Windows will not just let you delete them with File Manager and clicking on "Delete." To delete them you must use Command Prompt with administrator privileges to run these two commands: RD /S /Q c:\Win7SP1ISO and RD /S /Q c:\updates

You also have the option to delete the file Windows7Updated.iso from the root directory of the system drive the usual way (with File Manager) but first check to make sure it isn't still mounted. To check for this, use Windows File Manager to see if there is an extra optical drive showing in the left viewing pane. If so, right click on it and left click on "Eject".

Note: Windows 7 will not reach End-Of-Life status before January 14, 2020.

Many thanks to forum members c627627 and TechWizard who spent many hours working out the essentials of this process and who were the “script monkeys” behind it from the beginning.
 
Last edited:

MurdoTM

New Member
Joined
Nov 16, 2016
Great guide. Will certainly save alot of time when doing windows installs. I have been using Win Toolkit to keep images up to date but by following the guide it has meant that the install.wim file is alot smaller due to the rollup updates rather than the 300+ individual updates that I had to integrate using WTK. I tried to inject IE11 but ran into the same problem as someone on the forum where after injecting September Service stack update it would give errors when running DISM to inject them so had to start from scratch & inject IE11 & the updates relating to IE11 first then inject all the rollups minus September Service Stack. I then tested the image via VM & did a search for updates & it found 56 important & 6 optional updates to be installed dating from 2013 right up to today. does anyone know if it would be possible to inject all these updates into the image using DISM like the rollup updates or will i have to go back to WTK to get all these update integrated which will take longer to complete.
 

derniwi

New Member
Joined
Oct 19, 2016
This is what I'm doing with the install.wim:
1. integrate Internet Explorer 11
2. integrate the patches (KB3020369, KB3125574, KB3156417, KB3172605, KB3179573, KB3185278) from the first entry of this thread except KB3177467
[3. integrate drivers]
4. integrate other Microsoft patches, depending Windows edition
6. integrate KB3177467

After integrating KB3177467 it is nont possible to add any package, because this patch requires a restart of the system - which is a problem in case of an offline image. Confiming changes, unmounting and remounting the install.wim will not help.

For the first part (integrating IE11) I integrate the following patches, depending on system and system lanugage:
x86 German:
Windows6.1-KB2533623-x86.msu Windows6.1-KB2670838-x86.msu Windows6.1-KB2729094-v2-x86.msu Windows6.1-KB2731771-x86.msu Windows6.1-KB2786081-x86.msu Windows6.1-KB2834140-v2-x86.msu IE-Win7.cab IE-Hyphenation-de-DE.MSU IE-Hyphenation-en.MSU ielangpack-de-DE.CAB IE-Spelling-de-DE.MSU IE-Spelling-en.MSU

x86 English:
Windows6.1-KB2533623-x86.msu Windows6.1-KB2670838-x86.msu Windows6.1-KB2729094-v2-x86.msu Windows6.1-KB2731771-x86.msu Windows6.1-KB2786081-x86.msu Windows6.1-KB2834140-v2-x86.msu IE-Win7.cab IE-Hyphenation-en.MSU IE-Spelling-en.MSU

x64 German:
Windows6.1-KB2533623-x64.msu Windows6.1-KB2670838-x64.msu Windows6.1-KB2729094-v2-x64.msu Windows6.1-KB2731771-x64.msu Windows6.1-KB2786081-x64.msu Windows6.1-KB2834140-v2-x64.msu IE-Win7.cab IE-Hyphenation-de-DE.MSU IE-Hyphenation-en.MSU ielangpack-de-DE.CAB IE-Spelling-de-DE.MSU IE-Spelling-en.MSU

x64 English:
Windows6.1-KB2533623-x64.msu Windows6.1-KB2670838-x64.msu Windows6.1-KB2729094-v2-x64.msu Windows6.1-KB2731771-x64.msu Windows6.1-KB2786081-x64.msu Windows6.1-KB2834140-v2-x64.msu IE-Win7.cab IE-Hyphenation-en.MSU IE-Spelling-en.MSU

For the drivers I currently add the Intel USB 3 driver which is needed for some new machines without USB2 ports. They need an USB 3 driver to detect the S-ATA 3 ports... :confused:
I also add the Intel network stack which is used in a lot of machines, just to have a network connection for updating and receiving drivers from Microsoft.
I also add these drivers to the second image in the boot.wim (index 2, Windows Setup).

I'm still testing the installation but it seems to work pretty well.

I still have a problem adding support for NVMe, because I currently have no system for testing purpose, but after adding the Microsoft patches KB299094 and KB3087873 to the boot.wim index 2 the setup won't find any hard disk. I do not have an NMVe drive, but it also didn't find the S-ATA or IDE drives. I'm testing with VirtualBox 5.1.8. Also there is support for NVMe drives in VB, a configured NVMe hard disk will not be found in VB.
 

MurdoTM

New Member
Joined
Nov 16, 2016
Managed to get all the updates injected including all the optional updates. So when I go to check for updates after a fresh install there are only 4 updates left to insrall, the one for validation which cant be injected & Malicious Software Removal tool & .net framework 4.5.2 & 4.6.1. Can .net 4.6.1 be injected or will it only install if setup as a run once after windows install is completed?
 

derniwi

New Member
Joined
Oct 19, 2016
AFAIK it is not possible to integrate .NET, just add it as a RunOnce after the Windows setup. But this means there are also no updates integrated for .NET.
 

AngelfireUk83

Member
Joined
Nov 7, 2004
I have an issue with my laptop and Windows 7 it will not install any Monthly Roll up since I installed Windows 7 I've done the required things to get WU to work and it's downloaded and install most of the updates heck it even updates Security Essentials but it will not download and install any roll up one any ideas???
 

knoober

Member
Joined
Mar 18, 2015
I've done the required things to get WU to work

What steps have you taken? This will help to know what you will need to do next.

I recently redid the procedure outlined in the 1st post (2 days ago) and have a working installation disc again. I saw several convenience rollups in Windows Update also, and they *appear * to have installed correctly.
 
OP
c627627

c627627

c(n*199780) Senior Member
Joined
Feb 18, 2002
We have reports that Microsoft has now, in March of 2017, for the first time actually fixed Windows 7 update, for reasons unknown as to 'why' now.
Outlined procedure is still useful however to have an all monthly rollups included ISO, so it will take less time to install.
 
Last edited:

AngelfireUk83

Member
Joined
Nov 7, 2004
What steps have you taken? This will help to know what you will need to do next.

I recently redid the procedure outlined in the 1st post (2 days ago) and have a working installation disc again. I saw several convenience rollups in Windows Update also, and they *appear * to have installed correctly.

I did the required things in 1st post as you did when I installed a fresh copy of Win 7 on the laptop and I proceeded to install the updates it found and restarted when required but it just won't install the roll ups it did install I think Octobers roll up but after that November on wards it just won't says it FAILED, But it does install any small updates for like Windows Defender and other small things I will test to see if they have actually fixed in as C627627 says above.
 

knoober

Member
Joined
Mar 18, 2015
I see. You had already installed Windows. My comments were based on making a custom ISO with WAIK. Ive never tried to fix Windows once it was already installed. All I can say is that making a custom ISO definitely worked. I am glad you got your updates anyway, even if it was individually i stead of in the rollup.
 

derniwi

New Member
Joined
Oct 19, 2016
Hi,

it should be possible to update an already installed Windows 7 with SP1 with the patches from the first thread.

You have to download all the patches and then disconnect your computer from the internet (remove network cable or deactivate the network connections) and then reboot. The reboot is important since the Windows Update Service and other components may have started to work in background. If you reboot the can't download the update catalog and stop their work. So installing the patches will be done fast, only the big cummulative patch needs several minutes up to half an hour. After installaing all the updates reboot and connect your computer to the internet or enable the connections and let Windows search for other updates.

Regards
Nils
 

AngelfireUk83

Member
Joined
Nov 7, 2004
So Windows 7's March 2017 Rollup came up on the laptop and it again won't install but the small ones did I went as far as to run Disk Clean witin 7 via admin and it found 23.6GB of stuff it could free up so I ran that, but my free space under Computer didn't even go up after a reboot??? so I ran SFC /scanow via command prompt under Windows and that got stuck at 22% and said if found some files that were corrupt and couldn't fix them. So I decided to run it again under Windows Safe Mode and it went through fine didn't even stay on screen long enough so I assumed it was fixed tried WU again nothing still won't install??
 

knoober

Member
Joined
Mar 18, 2015
Here is some info on using DISM to cleanup your disc https://www.sevenforums.com/tutorials/122262-windows-7-sp1-disk-cleanup-tool.html. Option 2 is what I am specifically referring to. My thoughts here ate thst maybe an old partially installed update is causing something to hang. Im not really holding out a lot of hope, but it may be worth a shot.

As for sfc /scannow : it is no wonder if worked in safe mode, because only the barest system is being used. I would try again from inside the full OS and if it doesnt finish then consider backup of important data + reinstall Win7. Dont forget to make an ISO and bootable USB using the steps in the OP. You can troubleshoot all day long if you want but wouldn't a fresh install cure everything and give you the opportunity to create a clean backup? I can understand not wanting to if you dont have to but with /scannow out of commission.... Im not sure what other choices you've got. Good luck
 

papadan

Member
Joined
May 27, 2013
Location
Indian Lake Estates, Fl.
I hadn't booted up my Win 7 sys. for a long time. On Wednesday I booted it & for the first time since March of 2016 it came up & told me there was 30 updates avail. I had to install in groups to get them to go, but all 30 finally went. I can report that for me updates do work again.

Dan
 

TechWizard

Member
Joined
Nov 16, 2004
I'm still having issues with certain updates.

I got another large batch of systems to image and for the most part I was putting Windows 10 on them... now I've got a few I needed to put Windows 7 on and the last 8 updates won't go on the two systems I have here (both are HP ZBook G2).

One of them was BSOD'ing during updates and throwing a 7E - I assume it was because it was attempting to update the Chipset and nVME driver - considering these laptops have PCIe nVME drives in them I assume they don't like the Microsoft driver. Once I did that a few more updates cleared, but the last 8 are just being a complete pain and failing over and over.

Looks like I'll have to update my ISO yet again to include the rest of Roll Ups from Nov 2016 - March 2017. Last Roll Up in my install.wim is October 2016.
 
OP
c627627

c627627

c(n*199780) Senior Member
Joined
Feb 18, 2002
Yes, I think it's a given that updates will never go through on all systems, making yearly ISOs is the best quick way around that problem, even if Microsoft fixes the Update because, think of how much time you save not waiting for downloads to complete? Even on very high speed connections, it takes time to download these massive updates.
Thanks for reporting.