I’m working on my husband’s laptop which is HP G60-458DX and I just updated his paid Avast to the newest version 6.0.1000 on the OS which is Vista64. I have made a discovery after much searching regarding my mortal enemy Norton.
The laptop has had some shutdown issues and is slow to boot. I have found that drivers
SRTSP and SRTSPX boot drivers that can’t be started and are delaying things are NORTON
RELATED. This machine had NIS on it but I removed I thought all traces without ever
setting the software in motion. Now, in Services I found a trace and disabled it for NIS
but I doubt that is all by any means. This machine has had Avast from since I removed the Norton product. I am appalled that I let traces remain.
I need some guidance on running the Norton Removal tool. Will it hurt Avast as it now stands? What can I do?
Donna in AR
I also suggest that you check for remnants by going into Safe Mode > Advance Search > NIS (and type in under a different search Symantec, and again Norton)…see if anything comes up. If so, delete and empty the recycle bin while in Safe Mode.
If you have something like CCleaner, there is a Slim version available as well at http://www.piriform.com/ccleaner/builds – 4th option down, run it after rebooting. It removes unused files (cache, temporary Internet files, etc.) from your system, allowing Windows to run faster and freeing up valuable hard disk space. It also cleans traces of your online activities such as your Internet history. Additionally it contains a fully featured registry cleaner (you can make a temporary back up of your registry fixes is Documents or on a USB).
If Avast does not seem to be working after uninstalling Norton, try doing an Avast Repair:
Go to Control Panel > Add/Remove programs > Avast Antivirus.
Scroll down and choose Repair function in the pop-up window.
Just a quick heads up in your quest to be Symantec-free… when you are searching for leftover drivers, enter “sym” into the search box. I just found symlcbrd.sys the other day, which is a Symantec Core Service BIOS reader, or some damn thing. Point being, some of their drivers begin with “sym”, and you won’t find them doing a search for “symantec”. Good luck.