System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Software Updates Management
>
Microsoft Updates suddenly stops at 50% of downloading.
Microsoft Updates suddenly stops at 50% of downloading.
- Hi.
We have a fully working environment with SCCM 2007. We update 150+ servers and approx 650 clients through CM and it usually works like a charm. This mounths updates worked fine too, no problem distributing them as usual with CM. BUT, i have now gotten 3 cases where all the updates except one has been downloaded to the client. The last update will not pass 50% of downloading no matter how long we wait. So, what i see in the Software Updates Installation progresswindow is now several updates with status "Preparing for installation" and one with status "Downloading 50%".
I have of course done some checking to solve the problem like checking logs, connectivity, errorreports etc .. ..
Usually when there is some kind of errors i find the answers in the logs but this time they are clean as far as i can see.
The strange thing is that all updates except one were downloaded smoothly as always and that´s on approx 650 clients.
The update that won´t be downloaded is Kb968389. Any known issues with that one ? Since that update won´t reach 100%
the other updates won´t be installed.
Any suggestions ? Have never experienced anything like this this before.
I´m a beginner at this (SCCM) but this far i really like it :)
Thanks in advance
Best regards
Stefan
(SCCM 2007, WSUS 3.0, Win XP Professional SP3)- Changed TypeEric Zhang - MSFTMSFT, ModeratorThursday, October 29, 2009 10:23 AMno response
All Replies
- This is a common problem actually. I have never found a "good" solution for it. I generally run a repair on the client and that seems to fix it but that's not the best solution I know.
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - Hi,
Is there any error in Windowsupdate.log on the client? - As this thread has been quiet for a while we will be changing the issue type to ‘General Discussion’.
If you wish to return to this question you can go ahead and change the type back to ‘Question’. Then you can edit your initial post and change the radio button at the top of the post editor window.
If the issue has been resolved, we’d love to hear your solution. By sharing your experience you can help other community members facing similar problems.
Thanks! - This just started for me aswell! After releasing all October patches and parsing them into my image. KB968389 just wont download and install. It stops at 50% with no apperent errors in any logs. Has any one else experienced this?
It was not a problem to install this update into my image before releasing october patches... - I have the same problem with that exact patch failing at 50% on a handful of machines. I've tried a repair on the clients and it does not work. I've also installed that patch by hand, rebooted, and SCCM still thinks it's stuck at 50%, but the patch is in the CCM cache. Anyone else have an idea? I may try to clean the SoftwareDistribution folder up next. One note, it appears the KB968389 patch was an optional update from back in August. I don't recall seeing these problems until October, which is when MSFT released the Security Patch MS09-059 (KB975467) and there is clearly some metadata tying these two patches together. Is it possible that the WU detection method for these two patches has a problem?
For now I've removed the 968389 patch from my deployments, but it appears some machines are still stuck with it. - Hi guys ,
I have got it solved yesterday !
You need to download the latest Windows update Agent 7.4.2600.x and deploy it to your machine having trouble .
This solves the issue . It seems to be a problem between the update and the version of the WUA client .
Hope it helps ,
Kenny
Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/ - I checked my clients and most of them already had the 7.4 WUAgent. I tried to uninstall/reinstall WU and resetauthorization, removed softwaredistribution folder, nothing worked. The only way I've been able to fix these clients is to by removing the SCCM client then reinstalling. I've tried a repair and it does not work.
I'm assuming there is something stuck in a CCM WMI class that gets removed during this process. Anyone know where to look in WMI where the client stores info about SUP deployments? I'd like to try a surgical strike rather than carpet bombing these clients? - Hi again !
Sorry for being so quiet but i have been home ill for a while and then a 2-week trip but now i´m in place again:)
Thx all for your replies. I will try what you have tried and see if that will take care of the problem. Some of the things
you have tried i have tried already with no result unfortunately, see below.
I have also tried to uninstall/reinstall WU and resetauthorization, removed softwaredistribution folder, but nothing worked.
I have tried to repair the clients and it did not work. I have also installed that patch by hand, rebooted, and SCCM still thinks it's stuck at 50%.
I have checked my clients and most of them have the 7.4.7600.226 WUAgent
I will keep on trying and get back as soon as i have something new to report :)
/Stefan - I too am having trouble with this issue, with the same patch (this is the second time we have had this issue). I have tried numerious things all with no luck.... One client appears to be working after restoring the PC from a previous ghost image (thankfully we had this as this machine is a beast with 40+gb of software loaded), uninstalling SCCM, running all updates via windows updates, then reinstalling SCCM.... Currently we have about a dozen our ot 200 clients with this issue. I too saw that there was a previous patch that is not downloaded on our server, i wonder if this patch is "missing" and is stopping the clients from completing?
Bill - The only things I can add is make 100% sure you are not deploying either of the patches I mention above. I did find one deployment where it was hiding on some affected clients (Check the status is NO for deployed). However that still did not fix some machines. I found that I could still deploy software packages so I created a Clean SCCM package that included the ccmclean.exe file. I kicked off a script to stop BITS, WUAUSERV, and then CCMEXEC (It seemed like the uninstall had a better success rate doing this first). Then ran ccmclean.exe /q. I then sleep for 8 min and then fire ccmsetup.exe from a network share. (Don't try to do this from your CCM Cache as it's gone at this point.
This fixed every machine that still had the problem without manually touching each one. If you need the script I could post it.
You might want to try these links that I found helpful to confirm the problem:
http://social.technet.microsoft.com/Forums/en/configmgrsum/thread/23f5f406-aa1f-420a-83b7-de1c2f751935
http://www.myitforum.com/forums/m_197187/mpage_1/key_Inventory%252CHistory/tm.htm#197187
The 2nd link shows where to look in WMI for the running jobs (which is the same as what Client Center will show you). I did confirm with wmiexplorer.exe that no other jobs were pending so the next step was the uninstall/reinstall fix. - Hi Joey ,
I still do not believe in the fact you have to reinstall the client to solve this issue.It seems a drastic measure for something like this. For me the problem is related to the WSUS scan engine , not the SCCM client itself ( however the sccm lclient is leveraging on the WUA engine ) .
I did solve all my clients by running an update on the latest WUA engine.
However , if it solved your issue , I am pleased for you .
Kenny
Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
