![]() Also as well, my Norton installation has been in place since 2013, so I figure a clean sweep wouldn't hurt as it has gone thru all these product updates/upgrades over time and accumulated tons of stuff. Whenever it decides to upgrade to latest, maybe by then it will have the fix/patch in place. I know this isn't at the most recent 360 version (the one released earlier this month), but I'll leave it as is for the present. I'm now sitting at version 22.22.2.10 and no CPU spiking/process respawn & terminate quickly any longer.so pleased right now. Whatever was supposed to come down the pipe or connect in the background was not happening for me - so this afternoon I did a complete uninstall (remove all user data) from Control Panel followed by running Norton Remove and Reinstall tool followed by a total fresh reinstall of 360. I couldn't wait any longer as nothing changed at all for me since the 'fix' was announced yesterday (4/16). ![]() But I won't be surprised if it starts again. ![]() It used to start acting up within minutes, so getting to an hour+ is an improvement. No idea if it will last, but so far, so good. I even downloaded a file and ran a live update to "wake up" Norton, and it went back to normal as should after it did it's thing. I then restarted again and it seems to be fine so far. So I checked ccleaner, and it was still an option, so I did it again through there, which only took about 2 seconds. When I restarted, I checked Revo again and Norton was no longer an option. The problem with that is that you don't get to use the next part of Revo, which searches for all the left overs. Unfortunately, Revo launches Norton to uninstall it, and then when it is complete, Norton insists you must restart. Yesterday I had tried uninstalling through Control Panel, and then reinstalling, but the problem persisted. ![]() I just tried the suggestion above from xjoex, and after 1 hour on 2 different machines, it's still working as it should.
0 Comments
Leave a Reply. |