Old net update ms11-100 kb2656352 installing again W2003 R2 SP2

into work morning ms11-100 kb2656352 installing again through wsus , failing, causing looping of install.

not attempting install, failing everywhere. worse still, continually looping try install itself.

why old update being re-applied ?

investigating update log of 1 server. (w2003 r2 sp2)

8 updates required:-

** start **  agent: installing updates [callerid = automaticupdates]
*********
  * updates install = 8
  *   title = update windows server 2003 (kb2808679)
  *   updateid = {28c1b904-63d6-4929-9f12-2016bbaadc96}.201
  *     bundles 1 updates:
  *       {4eff3bb6-a5d9-4abe-870e-056d8851c55b}.201
  *   title = cumulative security update activex killbits windows server 2003 (kb2820197)
  *   updateid = {25f15c26-9a8b-4231-ba9c-1d41d3caf7ff}.202
  *     bundles 1 updates:
  *       {d18e65e7-df4a-4974-beb0-d956aa3fd37d}.202
  *   title = cumulative security update internet explorer 8 windows server 2003 (kb2838727)
  *   updateid = {b8d6f931-c01b-46b2-84a4-81f2a6fe3623}.201
  *     bundles 1 updates:
  *       {b9136431-b93a-413e-8a3e-9da4bcc422d4}.201
  *   title = security update windows server 2003 (kb2829361)
  *   updateid = {fecb193a-00bb-4425-894b-30389acbfdff}.204
  *     bundles 1 updates:
  *       {19fccb86-224e-4129-9316-6bb394bfbb7c}.204
  *   title = update microsoft .net framework 2.0 sp2 on windows server 2003 , windows xp x86 (kb2836941)
  *   updateid = {5572ec40-c894-4362-9112-1b794f2d9006}.201
  *     bundles 2 updates:
  *       {c68495a7-0a26-48fc-8bb2-fedbd85473fe}.201
  *       {bc3477ba-d20a-4cb0-8d93-cc71149f1b29}.201
  *   title = security update windows server 2003 (kb2839229)
  *   updateid = {8e214d56-2979-4904-b36f-d4e5926c144b}.203
  *     bundles 1 updates:
  *       {e6b8342c-63f9-4a0f-94d5-d2fea021f4bc}.203
  *   title = update microsoft .net framework 3.5 sp1 on windows xp, server 2003, vista , server 2008 x86 (kb2836940)
  *   updateid = {c9b06977-9f40-4451-9fca-c5c85bb1d644}.200
  *     bundles 2 updates:
  *       {5edb567d-419e-4dbf-9dc9-6f35350aaf42}.200
  *       {6ee46123-d8ed-4dac-8741-1f2599daf250}.200
  *   title = security update microsoft .net framework 2.0 sp2 on windows server 2003 , windows xp x86 (kb2804577)
  *   updateid = {839e8f9f-188f-48b6-b43a-a4c3cb58c679}.201
  *     bundles 2 updates:
  *       {b15aba78-84a0-4ae8-856a-5f8aa2317eb7}.201
  *       {69d500c3-f64d-47d9-ae79-2f8a349251e0}.201
warning: loadlibrary failed srclient.dll hr:8007007e

but when installing these found:-

preparing update install, updateid = {c68495a7-0a26-48fc-8bb2-fedbd85473fe}.201.
:::::::::::::
:: start ::  handler: command line install
:::::::::
  : updates install = 1
  : command line install completed. return code = 0x00000000, result = succeeded, reboot required = false
:::::::::
::  end  ::  handler: command line install
:::::::::::::
preparing update install, updateid = {bc3477ba-d20a-4cb0-8d93-cc71149f1b29}.201.
:::::::::::::
:: start ::  handler: command line install
:::::::::
  : updates install = 1
report event: {64915771-8da6-4bb3-8bc6-89a917814c93}
warning: cached cookie has expired or new pid available
initializing simple targeting cookie, clientid = dce5a5f2-4f97-430a-91ad-126192c9573c, target group = , dns name = rjhpman
  server url = removed
uploading 4 events using cached cookie, reporting url = removed
reporter uploaded 4 events.
  : command line install completed. return code = 0x00000000, result = succeeded, reboot required = false
:::::::::

after these installs there requirement 5 installs, 4 of in above 8, though installed there additional requirement :

  *   title = security update microsoft .net framework 2.0 sp2 on windows server 2003 , windows xp x86 (kb2656352)
  *   updateid = {8914d187-d0c7-4c7e-9824-cfcff4c8377d}.104
  *     bundles 2 updates:
  *       {150273bc-82b4-43d6-ae3d-c289d94cbc21}.104
  *       {f1b1b1e1-2b22-4445-8a9c-5924bf945d32}.104

the installation of fails - possibly installed when released in 2012 !

any idea going on ?

what have advised have done on immediate problem.

excellent.

it not when new server has built, have replace like.

for new system deployments, recommend special ou and/or target group, these legacy updates can remain approved, impact *new* systems. once new system patched gets moved "production" ou/target group, , subsequently impacted current updates.

under these conditions actual problem being circumvented, not fixed. why, half way through update sequence, installed update become needed

typically result of 1 of 2 things.. either legacy update is in fact superseded, metadata not coded reflect fact, or detection logic in 1 or other updates flat-out defective.

• if detection logic in new update defective, it's revision update come down pipe shortly , fix problem.
• if detection logic in legacy update defective, there's nothing done except removing approval.
• if legacy update is, in fact, superseded, coded in metadata of new update, , revision may come down pipe, or may not.

many updates contain supersession data period of time backwards (definition updates, cumulative ie updates, , malicious software removal tool notable having behavior). happens in instance new updates gets installed, , subsequent wuagent (re)evaluates legacy update , says "hey. update not installed , should be!" (it's "should be" that's defective part.) legacy update gets re-installed, making new update notinstalled again, , behavior continue ad infinitium until cycle broken ... removing approval legacy update.

it matters not how legacy update installed, it's presence of current update via au/wu/mu/wsus that's creating problem.

---

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
solarwinds head geek
microsoft mvp - software packaging, deployment & servicing (2005-2013)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
http://www.solarwinds.com/gotmicrosoft
the views expressed on post mine , not reflect views of solarwinds.

Windows Server  >  WSUS