Windows XP Pro - Belarc advisor score.

So here's the skinny: Old SATA HD died, decided to a buy a new one. While waiting, I decided to breakout an old IDE HD (20 GB) and format it to NTFS, of course, and put Windows XP Pro onto that. Fully updated it, installed all the needed security...ETC, but one problem--Belarc is having a fit and telling me I messed up on the .Net crap.

So, I booted up the removal tool, removed all traces, cleaned up with a few programs and decided to take it the full monty and work on improving my score from a 1.-whatever to something moderately higher.

I'm hoping that you fine folks and your lovely brains can help me, a cruddy hobbyist, figure out some issues and hopefully help me tighten my computer's holes up a bit more.

Specs:

Running programs:
1. Avast anti-virus
2. Peerblock (96 lists)
3. Zonealarm free firewall
4. Teatimer (Spybot S&E)
5: Threatfire
6: Winpatrol



Problems:
1. From .net 2.0 to 4.0, I keep being told I'm missing "important security updates" and have confirmed that they're not showing up in Windows Updates. When I download the updates manually, they either install without a hitch or I'm told that they're already installed, yet I don't see them in Add\Remove.

2. Belarc Advisor is one tough cookie to figure out, below are my current issues.
2a.

2b.

2c.

For now, I'll just post the above instead of going into greater detail of certain issues. Besides the above, I am open to any and all advice for securing and making my computer quite-well, what else--secure.

 

Edit:

Ran Belarc, again, claims these three are missing. I originally was told there was six, but after some poking around, I got it down to three. After poking around, manually installing and rebooting, it seems like they're not being seen on the computer. It's odd, really.

This isn't meant to be a bump.

 

Hi sarge. Welcome to MajorGeeks.

Can't help much with ".net", but I have to ask, how does this work?

and

There seems to be a bit of info missing somewhere, it's probably just me missing it though.

 

No, it's me and a typo, lol.
And the .net was fixed by removing all traces of .net 2.0