No Surprise (Score 1)

As someone who used to sell Norton this comes as no surprise, when my company was upgrading and switched away from Norton to E-Trust Ass. A.V. we had the same issue, however there was a simple fix. I would be surprised if this fix doesn't work for MS A.V. as well as it did for E-Trust. But I'll get to that in a minute. Fact of the matter is anytime you install more than one anti-virus on a computer you risk this problem due to the way A.V. companies code their software, the signatures in their databases are snippets of code that viruses, trojans, ect. use and the A.V. software uses these snippets to recognize the codes. Which subsequently is exactly why they start popping up and screaming about each other as if they were a hostile program. That being said on to the solution. The easiest way to fix the problem with Norton Windows and E-trust (if you had installed e-trust while Norton was installed) was to boot into safe mode, find the Norton root folder in the C directory usually C:\program files\Norton and delete the whole folder. Reboot, after the boot up is complete, go to the recycling bin and restore all of Norton's files, go to add/remove programs, in the control panel and uninstall Norton thus ridding yourself of the ever nasty registry entries and getting rid of Norton so you can use E-trust. Now I have a hard time believing this solution won't work for MS A.V. and if it doesn't its cause MS once again should leave specialized software fields to the specialists because frankly there is no reason for MS A.V. to write to the registry if it detects a virus. If it is there is something else going on entirely. Jack Please note all we have done here is prevented Norton from booting its background scanner and other software thus getting around any active files causing MS A.V. to shit a brick. AND OR causing any I/O conflicts that might have caused the system to freeze on boot-up (a common problem when dealing with E-trust in this situation)