Unsolved

This post is more than 5 years old

3 Apprentice

 • 

20.5K Posts

12252

July 12th, 2007 21:00

Article: MS update sends PCs 'haywire'

MS update sends PCs 'haywire'
.NET patch trips up systems

By John Leyden
Published Thursday 12th July 2007 16:15 GMT

"Early reports are suggesting problems after users apply one of the six patches issued by Microsoft on Tuesday.

Applying the MS07-040 patch for the .NET framework, which as luck would have it is probably Redmond's most important security fix this month, can lead to systems going "haywire", the SANS Institute's Internet Storm Centre reports."


More:
http://www.theregister.co.uk/2007/07/12/ms_patch_problems/

3 Apprentice

 • 

15.6K Posts

July 12th, 2007 21:00

i wish we had more to go on than just "haywire" or "gaga".
 
having looked at the XP forum here, about the only complaint I've noticed there is from people who are saying they couldn't get it to install... which, if things truly go "haywire", may mean they've actually "lucked out" by it's failing :smileywink:
 
i've installed the update on at least 2 xp pro sp2 systems, and haven't noticed anything unusual... so far


Message Edited by ky331 on 07-12-2007 06:28 PM

3.3K Posts

July 12th, 2007 22:00

I wonder if it's the .NET Framework version 1.1? I have Version 2 so I ignore version 1.1 and never downloaded it...it's optional software anyway.

I DID install the critical update for version 2 however since I do have it installed. Microsoft needs to know that if you have version 2, there is no need for version 1.1 but I nonetheless continued to receive the update for version 1.1 as an optional software download until I clicked the "Don't show this update again" box.

3 Apprentice

 • 

20.5K Posts

July 12th, 2007 22:00

Symptoms seem to be that the install fails. Of course, if a user is on Autoupdates, he is constantly notified that he needs to install an update. Solution seems to be an uninstall of all MS NET Framework versions and updates. Then a reinstall of all. After that, the patch seems to update properly. Mine updated on the first try, so I cannot speak from personal experience. I'm just repeating what I've been told.

I have one more system to update on Saturday, and I'm keeping my fingers crossed. Thinking 5

3.3K Posts

July 12th, 2007 22:00

Hmmmm...the article doesn't say if this relates to the
update for Windows Vista or Windows XP

...I have been running XP with no problems.

3 Apprentice

 • 

15.6K Posts

July 12th, 2007 23:00

I think it would be helpful if we could distinguish between a system going "haywire"   as a consequence of the patch  --- the implication (at least to me) here being that the patch was "successfully" installed, but then subsequently had pejorative effects on performance ;
vs. the patch "simply" failing to install in the first place  --- not to say that this is "right", but, aside from the "nagging" to re-install, I wouldn't consider this as going "haywire".
 
My systems have .NET 1.1.4322, 2.0.50727 AND 3.0 installed... yet I got both the 1.1 and 2.0 updates


Message Edited by ky331 on 07-13-2007 09:05 AM

2 Intern

 • 

5.8K Posts

July 13th, 2007 04:00

I had no problems, but Windowsupdate newsgroup is full of posts of .Net failing to install.
 
As mentioned, uninstalling/re-installing all .Net Framework versions/patches seems to work for many, but it's not as simple a process as it sounds: see this post for detailed instructions.
 
The best advice I've seen is to just hide the update (at MSU or WU) and wait for MS to fix it.

3 Apprentice

 • 

20.5K Posts

July 13th, 2007 10:00

Quote:
"...hide the update (at MSU or WU) and wait for MS to fix it."

That sounds like a good move, Joe. :)

0 events found

No Events found!

Top