Simplifying updates for Windows 7 and 8.1


updated to include link to KB article for Convenience rollup update for Windows 7 SP1 and details on Servicing Stack Update dependency

 

While we’ve spent a lot of time over the past year talking about Windows 10 (including new roadmap details), we know that organizations are still working with Windows 7 too, regularly updating their Windows 7 SP1 images to include the latest updates, app versions, and more.  For those that are involved in that process, you’ve probably seen a display like this too many times:

Win7SP1 WU

New Windows 7 SP1 convenience rollup makes image creation much faster

We’re happy to announce today that we’re making available a new convenience rollup for Windows 7 SP1 that will help.  This convenience rollup package, available to download from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574, contains all the security and non-security fixes released since the release of Windows 7 SP1 that are suitable for general distribution, up through April 2016.  Install this one update, and then you only need new updates released after April 2016.

And since this update can be injected into Windows 7 SP1 media, it’s fully supported to mount a Windows 7 SP1 image (WIM file), then inject this update into it.  See https://technet.microsoft.com/en-us/library/dd744559(v=ws.10).aspx for the details of how to do this.

This convenience update is completely optional; it doesn’t have to be installed and won’t even be offered via Windows Update – you can choose whether or not you want to use it.

To apply this update, you must install the April 2015 servicing stack update for Windows 7 (KB3020369).  You can read more about the Convenience rollup update for Windows 7 SP1 here.

We hope that you find this convenience rollup package useful.  This same convenience rollup also applies to Windows Server 2008 R2.

 

Monthly Rollups

Also today we are announcing that non-security updates for Windows 7 SP1 and Windows 8.1 (as well as Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2) will be available as a monthly rollup (fixes rolled up together into a single update).  Each month, we will release a single update containing all of the non-security fixes for that month.  We are making this change - shifting to rollup updates, to improve the reliability and quality of our updates.

These fixes will be available through Windows Update, WSUS, and SCCM as well as the Microsoft Update catalog.  We hope this monthly rollup update simplifies your process of keeping Windows 7, and 8.1 up-to-date.

 

Simplifying finding and downloading updates

Updates have historically been published on the Microsoft Download Center and the Microsoft Update Catalog.  Security Bulletins have linked directly to update packages on the Microsoft Download Center. To simplify this, within the next few months Windows updates will no longer be available from the Microsoft Download Center.  Security bulletins will continue to link directly to the updates, but will point to the packages on the Microsoft Update Catalog instead of the Microsoft Download Center. Customers that use tools linking to the Microsoft Download Center should follow the links provided in the Security Bulletins or search directly on the Microsoft Update Catalog.

For those who aren't familiar with the Microsoft Update Catalog website, note that it still requires using Internet Explorer at this point because of an ActiveX control used.  Later this summer, we will be updating the site to eliminate the ActiveX control in order to support other browsers.

As always, all updates will still be available via WSUS, SCCM, and Windows Update - this change is only for manual downloads.

Comments (49)

  1. Dave says:

    WOOHOOO

  2. Erich says:

    So many of us have all been asking for this for a while- Thanks for listening Microsoft!!! This will make image updating so much easier.

  3. John says:

    I think I can speak for everyone who still has to deal with Windows 7 by saying Thank You!

  4. Rich668 says:

    Woot! Thank you so much. This will be great for some machines that have to run Windows 7.

  5. Be sure to see https://support.microsoft.com/en-us/kb/3125574 for details on this convenience rollup: Known issues, lists of files changed, etc.

    1. Andreiz says:

      Thank you so much for releasing this :).

  6. Vinh D. says:

    I’m trying to use DISM to inject this into an SP1 WIM and it errors out every time. I’ve tried on multiple indexes, both x86 and x64. Same error each time: 14005 “The manifest file contains one or more syntax errors”. What could possibly be wrong?

    1. Could you please try injecting the updated servicing stack from https://support.microsoft.com/en-us/kb/3020369 first

      1. Max says:

        I had the same DISM injection problem, but I can confirm that it works correctly if the servicing stack update is injected first.

      2. Vinh D says:

        Figured it out after posting, but thanks for the reply. I pays to fully read the release notes and article. 😛

  7. agressiv says:

    Thanks much for this, it is long overdue. One request – please either update Microsoft Catalog to modern technology (no more ActiveX!) or provide direct download links instead.

    1. Later this (Northern hemisphere) summer, we will be updating MU to eliminate the ActiveX control in order to support other browsers.

  8. David del Campo says:

    Does this rollout update include all the Windows 10 nagware? Because if it does it is of no use.

    David

    1. No, the convenience rollup does not contain the “Get Windows 10” updates. (Those updates are primarily for end users; this convenience rollup is intended for IT pros in organizations that want to create Windows 7 images faster.)

  9. Johanna says:

    I’m trying to make a new image with those updates too,
    I got the install.wim of an de_windows_7_professional_with_sp1_x64_dvd_u_676919.iso and try to execute this command, after mounting
    Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\test\packages\Windows6.1-KB3020369-x64.msu /PackagePath:C:\test\packages\Windows6.1-KB3125574-v4-x64.msu /PackagePath:C:\test\packages\Windows6.1-KB3156417-x64.msu
    There are errors at File 2 (the April Rollup), what do I have to change?

    1. You have to inject the servicing stack update by itself first (one DISM command) and then you can inject the others (second DISM command).

  10. Edward_b says:

    Hasn’t the Win 7 convenience update been going on for a while? It’s already at the 4th version [“-v4” in the file name].

    1. The other versions were only used internally for testing, v4 is the first one released to the public.

  11. AJ says:

    Is this available to use with WSUS?

    1. The update is only published to the Update Catalog site, not to Windows Update or WSUS. It can be imported into WSUS manually however.

  12. Michael says:

    After this Update Rollup is installed, there are stil some Security Updates missing. Is there a simple way to get them also downloaded and injected via DISM offline?

    1. All of those additional updates are available via the Microsoft Update Catalog site (http://catalog.update.microsoft.com) mentioned in the blog above.

  13. Samuel Leslie says:

    Great news. Does this impact KB2775511 at all w.r.t. supersedence? I assume not and that both should be installed where applicable? Any suggested ordering or is the servicing stack expected to handle this gracefully irrespective of installation order. Thanks!

    1. The convenience update does include the fixes from KB 2775511, so this does supersede that update.

      1. Samuel Leslie says:

        Thanks Michael. Lastly, is there a list anywhere of the updates and especially hotfixes that are included? I know there’s the file information CSV but that doesn’t explicitly list the included hotfixes. I suppose one could manually correlate the file versions against each KB article of interest but that’s a pretty tedious process. Would be very helpful to cross-check against the hotfixes we already deploy to have certainty as to which we can safely consider as superseded by this update.

    2. See the http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574 link, then select one of the updates to see a full list of the superseded updates on the “Package Details” tab.

      1. Samuel Leslie says:

        Thanks Michael!

  14. zepe says:

    The title mentions both Windows 7 SP1 and windows .1, but I see no mention of 8.1, it’s all about 7.

    1. Windows 8.1 also gets the monthly non-security rollup updates

  15. tester says:

    Does not work after a clean install of Windows 7 SP1. “This update is not applicable to your computer” or something similar. Waste of time. Windows 7 SP1 x64

    1. please make sure your’e downloading the right download to match your PC architecture x86/x64 and you must install the April 2015 servicing stack update for Windows 7 first KB3020369 https://support.microsoft.com/kb/3020369

      1. Jerry says:

        x64 download is for AMD architecture only, no option for Intel x64.

        1. x86-64 is also known as x64, x86_64 and AMD64. The download applies to both AMD and Intel x86-64 CPUs

  16. dmerces says:

    Hi Nathan,
    Today I’m completing thirty days working on windows update troubles. My current and unique alternative, the convenience rollup solution, didn’t work. Now, thanks to your article, I’ve succeed installing the convenience rollup. I love you!
    Thank you very much!

  17. 박양원 says:

    Thank

  18. John Smith says:

    Are you kidding me? So what happens when a particular patch in the rollup causes issues? You have to rollback the entire bundle. Worse, since the bundles are cumulative, you cant patch again until the problem is resolved. In our case, with lots of highly specialized device software, this might mean never, or least till next major OS or application upgrade, which could be years. Did you guys think this through? In the past, we could just uninstall and reject the offending patch and go merrily on our way. I guess if you were small enough, or silly enough to patch manually, this might be useful, but for those of us with automated tools, it really has little value beyond image management. In fact, the number of patches has never been an issue, but fine grained control of what fixes are incorporated will always be an essential requirement. Why don’t you make the rollup optional like before? The result of this is going to be either fully patched systems, or systems not patched at all since the last baseline, and potentially beyond. All or nothing is not simpler or better.

    1. Fixing issues that prevent you from installing a security update are our highest priority. Security-only isn’t cumulative like Monthly rollup is, it just contains security patches for that month. Offering the security-only update allows enterprises to gradually adopt the monthly rollup, or completely avoid if it they choose.

  19. Dave Kelly says:

    What prereqs are needed to be installed to start using the new Rollup process for windows. I read something about needing to install KB3020369 and KB3156417 before you can start using Rollups? is that true. I was just planning on using SCCM2012 & downloading the rollup instead of the monthly patches. If there is a lot more involved, where can I get this information?

    Thanks, Dave

  20. Dave T says:

    Hardware: Dell Inspiron 1720 Core 2 Duo T7500 @ 2.2 GHz. 4GB RAM and 7200 RPM mechanical drives.

    I have a fresh install of Windows 7 SP1 and have now successfully applied this rollup. Excellent. After restart, check for updates is now running and has been running for 17 hours now and nothing has happened. It’s pegged CPU usage at 50%. Prior to the rollup, the update service was using about 2GB of memory. Post-rollup, it is now using only about 200MB so something has certainly changed.

    What is this thing doing? Is it ever going to finish?

    Any tips would be appreciated. It’s an older laptop but still works really good for certain things. ( like loaning to my sister-in-law during her recent extended visit who then filled it full of malware hence the re-install )

    Thanks

    1. try this order:

      Windows 7 SP1 media (or http://support.microsoft.com/kb/976932)
      + Servicing stack update – https://support.microsoft.com/kb/3020369
      + Convenience update rollup – https://support.microsoft.com/en-us/kb/3125574
      + https://support.microsoft.com/en-us/kb/3172605 which includes a WU client update

      1. Phil Hart says:

        Do we really need to hunt down each ‘rollup’ each month and back track through the list of previous update prerequesites? Is there not a single rollup update to install that’s going to be released each month?

        1. The rollups are cumulative, so you only need to install/deploy the most recent one.

    2. Sean Duignan says:

      Hi Nathan,

      The link to the windows 7 roll up pack seems to be broken. Is there any other way I can acquire it.

      Best regard,
      Sean.

  21. andrew says:

    very good

  22. Bruce says:

    Hi Nathan,
    You say; “To apply this update, you must install the April 2015 servicing stack update for Windows 7 (KB3020369). ”
    When I looked at downloads they said x86 and x64 based systems. Does this mean I can’t use either as my system is x32?
    Thank you.

    1. 32bit is x86, so please use that version

  23. Daniel says:

    i have tried to include the updates into my windows-7 iso image with dism.
    Which updates should i implement so that i have a medium thats nearly up-to-date?

    1. Check out this post for details: https://blogs.technet.microsoft.com/askpfeplat/2017/03/06/building-windows-7-images-in-2017. Visiting Windows Update from your Windows 7 reference image will also show you which updates your missing. (If you haven’t done so already, I recommend installing the latest Windows Update agent beforehand.)

Skip to main content