KB976569 installs successfully... over and over and over again... and still shows up on windowsupdate.microsoft.com the next time
we carrying on thought thread because answer thread was: don't solve problem, hide update.
can tell me windowsupdate (or wsus, since appear using same logic) is using determine update needed? apparently, it using other patch file itself, because patch file reports installs successfully. (and have on 6 gigs worth of 12 megabyte log files prove it).
if can solve problem in terms of windowsupdate (and it's nothing personal papa bear, hiding update not solve problem), problem wsus solved.
what gives? did let new guy package update? (and old timers reading thread right , gigglin' behinds off?) =)
(some additional keywords here):
* update has been downloaded computer if select it, finish installing (recommended)
(this says when go windowsupdate , @ bugger update still there)
and here bit recent log file in
c:\windows\system32\config\systemprofile\local settings\temp\
msi (s) (60:b4) [14:18:00:355]: note: 1: 1728
msi (s) (60:b4) [14:18:00:355]: product: microsoft .net framework 2.0 service pack 2 -- configuration completed successfully.
msi (s) (60:b4) [14:18:00:355]: attempting delete file c:\windows\installer\38a03b.msp
msi (s) (60:b4) [14:18:00:371]: cleaning uninstalled install packages, if exist
msi (s) (60:b4) [14:18:00:371]: post-install cleanup: removing installer file 'c:\windows\installer\38a03b.msp'
msi (s) (60:b4) [14:18:00:371]: mainenginethread returning 0
msi (s) (60:b8) [14:18:00:371]: destroying remoteapi object.
msi (s) (60:74) [14:18:00:371]: custom action manager thread ending.
=== logging stopped: 4/15/2010 14:18:00 ===
msi (c) (7c:38) [14:18:00:387]: decrementing counter disable shutdown. if counter >= 0, shutdown denied. counter after decrement: -1
msi (c) (7c:38) [14:18:00:387]: mainenginethread returning 0
=== verbose logging stopped: 4/15/2010 14:18:00 ===
on xp machine, kb974417 shows in add/remove list being installed october 14th.excellent! installed october security updates in october! :-d
now trying re-install on , over. suggestions (for non-technical person)?
this because kb976569 (february 2010) changed file dates , versions of files updated the kb974417 update, , writers of metadata violated fundamental provision of package building, test later version in applicability rules , report update notapplicable when later version installed. update (kb976569) installed newer files, causing isinstalled test kb974417 report false (correctly so), isinstallable rule (to report true -- , incorrectly so, given newer versions of files installed).
a revision released yesterday resolves flaw, correct resolution of issue either remove approvals kb974417 (which has been current workaround), or ensure latest revision (rev 105) approved revision.
lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2010)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
blog: http://onsitechsolutions.spaces.live.com
Windows Server > WSUS
Comments
Post a Comment