Installed Vista-->Windows7 update. W7 disabled the Symantec Heuristics driver stating same made W7 unstable. Ran Autodetect package, downloaded newest 360 (which I'm fairly certain was the same already installed), installed same, same driver problem post boot.
Installed Vista-->Windows7 update. W7 disabled the Symantec Heuristics driver stating same made W7 unstable. Ran Autodetect package, downloaded newest 360 (which I'm fairly certain was the same already installed), installed same, same driver problem post boot.
markg2 wrote: If I use the removal tool is there a way to save my saved browswer passwords?
Yes there is. Go into Norton 360 click on Manage Identity Protection and at the bottom of the screen there is a back up setting that you can use to export your logins and passwords to an npm file, click on configure and follow the prompts. You can restore this file after you reinstall Norton 360.
I did as you suggested--removed all with the removal tool and reinstalled. Windows still thinks the entire of N360 is unstable with Windows 7 (attachment) and still disabled the heuristic driver (attachment). Sorry--tried to attach screen shots of the two error messages but the forum will only accept txt and log.
I need to have a better idea as to what the disabled driver does and how the lack of it adds to my exposure. Based upon that information I'll be better able to judge whether to dump Norton for a time until they resolve the problem and use Microsoft's well received new security software in the meantime.
I did as you suggested--removed all with the removal tool and reinstalled. Windows still thinks the entire of N360 is unstable with Windows 7 (attachment) and still disabled the heuristic driver (attachment). Sorry--tried to attach screen shots of the two error messages but the forum will only accept txt and log.
I need to have a better idea as to what the disabled driver does and how the lack of it adds to my exposure. Based upon that information I'll be better able to judge whether to dump Norton for a time until they resolve the problem and use Microsoft's well received new security software in the meantime.
Mark
Hi Mark
Thanks for the update. You can upload an image(s) by clicking on the icon that looks like a little tree. We would like to see the error messages if you can get them uploaded to help decide the next step.
And here is a shot of another problem that I mentioned in a different topic this forum yesterday. Clicking Fix does not fix. Your website hotfix for this sonar does not apply to N360. Oddly, after 360 was running yesterday, the error went away later in the day. Don't know about today yet with the new install.
While you guys are at it, here's the last of the Windows 7 compatability problems. One Click Support will open and initialize all on its own and display the following same error each time. FWIW, I ran Check for Updates each time I installed the software and each time I would get the following:
What is the version of N360 you have installed? The version number is listed in the Help&Support > About menu on the main interface screen.
Also, please run Live Update manually after you install N360 until you get the message that there is no more updates for you system and then reboot your system. There is a compatibility update that must be downloaded via Live Update. Let us know how these steps turn out for you.
Regarding setup.exe--prior to updating from Vista-->W7 I visited your site and downloaded the latest version 3 that was said to be compatible with W7. I again used that setup.exe after having the initial problem with 360 post W7 update. Subsequent to that I ran your compatibility software (I think that's what it was called) and it directed me to again download what appeared to be the same v3 from your site--which I did. I didn't use your links since I didn't know which of the two flavors of 360 I have.
I did not click run program, I clicked find solution online.
I followed your instructions and all is now fine--thanks.
I have a suggestion. Since I had installed what was reported to be a W7 compatible version prior to upgrading and after the install ran live update and installed ~55mb of definitions, I improperly 'assumed' that the error 3039,1 message to manually update was also an install compatibility error. I would not have called this error an error if I were running the show, rather an additional scripted part of the install process--possibly automatic and transparent. Or, at least, a more explanatory top statement that for some reason although you think you've done everything correctly, you haven't due to 'whatever' and must follow these additional steps.
I followed your instructions and all is now fine--thanks.
I have a suggestion. Since I had installed what was reported to be a W7 compatible version prior to upgrading and after the install ran live update and installed ~55mb of definitions, I improperly 'assumed' that the error 3039,1 message to manually update was also an install compatibility error. I would not have called this error an error if I were running the show, rather an additional scripted part of the install process--possibly automatic and transparent. Or, at least, a more explanatory top statement that for some reason although you think you've done everything correctly, you haven't due to 'whatever' and must follow these additional steps.
Just a thought.
Thanks again,
Mark
Hi markg2
I'm happy for you that all is now working. Thanks for sticking with it through such a load of instructions. I note your suggestion and will pass your remarks on.
If your question has been answered to your satisfaction then please mark the message that you believe contained the solution to your issue by using the green button beside it. This will mark the thread as Solved and others will know that it has been answered and can see the solution.