Comments on: 'Critical' megapatch sews up 10 holes in IE

Microsoft bulletins highlight browser flaw being used in cyberattacks, plus fix bugs in Windows and other software.

[zhaol]

How long between MS Bulletin notification and the real vul report

Whenever Microsoft publishs a security bulletin notification and patch, we know some bugs and defects are discovered and we have to do something to patch our windows. But I want to know "how long between MS notification and the real vul report"? ie. typically, what's the internal time slot between they know the vulnerability's existing and they roll out a patch or workaround, and finally notify our end users?

http://hi2005.wordpress.com

[zhaol]

How long between MS Bulletin notification and the real vul report

Whenever Microsoft publishs a security bulletin notification and patch, we know some bugs and defects are discovered and we have to do something to patch our windows. But I want to know "how long between MS notification and the real vul report"? ie. typically, what's the internal time slot between they know the vulnerability's existing and they roll out a patch or workaround, and finally notify our end users?

http://hi2005.wordpress.com

[thuck]

MS06-015 / KB908531 is causing my Win XP Pro SP2 OS to COMPLETELY FREEZE

MS06-015 / KB908531 is causing my Win XP Pro SP2 OS to COMPLETELY FREEZE intermittently. I am able to "SEE" this fact because I have GoBack 4 from Norton/Symantec installed on my system. I am forced to reboot my system when it freezes. I can then, after the reboot, start the Advanced Restore feature of GoBack 4 to see what the last file activity was on my OS just prior to the system's freezing (i.e., the file activity right before my latest system restart due to the reboot). When I check this file activity, right before the freeze itself occurred, I see VERCLSID.EXE was executing immediately prior to the system freeze! Prior to this Microsoft update, my system was completely stable; I could run it for days with no issues. Now, however, it freezes randomly, and it appears that VERCLSID.EXE is the culprit. Moreover, the freezes can occur right after my OS' sstars screensaveer is activated, when I try to use ACT!, or any number of other "random" activities I might be doing. Therefore, Microsoft's exceedintly limited list of "known" conflicting third-party applications is B.S.; there are myriads of conflicts, it appears to me. So, besides fixing this Microsoft pushed OS-breaking piece of sh't on the masses who use Windows XP, I suggest that Microsoft REPLACE its entire QA team for these OS updates. This is beyond unacceptable! Microsoft is making its OS crap rather than improving it for us all. Hmmm! I wonder... Could it be that Microsoft would like to break everyone's Windows XP OS's just in time to tell us about how great it would be for us to all migrate to Windows Vista? Now that's a thought!!!

[thuck]

MS06-015 / KB908531 is causing my Win XP Pro SP2 OS to COMPLETELY FREEZE

MS06-015 / KB908531 is causing my Win XP Pro SP2 OS to COMPLETELY FREEZE intermittently. I am able to "SEE" this fact because I have GoBack 4 from Norton/Symantec installed on my system. I am forced to reboot my system when it freezes. I can then, after the reboot, start the Advanced Restore feature of GoBack 4 to see what the last file activity was on my OS just prior to the system's freezing (i.e., the file activity right before my latest system restart due to the reboot). When I check this file activity, right before the freeze itself occurred, I see VERCLSID.EXE was executing immediately prior to the system freeze! Prior to this Microsoft update, my system was completely stable; I could run it for days with no issues. Now, however, it freezes randomly, and it appears that VERCLSID.EXE is the culprit. Moreover, the freezes can occur right after my OS' sstars screensaveer is activated, when I try to use ACT!, or any number of other "random" activities I might be doing. Therefore, Microsoft's exceedintly limited list of "known" conflicting third-party applications is B.S.; there are myriads of conflicts, it appears to me. So, besides fixing this Microsoft pushed OS-breaking piece of sh't on the masses who use Windows XP, I suggest that Microsoft REPLACE its entire QA team for these OS updates. This is beyond unacceptable! Microsoft is making its OS crap rather than improving it for us all. Hmmm! I wonder... Could it be that Microsoft would like to break everyone's Windows XP OS's just in time to tell us about how great it would be for us to all migrate to Windows Vista? Now that's a thought!!!