Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»Updating the Windows Update Agent on Windows 7 clients

    Updating the Windows Update Agent on Windows 7 clients

    26
    By Ronni Pedersen on June 4, 2015 Configuration Manager, Enterprise Mobility, Windows and Devices, Windows Deployment

    The last 2 months or so we’ve worked hard with many of our customers to fix a small problem with the Windows Update Agent on Windows 7.

    More Information on this problem:
    http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx

    Last night Microsoft released an update for this specific problem and this blog post will explain how to deploy this fix in your environment.

    Download the update

    Start by downloading the Windows Update Agent version 7.6.7601.18847 for Windows 7 here:

    https://support.microsoft.com/en-us/kb/3050265

    Create Collections

    In this example I’m using two collections as limiting collections that I’ve created earlier.

    clip_image002 Query (x64):

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_G_System_OPERATING_SYSTEM.Version = “6.1.7601” and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

    Query (x86):

    select
    SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_G_System_OPERATING_SYSTEM.Version = “6.1.7601” and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

    And then I’ve created two new collections that I can use to target my deployments:

    clip_image004

    Query:

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_WINDOWSUPDATEAGENTVERSION on SMS_G_System_WINDOWSUPDATEAGENTVERSION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WINDOWSUPDATEAGENTVERSION.Version < “7.6.7601.18847”

     

    Create and Deploy the Software Package

    1. Create a software distribution package for the downloaded Windows Update Agent installation files as shown in the screenshot below.

    clip_image006

    2. Create two programs for the software distribution package. One for x86 and one for x64 like this:
    Wusa.exe “Windows6.1-KB3050265-<platform>.msu” /quiet /norestart

    3. Create a deployment that targets the client computers that do not have the updated version on the Windows Update Agent. Specify the collection that was created in the preceding procedure.

    clip_image008

    4. Don’t forget to monitor the deployment. This update does require to be restarted, so don’t expect to be compliant before all clients has been restarted.

    clip_image010

    That’s it…

    Until next time….

    +Ronni Pedersen

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    26 Comments

    1. Pingback: Windows Update memory leak

    2. Chris Mosby on June 4, 2015 14:40

      First thing I need to do today, and here you have gone and done all the work. Thanks!!

      Reply
    3. Blake on June 4, 2015 14:50

      Looks like both queries are for x64 systems. 🙂

      Reply
      • Ronni Pedersen on June 15, 2015 22:34

        Copy paste error… Nice catch 🙂

        Reply
    4. Jason on June 4, 2015 15:11

      If you wanted to deploy this as an application rather than package; what would be the best detection method?

      Reply
      • Ronni Pedersen on June 15, 2015 22:35

        This is not an Application, so I would never do that 🙂

        Reply
        • MJ on June 17, 2015 19:43

          Actually you can deploy almost anything as an application including Windows Software Updates using a batch script. The batch script should contain Wusa.exe “%~dp0Windows6.1-KB3050265-.msu” /quiet /norestart. Move the batch script and the msu to your desired source location. After that, I usually copy an existing Application deployment that was created using a msi. Just change the name, source location, and replace the install field with whatever the batch file name is, ie myinstallscript.bat. You can do the same for the uninstall field too. The tricky part is the detention method. I will let you search for that as there are a few way to do it. Easier way is using a powershell script, but that depends on your environment polices. With all this being said, the way Ronni explained is by far the easier deployment method.

          More info below:

          https://social.technet.microsoft.com/forums/systemcenter/en-US/5a4a4dc7-845a-41d5-8694-95c3da38578f/how-are-people-deploying-hotfixes-msu-files

          http://didyoutryrestarting.blogspot.com/2014/01/application-detection-method-for.html

          Reply
    5. Jeppe on June 4, 2015 17:16

      Din x86 query er vist forkert 😉 …. X64-based?

      Reply
      • Ronni Pedersen on June 15, 2015 22:35

        Yep… Copy paste error 🙂

        Reply
    6. Adam on June 4, 2015 22:05

      Just curious, this update shows up under the list of updates when you sync the SUP. Can you not simply deploy using software updates?

      Reply
      • Ronni Pedersen on June 15, 2015 22:36

        You can do that… But if you’re client is broken it wont get the update.

        Reply
    7. Manish on June 5, 2015 11:15

      Hi Ronni,

      Does this apply for SCCM2007R2 inftastructure as well?

      Thanks,
      Manish

      Reply
      • Ronni Pedersen on June 15, 2015 22:37

        The update is for the client OS, so yes.

        Reply
    8. Bill Dunn on June 5, 2015 20:16

      I think your X86 query is incorrect…simple because it looks jsut like the x64 query…I think you want the system type to specify x86…

      🙂

      Reply
      • Ronni Pedersen on June 15, 2015 22:38

        Yep 🙂

        Reply
    9. ben on June 8, 2015 07:33

      Ronni, there is in error in your x86 query, it must be

      ….and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

      I think it’s just a c&p error 🙂

      Ben

      Reply
      • Ronni Pedersen on June 15, 2015 22:38

        You’re 100% right 🙂

        Reply
    10. Cheesus on June 10, 2015 09:05

      and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x86-based PC” <<– x86-query

      Reply
      • Ronni Pedersen on June 15, 2015 22:38

        🙂

        Reply
    11. Pingback: Windows Update Client: system performance can be decreased during scans « Yuriweb's Weblog

    12. vegimichel on January 16, 2016 23:40

      For all of you trying to update an old or fresh installed win7:
      Leave it 24hours “checking for updates”. It will find over 200 updates 😉

      Why ms-chat-support didn’t know this! And why do they end a chat as soon as I’m trying to explain it to them to help others. Then they don’t waist time like they did with 10 hours remote control on my pc!

      MS really is trying to let us choose to “upgrade” to win10. On win10 updates are very fast, but on win7 you need to let your pc go searching for updates days!

      Reply
      • Ronni Pedersen on February 4, 2016 09:56

        That’s why you need an automated solution to build new reference images 🙂

        Reply
    13. Peter on July 29, 2016 05:53

      how can i deploy that so i can get Windows Update Agent version 7.6.7601.18847 in windows 7 x64

      Reply
      • Ronni Pedersen on September 27, 2016 17:50

        You can add the updated agent as a package or as part of your build and capture process. I prefer to do it as part of the image build process.

        Reply
    14. Pingback: Windows Update Agent Build Numbers for Windows 7 | Potent Engineer

    15. Pingback: Configmgr How use compliance settings to check windows update agent version (WUA) is older ,Collection and SQL query | Eswar Koneti Blog

    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • Setting OSDComputerName using CustomSettings.ini
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • SCCM: Failed to Get Client Identity (80004005)
    • Updating the Windows Update Agent on Windows 7 clients
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.