It looks like your exefile association is broken.
See here how to fix this: http://filext.com/faq/broken_exe_association.php

Thanks. Unfortunately, my time is limited lately, so I have not found the time yet to maintain/update my blog.

Unclear what link you are talking about. If it's above link, then I'm usure why Norton flags it as there's nothing suspicious/strange there. That page doesn't even contain any scripts.

Browsing/surfing is always a risk as you noted, and legitimate sites can be compromised and infect your computer. However, "illegal sites" bring in 90% of the cases malware with it. So if you already know this, then avoid.

There's no need for a Registry cleaner at all. There is a need for an Antivirus, because not having an antivirus is somewhat suicidal in today's digital world. Here's a list of the ones I recommend: http://users.telenet.be/bluepatchy/miekiemoes/Lin... (I need to update my list asap). Only install one Antivirus, because multiple together will decrease the reliability of it seriously!
The reason for this is that if both products have their automatic (Real-Time) protection switched on, your system may lock up due to both software products attempting to access the same file at the same time.
Also because more than one Antivirus installed are not compatible with eachother, it can cause system performance problems and a serious system slowdown.

What do you mean with more variants? Above one I explained is the one that patches the legit ws2_32.dll file. There are still so many other variants that causes search engine redirects, which I also explained in older posts in this blog. Most scanners detect and delete these though, so that's why I only post variants here which are a bit more advanced to find in logs. In case you're dealing with a searchengine Hijacker and you can't find the culprit (if no scanners detect it), then I suggest you post your issue on one of the forums mentioned on the right here :)

Glad I could help :)

Thank you for the kind words :)

The reason why mbam has problems with fixing this one is because of a permission issue set on these keys by the malware you were dealing with. Mbam 1.42 (which will be released soon) should be able to fix these properly.

Update: http://malwarebytes.besttechie.net/2009/11/03/iob...