I only use the free version so don’t have that feature but I agree that it seems very redundant given the protection of Avast and all of the major browsers doing the same thing.

I also don’t care for the new icon but I’ll get used to it.

Sumatra PDF 2.2 http://blog.kowalczyk.info/software/sumatrapdf/download-free-pdf-viewer.html

Free Download Manager v. 3.9.2

Info: http://www.freedownloadmanager.org

Direct download link: http://files.freedownloadmanager.org/fdminst.exe

Microsoft “Fix it” available for Internet Explorer 6, 7, and 8

http://blogs.technet.com/b/srd/

Foobar2000 1.2

Download:
http://www.foobar2000.org/download

Changelog:
http://www.foobar2000.org/changelog

WinPatrol updated 26.1.2013

http://www.winpatrol.com/upgrade.html

NVidia Geforce updates 310.90

http://www.nvidia.com/Download/Find.aspx?lang=en-us

Firefox 18.0

http://www.filehippo.com/download_firefox

Surprisingly, considering Mozilla usually keeps version nos. more or less in sync with Firefox:

Thunderbird 17.0.2

Windows updates have been released, 10 important and 1 recommended for me.

16 on Win 7 , 7 on XP

Adobe Flash Critical Update 11.5.502.146 Released

http://get.adobe.com/flashplayer/

Flash Player Help

Deselect the McAfee scanner unless wanted!

Exercise caution! I installed the below six WU on XP32 Pro. After the required restart, one of them ate my wireless adapter. Seriously, the software was gone with no trace other than the Start menu link which went nowhere. Re-installing wasn’t a problem for me as I had the installation CD and use a driver backup program, but anyone without one of these could be without internet and not able to re-download.

Just updated my XP Pro SP3 and no issues, but I never ever download the Malicious Software Removal Tool, why would I need that with avast and my other protection.

That said I don’t know if it might have been the MSRT causing the wireless adapter issue.

Same updates here on XP Pro connected via wireless. No problems whatsoever and I did run the MRT like always.

@ DavidR & Dch48: I’m glad you didn’t have the same problem. When I ran Ccleaner last night, it found some .netframework issues. I suppose that is related somehow. NETGEAR WNA1100 was the wireless adapter that got zapped.

Well .net framework is the biggest pain in the backside for updates and there were several .net updates in the last batch from WU. Though that I don’t believe would be the cause of the failure of the wireless adaptor unless it uses .net.

There has been one pain in the backside ,net update that so far I have installed twice and on neither case did it say it failed, yet it popped up again (installed again) and now whilst posting this I noticed the WU tray icon, requesting this bloody .net framework 3.5 SP1 KB2736416 has raised its ugly head.

Having just installed it again and again (so now it is 4 times I have installed it and it gets through to ‘Installation complete’ no doubt it will be back again. I have had nothing but trouble with .net framework a right pain.

I got the notification this morning, and took the plunge.
8 items for me… 7 .nets and the malware cleaner. Took
them all. No problems (so far). My house is networked
with G systems. Computers (desktops,laptops), HDTVs
Xboxs, PS3 and PS2, tablets… you name it,we have it.
The only difference might be if you have N instead of G.

All 17 updates downloaded and installed correctly here. Computer restarted and wireless is working fine.

Hello DavidR,

I had the same problem in the past and one of my friends too (just a year before me). We were both on XP.
This is quite OT here, however I’d like to say that I solved the issue removing all the related .net framework stuff and then installing it all again - I wouldn’t recommend this though.

I did several research on the Intertubes at the time, but anything worked for me. What I can say is that I believe in my system the installation was actually completed and without glitches (no matter what WU said). The only real issue should have been the WU tray icon requesting the update endlessly.
My friend solved it (on my advice) excluding the bloody update and then including it again at some point over the following months when other newer .net framework updates came out. Hope this could help.

Sorry for the OT.

EDIT: some of many typos