KB3023607 repeatedly removed by deepclean after KB3032359/KB3021952 (5.2mb ea) repeatedly offered/installed...

Anonymous
2015-03-15T22:40:10+00:00

KB3021952 (Feb "Cumulative" Update for IE) invloves a "bundled" update, it includes KB3023607. KB3032359 (March "Cumulative" Update for IE) is "bundled" it includes KB3040335 & KB3023607 (Again???) KB3032359 (allegedly) supersedes KB3021952 but both are needed along with KB3023607 to have a fully patched system. The problem occurs when Windows Update Cleanup (deepclean) is run after all patches are installed, it removes KB3023607, the "bundled" update as superseded :

2015-03-12 09:31:26, Info CBS Adding: Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0

2015-03-12 09:31:31, Info CBS DC: Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0: unique components: 58 Size: 20.54 MB (21,538,670 bytes) 2015-03-12 09:31:31, Info CBS Total size of superseded packages: 20.54 MB (21,538,670 bytes)

The KB's 3021952 & 3032359 (5.2mb) that are continually removed/re-offered/re-installed/re-removed... lather, rinse, repeat... are actually the child package component KB3023607 which gets removed by deepclean.

Thread information Updated see my reply Pg 6 March 30 2:48 AM

Windows for home | Other | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2015-03-30T23:03:36+00:00

At this point, it's evident that MS needs to investigate why Windows Update cleanup detection logic is ...broken (for lack of a better word) on some user's computer's only, there has to be a "missing link" ... I'm out of ideas and don't see too many here or elsewhere on the Innernetz

.

I have 2 options to correct the problem of KB3031432 not appearing in Installed Updates but yet the MSU installer returns the message KB3031432 is already installed... and the PendingDeletes that won't.

  1. Repair Install
  2. Restore from prior backup image (2/12/15, after Feb Black Patch Tuesday, tested on spare HDD.

Thank to everyone who replied, and a special thanks to "J"... seems you're one of the few I've seen around here that "gets" it.

Regards & Hasta la Bye-Bye

,

"Pink"

Edit to add: I have successfully restored my system to a previous backup image (2/12/15) prior to the "March Patch Madness" described in my OP, uninstalled the troublesome KB2852386 that enables Update Cleanup and re-applied the March '15 patches, all now appear in Installed Updates, including KB's 3023607, 3035131 & 3031432. Kindly mark this as "Answer" as I consider this matter resolved... if only temporarily.

Thank you.

Was this answer helpful?

0 comments

127 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-03-25T23:31:27+00:00

    In the meantime, if KB3021952 and/or KB3032359 are being repeatedly offered to you, search for installed updates following the instructions located here.

    Does it matter if KB3021952 and/or KB3032359 are listed in Update History but not in Installed Updates?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-25T21:58:09+00:00

    Look for KB3032395, KB3021952, KB3046049. If they are present in the Update history list and the status for each shows Succeeded, you have received subsequent packages that supersede the ones being re-offered.

    You can hide the re-offered KBs.

    Thanks for the response, but this has been established. All of the above are confirmed installed in Installed Updates. I will hold off on running Windows Update Cleanup until a fix/resolution is found. The issue is Mr.Bear's mysterious "more important issues" & his (erroneous, it wold appear) assertion that "there's something very wrong with your Windows install" Re: KB3035131 (Kernel Update) not showing in Installed Updates/ also being falsely detected as superseded by WU Cleanup. The workaround I posted above (March 20, 6:01 PM) works for me, also contingent on NOT running WU Cleanup.

    As a matter of fact I'll go one further and un-install KB2852386 altogether and be rid of this albatross entirely.

    Kindly mark this as "Answer" if you would be so kind for as they say:

    I have nothing further to add to this discussion.

    BTW, the bolded text in your quoted reply contains a typo, s/b KB3032359 not 95.

    Regards

    Pink

    EDIT to add "installed in Installed Updates."

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-25T20:11:01+00:00

    Hi,

    KB3021952 and KB3032359 should not re-offered if they are currently installed. An investigation is in-progress to find the cause and a resolution.

    In the meantime, if KB3021952 and/or KB3032359 are being repeatedly offered to you, search for installed updates following the instructions located here.

    Look for KB3032359, KB3021952, KB3046049. If they are present in the Update history list and the status for each shows Succeeded, you have received subsequent packages that supersede the ones being re-offered.

    You can hide the re-offered KBs.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-25T00:30:57+00:00

    I know, I had 3 recurring updates... KB3021952, KB3032359 & KB3035131. Believe it or not I suspect KB3033929 is "Patient Zero" in Micro$lop's latest batch of botched updates. Reason? Call it a hunch:

    Patch Tuesday: October's Rescinded 2949927 Gets Reissued as 3033929

    Patch Tuesday: Is KB3033929 Causing Problems?

    MS Update 3033929 Causing Reboot Loop

    My latest Microsoft update problem

    KB3033929 is a re-issue of the previously Issued-FUBAR-ed- Rescinded KB2949927. KB3033929 is also quite ... busy superseding several previous updates including (but not limited to):

    KB3009736, KB3004394, KB3001554, KB2847077.

    But wait! There's more!

    *[1]*The 3033929 update has affected binaries in common with the 3035131 update being released simultaneously viaMS15-025. Customers who download and install updates manually and who are planning to install both updates should install the 3035131 update before installing the 3033929 update.See the Advisory FAQ for more information.

    But that's not all...

    How is this update (3033929) related to the 3035131 update discussed in MS15-025?This update (3033929) shares affected binaries with the 3035131 update being released simultaneously viaMS15-025.This overlap necessitates that one update supersede the other and, in this case, advisory update 3033929 supersedes update 3035131.****Customers with automatic updating enabledshouldexperience no unusual installation behavior; [key word beingshould***] both updates*should install automatically and bothshould** ***appear in the list of installed updates. [mine didn't]*However, for customers who download and install updates manually, the order in which the updates are installed will determine the observed behavior as follows:

    Scenario 1 (preferred): Customer first installs update 3035131 and then installs advisory update 3033929.

    Result: Both updates should install normally and both updates should appear in the list of installed updates.

    Scenario 2: Customer first installs advisory update 3033929 and then attempts to install update 3035131.

    Result: The installer notifies the user that the 3035131 update is already installed on the system; and the 3035131 update is NOT added to the list of installed updates.

    Wait, whut? this Super-Duper Update not only supersedes... a bunch of... previous updates, it supersedes it's "twin" KB3035131 born the same day? No wonder Windows Update Cleanup is "confused"

    Horrible, simply horrible.

    Edit: Add bold to text

    Was this answer helpful?

    0 comments