I'm trying to establish exactly what you did, and why it went wrong. I've downloaded a copy of Hitman Pro and read through the product description on the website, and also read carefully the License Agreement. I haven't yet run it. One thing I note is that this program is not known to McAfee's Hackerwatch system, so I've sent through all the information Hackerwatch was asking for.
Hitman Pro is designed to be a "second opinion" and to be compatible with resident AV programs, so it says. There is though a strong possibility of conflicts with a running McAfee installation.
The license agreement makes it clear that you either agree to a one-off free 30-day trial installation or you accept that by downloading the program you are agreeing to pay SurfRight for using it. If you accept the free version for 30 days you can only scan your system for infections, the free version will not remove anything it finds. So be cautious of accepting at face value any findings from this free scan; you should double-check that any infected files are not false positives by submitting them to VirusTotal for analysis (or to McAfee, if you strongly suspect that the files are indeed malware).
If your downloaded program went from detection to Repair then you have (knowingly or not) installed the not-free version. The files or processes it detected as malicious it will have attempted to remove :
When the file is classified as malicious by the Scan Cloud, the Hitman Pro client is placing the infection into quarantine. Various techniques ensure that all infections are completely removed without false positives.
- Close handles (e.g. unload DLL from winlogon)
- Close processes (e.g. winlogon stays)
- Remove object from disk
- Schedule object removal using PendingFileRenameOperations
- Remove references like shortcuts and registry entries
- Restore standard registry keys to default values (e.g. Userinit)
- Disable service drivers
- Deploy native NT bootdelete to remove resilient disk objects
- After reboot retry removal and rescan to ensure complete removal
By so doing, it may have triggered some preventive action by your McAfee installation. I can't be sure about that. What you say happened was that on reboot you got a BSOD. If that is the case there will be a minidump or kernel dump in your %systemroot% directory, which should throw some light onto the reason for this. Microsoft say that a BSOD simply means that something was trying to write into an area of protected memory, and that 3rd-party drivers are often the culprit.
If you're trying to do a repair installation on Windows 7 then the best person to help you is Ex_Brit, who knows a lot more about W7 than I do. My specialisations don't include that OS.
The problem you originally had (redirects) may well disappear if you do an OS re-install, unless the underlying cause lies outside your system.
