Yes HKCU:Run ctfmon.exe C:\WINDOWS\system32\ctfmon.exe
No HKCU:Run YahooMessenger "C:\PROGRA~1\Yahoo!\MESSEN~1\YahooMessenger.exe" -quiet
No HKCU:Run Skype "C:\Program Files\Skype\Phone\Skype.exe" /nosplash /minimized
No HKCU:Run YAHOOM~1 "C:\PROGRA~1\Yahoo!\MESSEN~1\YAHOOM~1.EXE" -quiet
Yes HKLM:Run avast5 "C:\Program Files\Alwil Software\Avast5\avastUI.exe" /nogui
No HKLM:Run AdobeARM "C:\Program Files\Common Files\Adobe\ARM\1.0\AdobeARM.exe"
No HKLM:Run Reader_sl "C:\Program Files\Adobe\Reader 8.0\Reader\Reader_sl.exe"
No HKLM:Run iTunesHelper "C:\Program Files\iTunes\iTunesHelper.exe"
No HKLM:Run QTTask "C:\Program Files\QuickTime\QTTask.exe" -atboottime
No HKLM:Run jusched "C:\Program Files\Common Files\Java\Java Update\jusched.exe"
No HKLM:Run realsched "C:\Program Files\Common Files\Real\Update_OB\realsched.exe" -osboot
No Startup Common C:\PROGRA~1\MICROS~2\Office10\OSA.EXE -b -l
No Startup User C:\PROGRA~1\LimeWire\LimeWire.exe -startup
The ones with the "no" entry beside them have been disabled from starting.
There were quite a few, some of them fairly significant memory hogs, such as Adobe Reader, and Limewire.
I know for a fact there are options within the Limewire program to not have it running at startup. Probably the same is true for Adobe, but since I don't use it, I can't be sure.
I wouldn't mess with Uniblue, either.
Ccleaner has a registry cleaner, available under "Issues". If you scan for and remove any found, make sure a backup is kept, and make a note where it is kept (or decide where to keep it yourself) in case of problems as a result. Ccleaner is generally safe to use as a reg cleaner, but sometimes cleans valid entries, in my experience, particularly if the associated program has not been used in a long time. You may notice a slight performance improvement.
I would certainly download the installer pack for SP3, and apply it. (It can later be removed via "add/remove programs" in the event of problems. Problems are generally not encountered.)
After applying it, which will take a few minutes, reboot, and then go to MS (or Windows) update. There are likely to be a lot of updates. At least one further reboot will be required.
Then see how it's all going.