Reply to thread

Message

<blockquote data-quote="conceptualclarity" data-source="post: 797037" data-attributes="member: 11916">I have found that programs&#039; own uninstallers are not reliable about removing drivers, and neither are Revo and the other third-party uninstallers. I wrestled with this issue when I was frustrated that O&amp;O drivers from a program I hadn&#039;t even used were hanging around and causing blue screens after I uninstalled the program. I was pissed, so I shredded those drivers, and next thing you know I can&#039;t boot my computer. That lasted a good while. I had to get AtlBo&#039;s help to add the drivers back temporarily. The problem was in the registry. Through the registry Windows was married to the autostart of those drivers.Within the last two years I reluctantly uninstalled ZAM because of too many blue screens. The uninstall left the offending driver behind. What I do these days in a situation like that is run RegScanner by NirSoft. I first use RegEdit to make an up-to-date full registry backup (Export). I then use RegScanner to make a thorough purge of the program (zemana in this case) and I particularly scan for the name of the driver(s). Only after cleaning up the program leftovers in the registry do I deal with the driver. I move it from system32 to a non-sensitive folder. Only after verifying that my bootups are OK do I shred the driver.It pays to be aware of driver installation when you install a new software. Ideally for reference you should use one of those programs that monitors and records all file/folder and registry activity during the installation. Maybe it&#039;s not realistic to do that with every little program, but with ones that are sure to install drivers, like security programs, you should.</blockquote>

[QUOTE="conceptualclarity, post: 797037, member: 11916"] I have found that programs' own uninstallers are not reliable about removing drivers, and neither are Revo and the other third-party uninstallers. I wrestled with this issue when I was frustrated that O&O drivers from a program I hadn't even used were hanging around and causing blue screens after I uninstalled the program. I was pissed, so I shredded those drivers, and next thing you know I can't boot my computer. That lasted a good while. I had to get AtlBo's help to add the drivers back temporarily. The problem was in the registry. Through the registry Windows was married to the autostart of those drivers. Within the last two years I reluctantly uninstalled ZAM because of too many blue screens. The uninstall left the offending driver behind. What I do these days in a situation like that is run RegScanner by NirSoft. I first use RegEdit to make an up-to-date full registry backup (Export). I then use RegScanner to make a thorough purge of the program (zemana in this case) and I particularly scan for the name of the driver(s). Only after cleaning up the program leftovers in the registry do I deal with the driver. I move it from system32 to a non-sensitive folder. Only after verifying that my bootups are OK do I shred the driver. It pays to be aware of driver installation when you install a new software. Ideally for reference you should use one of those programs that monitors and records all file/folder and registry activity during the installation. Maybe it's not realistic to do that with every little program, but with ones that are sure to install drivers, like security programs, you should. [/QUOTE]

Verification