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

Agreed, six of one, 1/2 dozen of another.,  I just don't want to "forget" to untick the box., and fixing this flaw that's only happening on some users boxes- I don't think is very high on M$ priority list *COUGH* Win 10 rollout *COUGH* "Spartan" Browser (Re-branded Ex-PLODE-r if u ask me)... tin foil hatters like me see all signs pointing to "forcing" (thru neglect, FUBAR updates, no service pack etc...) users into the free upgrade to 10, M$ doesn't want another XP and want to move away from the disastrous 8. 

However to paraphrase Charlton Heston:

"They can take my Win 7 when they pry it from my cold, dead harddrive!"

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.

As much as I appreciate the time you've put into this issue (hardly any bu***r else is), it's no more a solution than unticking the Windows Update box in cleanup is - it's a workaround that removes functionality (albeit currently BROKEN functionality!)

OT

re KB3035583: http://www.infoworld.com/article/2903005/operating-systems/what-we-don-t-know-about-mystery-windows-patch-kb-3035583.html#tk.rss_all

More O/T, but then again not:

You cant make this stuff up, part 6,597:

Update enables additional capabilities for Windows - Broken  (Sevenforums)

EDIT: Great find by user Tech77 @ Sevenforums: MDL Hotfix Repository (TY **Ricktendo64**)

G.W.X. (gwx.exe) stands forGetWindows X (10)

well if this fuzzy logic KB3035583 causes some extra errors in win7 log... no problem... removed... all errors along with GWX-Ins log folder gone!

P.S. when WU is commonly set to Manual I hope we don't need to worry of some silent free-of-charge upgrade from the nice win7 to a cloudy win10.

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.

WOW, the enormous job is done!

The idea of a removal of KB2852386 was tested on a real hardware and works just fine although I guess it's a some kind of compromise solution but not the complete one, when at least in my case I don't have any problem with both also mentioned KB3035131 as installed on Mar. 11, 2015  & KB3031432 as installed on Feb. 11, 2015 but solely that damn KB3023607 that is nothing more than some messy TSL security patch of Feb2015 that was cooked bad by MS from the very beginning!!! http://www.infoworld.com/article/2884942/operating-systems/microsoft-posts-fixit-for-kb-3023607-the-poodle-patch-that-clobbers-cicso-s-anyconnect-vpn.html, which is always being removed by deepclean at the moment right after the install of the 2nd small parts of the re-offered KB3021952 of Feb2015 & KB3032359 of Mar2015, those two are seeming to be just equal to installation of KB3023607 since this particular KB3023607 immediately appears in list of Installed Updates instead of the new entries of KB3021952 & KB3032359 as it should be logically.

I mean that it seems a culprit of all this March 2015 fuss is not a broken logic of KB2852386 as installed on Oct. 26, 2014 in my case and was working just nice before March 2015 but KB3023607 itself or some small part of it like a wrong/messy in-system flag or marker, which prompts deepclean to remove it.

Anyhow I don't see any big difference if the 2nd small parts of the re-offered KB3021952 & KB3032359 are put to hidden list or it's KB2852386 as hidden. Moreover from my point it seems preferable to keep on Win7 deepclean function as KB2852386 installed rather than KB3023607. Don't you think so? 

Thanx

Rgds,

P.S. I believe this KB3023607 & deepclean mess-up does affect the most OR a lot of Win7 machines but it yet remains not widely known just since most of users don't burden themselves with deepclean. So I hope that some of MVPs, Patch Queens & Kings will finally pay a bit of their f..king (guess what? right, good guess!) attention to this odd issue!