petemus
That's what I did, and it went well, without registry hackery or such.
It's not hackery, but rather cleaning up bits of leftover code. You don't even have to go into the registry editor if you have a utility like JVPowertools or CCleaner, which searches for and cleans up all unused registry entries. After a reboot, all the old driver bits are gone!
This ensures a thorough fix as opposed to installing on top of the corrupted code and hoping it all works out. Also, by leaving the old drivers in there, you never know if they'll cause a problem again down the road.
I get that some folks are leery of anything to do with the registry, but a registry cleaner is just another tool. You don't have to know a thing about how it works - only how to run it. The only thing I suggest users learn to do is backup the registry beforehand. (In 20+ years of cleaning the registry I've never had to restore one because of a botched cleanup job. Just pointing out that there's an easy fix if something bad were to happen).
