Norton Registry Scan Errors

Why is it when I run Norton one button check-up it keeps finding the same "invalid active X/com" entries in my registry? How do I repair my registry?

 

Once the scan is complete you should see a button marked Begin Fix - you need to press this. Alternatively, you can click on the item where the error is highlighted and expand the fetails for the errors, you can then see the registry key and if you right click or double click you can shoose to fix the individual items.

Which version of the Norton product are you using and which version of Microsoft Windows?

 

I always select the "fix selected problems" button, and it fixes the problems...but they return on the next scan.....INVALID ACTIVE X/COM ENTRIES. I am using NORTON SYSTEM WORKS and i have WINDOWS XP. I don't like screwing around with the registry on my own....that's why I'm asking you..... If you have any advice about registry errors or registry repair programs I would like to hear it in detail, (please) because I don't want to permanently damage my computer. thank you.

 

I just tried using "easy registry cleaner" and re scanned with norton system works and the same problems pop up......19 invalid active x/com entries. I click "begin fix" and rescan. Same result

 

anyone got any ideas?

 

Two possible routes here:

1) Analyse what the ActiveX/COM entries are and determine why they exist and eradicate the cause or reinstall the ActiveX/COM components. Do you know (from expanding the detail in Norton) what the ActiveX/COM are?

2) Use an alternative means of cleaning the registry. As you can see there are numerous such utilities: http://majorgeeks.com/downloads15.html and there are many threads here advising on a recommended choice. However, I use CCleaner (http://majorgeeks.com/download4191.html) and use the Scan for Issue button under the Issues tab. From my experience, this has a similar registry cleaning capabilities as Norton but allows you back up your registry before repair (so that you can restore if things go wrong).

I would go with option 2 as the simplier route to take but you may wish to take some time to understand what ActiveX/COM values are causing a problem and why then attempt a repair that way.