Updating the Windows Update Agent on Windows 7 clients

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.

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:

Query:

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.

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.

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.

That’s it…

Until next time….

+Ronni Pedersen

26 Comments

Pingback: Windows Update memory leak
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!!

Blake on June 4, 2015 14:50

Looks like both queries are for x64 systems. 🙂

- Ronni Pedersen on June 15, 2015 22:34
  
  Copy paste error… Nice catch 🙂
  
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?

- Ronni Pedersen on June 15, 2015 22:35
  
  This is not an Application, so I would never do that 🙂
  
  - 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
    
Jeppe on June 4, 2015 17:16

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

- Ronni Pedersen on June 15, 2015 22:35
  
  Yep… Copy paste error 🙂
  
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?

- Ronni Pedersen on June 15, 2015 22:36
  
  You can do that… But if you’re client is broken it wont get the update.
  
Manish on June 5, 2015 11:15

Hi Ronni,

Does this apply for SCCM2007R2 inftastructure as well?

Thanks,
Manish

- Ronni Pedersen on June 15, 2015 22:37
  
  The update is for the client OS, so yes.
  
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…

🙂

- Ronni Pedersen on June 15, 2015 22:38
  
  Yep 🙂
  
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

- Ronni Pedersen on June 15, 2015 22:38
  
  You’re 100% right 🙂
  
Cheesus on June 10, 2015 09:05

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

- Ronni Pedersen on June 15, 2015 22:38
  
  🙂
  
Pingback: Windows Update Client: system performance can be decreased during scans « Yuriweb's Weblog
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!

- Ronni Pedersen on February 4, 2016 09:56
  
  That’s why you need an automated solution to build new reference images 🙂
  
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

- 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.
  
Pingback: Windows Update Agent Build Numbers for Windows 7 | Potent Engineer
Pingback: Configmgr How use compliance settings to check windows update agent version (WUA) is older ,Collection and SQL query | Eswar Koneti Blog