[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Hang loose until someone in Redmond wakes up and fixes Microsoft update. - THE OFFICIAL BLOG OF THE SBS DIVA
Mon, May 21 2012 23:43 bradley

Hang loose until someone in Redmond wakes up and fixes Microsoft update.

MS12-016: Description of the security update for the .NET Framework 2.0 Service Pack 2 on Windows XP and Windows Server 2003: February 14, 2012:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2633880
MS11-044: Description of the security update for the .NET Framework 3.5 Service Pack 1 and .NET Framework 2.0 Service Pack 2 on Windows XP Service Pack 3 and on Windows Server 2003 Service Pack 2: June 14, 2011:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2518864
MS11-078: Description of the security update for the .NET Framework 2.0 SP2 for Windows XP and Windows Server 2003: October 11, 2011:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2572073

Seeing these being offered up tonight on a Server 2003 and on XP on unmanaged,  or Automatic updates enabled machines.

Hang loose until someone in Redmond wakes up and fixes Microsoft update.

It is reported that it will be fixed sometime after 10 a.m pacific.  It appears that MS12-035 will be rereleased and this is what is causing our momentary blip in detection.

Edit:  Now fixed, and the Microsoft securty bulletin alert indicates that some of these updates got a detection change.

********************************************************************
Title: Microsoft Security Bulletin Minor Revisions
Issued: May 22, 2012
********************************************************************

Summary
=======
The following bulletins have undergone a minor revision increment.
Please see the appropriate bulletin for more details.


   * MS11-100 - Critical
   * MS12-034 - Critical
   * MS12-035 - Critical
   * MS12-MAY


Bulletin Information:
=====================

* MS11-100 - Critical

   -http://technet.microsoft.com/security/bulletin/MS11-100
   - Reason for Revision: V1.5 (May 22, 2012): Added entry to the
     update FAQ to announce a detection change for KB2656352 for
     Microsoft .NET Framework 2.0 Service Pack 2 to correct an
     installation issue. This is a detection change only. There were
     no changes to the security update files. Customers who have
     already successfully updated their systems do not need to take
     any action.
   - Originally posted: December 29, 2011
   - Updated: May 22, 2012
   - Bulletin Severity Rating: Critical
   - Version: 1.5

* MS12-034 - Critical

   -http://technet.microsoft.com/security/bulletin/MS12-034
   - Reason for Revision: V1.2 (May 22, 2012): Added an entry to
     the Frequently Asked Questions (FAQ) Related to This Security
     Update section to explain this revision.
   - Originally posted: May 8, 2012
   - Updated: May 22, 2012
   - Bulletin Severity Rating: Critical
   - Version: 1.2

* MS12-035 - Critical

   -http://technet.microsoft.com/security/bulletin/MS12-035
   - Reason for Revision: V2.1 (May 22, 2012): Added entry to the
     update FAQ to announce a detection change for KB2604092 for
     Microsoft .NET Framework 2.0 Service Pack 2 and KB2604110 for
     Microsoft .NET Framework 3.0 Service Pack 2 to correct an
     installation issue. This is a detection change only. There were
     no changes to the security update files. Customers who have
     already successfully updated their systems do not need to take
     any action.
   - Originally posted: May 8, 2012
   - Updated: May 22, 2012
   - Bulletin Severity Rating: Critical
   - Version: 2.1
Filed under:

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Tuesday, May 22, 2012 4:37 AM by scendu

I know now that you should ignore those updates, since there's obviously a problem with Windows Update, however are there any known problems if I installed those updates already? Do I need to uninstall/reinstall any .NET Framework?

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Tuesday, May 22, 2012 7:41 PM by brad stewart

It is now 5:41 pacific and this update is STILL wanting it over and over, about every 5 minutes after its dl

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Tuesday, May 22, 2012 7:48 PM by bradley

5:41 pacific here.  I clicked on the little yellow icon to install them on my Server 2003 at home (older home server), it threw up a failed screen I clicked okay, the yellow button went away.

Have you clicked on the yellow button and tried this?

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Tuesday, May 22, 2012 9:20 PM by ted dyer

No change here! Still have the little yellow icon,etc.

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Wednesday, May 23, 2012 3:57 AM by Frank

Today, 23.MAY.2012 8:00 EE all 3 critical updates dissapear, and they are not installed,

It happens at all 3 PC I service, by itself. Curious.

The notification icon was displayed again, when I click It, pop up window to install updates,

then,  in a second, the window close itself and the icon dissapear.

Really fast solution.

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Wednesday, May 23, 2012 7:04 AM by Dmerces

I believe that resetting your updates can fixed the problem. See below what has worked for me:

Click Start, Run

Type the following:

net.exe stop wuauserv

click OK

Type:

regsvr32.exe wuapi.dll

click OK

Type:

regsvr32.exe wups.dll

click OK

Type:

regsvr32.exe wuaueng.dll

click OK

Type:

regsvr32.exe wucltui.dll

click OK

Type:

regsvr32.exe MSXML3.dll

click OK

Type:

net.exe start wuauserv

click OK

Restarted computer

Note:

• The update balloon stayed in the systry for about five minutes and suddenly disappeared and remained in that way.

• I ran windows update and the balloon remained dead, up to now

Try this procedure and post the results, please.

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Thursday, May 24, 2012 3:14 AM by Terence

These updates won't have been installed even if they were download because Windows File Protection prevents newer files from being overwritten by older versions.

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Thursday, May 24, 2012 4:01 PM by Antone

Same thing happened (apparently fixed it) as did to Frank on 05-23.  It seems to be fixed.  I completed 4 separate installs of the 3 updates on 05-22, as seen in my Update History.  When I turned on my computer early on 05-23 the yellow icon was present.  However, when I clicked install and immediately cancelled the install the yellow icon disappeared.  It hasn't occured since.  I notice in Update History that KB2633880 (one of the three) attempted to install on 02-15-12.  Also, that install and the 12 done on 5-22 do not show in Add/change in Control Panel.

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Sunday, June 10, 2012 6:47 AM by Lester

The Flame virus maybe responsibble for false updates.

using false microsoft certificate

Hash

The WSUS Update that microsoft release for the defense in depth?

# re: Hang loose until someone in Redmond wakes up and fixes Microsoft update.

Sunday, June 10, 2012 10:30 AM by bradley

The Flame virus was NOT the source of this bad detection.

They pulled off a .net which let three older .nets want to install.