Share this question

Welcome to Teachnovice Q&A, where you can ask questions and receive answers from other members of the community.

This is a collaboratively edited question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

sccm client corrupted after update window update agent

0 like 0 dislike
3,650 views

we had updated windows update agent 7.4.7600.226 in few hundred systems, and found SCCM client has got corrupted (issue with WMI) and SUP entry has got revoked after the upgrade .

we also found these systems stopped even accepting software distribution.

Can you please help us how to rectify these systems using SCCM.

asked Sep 27, 2012 by anonymous  

5 Answers

0 like 0 dislike

Are you saying several hundred machines are now messed up? Generally we see a 1or 2 a month with some type of issue. We hvae fixed it several ways.

  1. Restart, go back to windows update and install and update. We generally find something, driver, office help, something to initiate the install, restart that machine and scan with SCCM. Then we uninstall a patch, scan and make sure it can patch
  2. Stop the Window update service. Delete the Software Distribution folder in the Windows update agent folder. I think we did another one but I can't recall. Then restart the machine. Then it generally will scan and patch. Otherwise we go to windows update. Let it install and scan from there. Then we close it out and rerun the SCCM scan/patch.

Other times we didn't get to them in time and they fixed themselves. Sometimes it coud be the user turned off the machine and then turned it back on and something was hung and not it isn't. A normal restart didn't fix the problem.

answered Sep 27, 2012 by anonymous  
How do you do this.
0 like 0 dislike

I'm having same problem.

I tried this on 2 separate workstations. The 1st workstation I’m not having any issues with. It ran and the log file updated and says it was successful. The 2nd workstation that the KB960089 MS04-09 update is failing is failing to update. I have run the /detectnow 3 times and I receive this error in the log file.

Any suggestions if it keep failing?

answered Sep 27, 2012 by anonymous  
0 like 0 dislike

One thing that might be the problem is that the WU/WSUS client might have a corrupted local catalog.

To fix it this is what I do;

Stop the Windows Update service.

Delete the “C:\WINDOWS\SoftwareDistribution” folder.

Start the Windows Update service.

Wait for about 5 minutes.

Run the command “wuauclt.exe /resetauthorization /detectnow”

Wait for about 15 minutes.

Run the command “wuauclt.exe /detectnow”

Wait for about 15 minutes.

Run the command “wuauclt.exe /detectnow”

Check the c:\windows\windowsupdate.log to make sure it has stopped having errors. If it is still getting errors, run the detect now again. The detect now is needed to force the catalog to continue its download. The catalog these days is far too big to complete downloading within timeout limits after a full rebuild, so I find it takes at least 2 times but I do it 3 times to cover my bases.

After this is stabilized, I restart the SMS Client service, then run an updates scan. That usually fixes those wonky situations.

answered Sep 27, 2012 by anonymous  
0 like 0 dislike

I have verified that the patch is present on the DP’s. I have copied the patch that was downloaded via WSUS and manually installed it lon the client workstation that it was failing on. Yet the client still thinks it needs to install the patch. I have this same issue with the MSXML 4 patch that came out a while back. I will randomly get workstations that fail to install it, yet the patch is already installed. Anyone seen this type of behavior or have any suggestions for me to try?

answered Sep 27, 2012 by anonymous  
The problem here is the patch is already installed but SCCM thinks it’s not there and then fails when trying to install.  Anyone know why this might happen or a way to fix it?
0 like 0 dislike

Trying to deploy the latest Microsoft patches via SCCM WSUS and KB960089 Sql 2005 SP2 update fails on a workstation. I have manually installed the update, but SCCM still thinks the workstation needs to install it. I have manually uninstalled the update, reinstalled and same thing happens. I thought the SCCM client might be messed up. So I removed the SCCM client and then reinstalled it, and it still says the workstations needs the patch. Add/Remove programs has the patch listed.

Has anyone had a problem like this before, and how can I get SCCM to recognize that the patch is installed and not needed?

answered Sep 27, 2012 by anonymous  
...