So now this episode is over until the next time. I find it exceedingly uncomfortable that the WU system is used like a weapon to beat me into submission. Even though it was obvious to me that I did not need KB3024777, WU was determined to shove it down my throat. It's like the worst kind of socialist policy we used to see here in England - 'if not everyone can have it, then no-one shall have it'. That's not a pretty badge for MSFT to be wearing.
jFiredog,
I submit that as knowledgeable as you may be in your MVP field, the root cause analysis of this error indicated forced removal was necessary. I agree that it was forced. I'm appallled at the lack of communication and explanation from Microsoft Security Response Center / Microsoft Update / Trucstworthy Computing groups.
I have not experienced English socialism, but I do not see this as a "not everyone can have it, then no-one shall have it." situation. If the VirtualBox bug tracking threadis to be believed, and I was able to duplicate their results, then the lack of a security catalog and the resulting inability to validate software signatures, with attendant impacts on whitelisting and system integrity features was simply untenable. That would warrant the forced removal of kb3004394.
For me, more info from MS would releive the bitter taste that the last 5 cycles of updates have left. Staff replacements in MSRC, the loss of the Bulletins webcast and public Advance Notification Service demonstrate a trend towards less openness, and further erosion of public confidence in MS patches.
Respectfully,
Tom S.