Black Tuesday updates

[Avastfan1]

Dear Forum,

11 Window$ Updates were installed and the reboot occurred without any problems.

How did YOU fare with the dreaded Black Tuesday?

Best wishes,

Avastfan1

[YoKenny]

Dear Forum,

11 Window$ Updates were installed and the reboot occurred without any problems.

How did YOU fare with the dreaded Black Tuesday?

Best wishes,

Avastfan1

2 for Windows 7 and 12 for XP Pro.

Windows Malicious Software Removal Tool x64 - December 2009 (KB890830)
Cumulative Security Update for Internet Explorer 8 for Windows 7 for x64-based Systems (KB976325)

[Pondus]

Got 2 for office and 8 for XP on my work laptop, restart OK

Inga problem her grabben......

[DavidR]

I got 7 for XP Pro SP2 Yesterday (manual visit to WU site), I always decline the Malicious software removal tool (to darn big for dial-up and I have avast )

Strange thing WU Auto updates pipes up and offers one more, yet when I visit WU site and no updates, just one of the further inconsistencies of WU for me.

[polonus]

Hi DavidR,

But Microsoft just before Christmas protected against a USB-stick-worm: http://blogs.technet.com/mmpc/archive/2009/12/08/msrt-slices-the-hamweq-for-christmas.aspx

The latest Malicious Software Removal Tool (MSRT) update is enabling the removal tool to detect also the Hamweq worm. This malicious software spreads through shared network folders, USB-sticks also known as pendrives and other preripherals and enables attackers to access the OS via an IRC-backdoor. Because of an increase in Hamweq activity the software vendor decided to put it onto a "blacklist" and add to the free removal tool. According to MS firm scanner Forefront it is the second most active worm to-day:
http://www.ca.com/us/securityadvisor/virusinfo/virus.aspx?id=77478
http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?Name=Win32/Hamweq

The advice for now is to disable autorun: http://support.microsoft.com/kb/971029

 You can reduce the effectiveness of these types of worms by ensuring that autorun content is not displayed in the autoplay dialog when removable or network drives are attached. For Windows 7, this is the default behavior (see: http://blogs.technet.com/srd/archive/2009/04/28/autorun-changes-in-windows-7.aspx). If you have an earlier version of Windows that is not already configured in this way, you can follow the instructions at:  http://support.microsoft.com/kb/971029. Alternatively, for Windows Vista or later, you can disable autoplay completely, or for particular types of media, via the “Hardware and Sound” section of the Control Panel.  

For me Hamweq is not coming to Christmas dinner, folks,

polonus

[DavidR]

The Malicious Software Removal Tool still doesn't bring any benefits to my system as I'm more than adequately covered and autorun is already disabled, along with another slew of measures.

That may not be the case for everyone, but it is for me.

[polonus]

Hi DavidR,

Ah I see, that is why you did not post it. I hope some may benefit, else MSRT would be an idle operation alltogether,

pol

[DavidR]

Well I have posted the various measures that I take in many posts where it is related as opposed to being somewhat off-topic for this topic.

[PTRPRO]

No problem on Vista. Hate the waste of time restart. I manually download at my leisure and sometimes reject useless updates.

[cinchez]

Same here Corday^^

Others r just a waste of time...successfully installed 7 important windows update with of course a reboot^^

[Win Vista]

-AnimeLover^^

[pinnacle]

Got them late that day after  a little trouble i had with windows update but everything is humming along fine now.

[MikeBCda]

8 for XP -- got a new problem I'd never seen before (access denied because of credentials submitted), but got a quick email response from MS Support suggesting I check, among other things, my Local Area Connections DNS settings.  I don't remember ever touching those, just the ones for my ISP connection, but once I set the LAC ones to MS's recommendations, Update went just fine.

Wandering somewhat OT, it'll be interesting to see if the change makes any difference to the extremely slow lookups for HTTPS addys I've experienced with Firefox 3.5.x.