Hello Raiden. FWIW, Norton has nothing to do with updates from Microsoft.
There're people that don't like the crappy updates that MS deploy
Your specific issue, as shown in your thread that you linked, is that you are also on an older version of Windows 10, but not on LTSB as the OP of the thread is having issues with. 1607 is not supported by Microsoft any longer which I am sure you are aware of, making it extremely vulnerable. Conversely, There have been a few Norton product releases after version 22.22.6.10, did you attempt to update in the past and had issues or just updating now? TIA.
SA
https://community.norton.com/en/forums/new-update-using-50-processing-idle
Could some mod deliver this issue to a developer? There're people that don't like the crappy updates that MS deploys. And there're people that are expecting a good customer service, specially since the last known good version (22.22.6.10) I had of Norton is the previous one to this new mess.
I believe that since you are at least on the Windows 10 Anniversary Update, for the latest Norton to function correctly. Your Windows version isn't getting anything other than patches that Microsoft deems a risk to the Windows environment at large and nothing more feature wise. That is most likely the issue. Is Norton version 22.22.7.13 the version that causes your issue?
https://answers.microsoft.com/en-us/windows/forum/all/norton-doesnt-start-on-windows-10-startup/17a82616-7722-4d9b-9eef-3536e4288a21
SA
Hello, thank you so much again for your advice! this is running in a home environment but I run them like it is a corporate environment except for having them joined to a domain. The computers are running Windows 10 Enterprise LTSB 2016 Edition version 1607 build 14393.0. I had some software that was not cooperating with windows updates a while back and was already running LTSB on a PC acting as a home server, so moved several other PCs over to it as well. I have not tried using the "remove only" option in Norton RnR yet, I will give that a try tomorrow as well as delete everything I can find Norton related on the PC and try again. I really appreciate the advice, and that is a good idea, my version of Windows 10 could be too old that Norton's code doesn't work anymore, although Microsoft is saying I have extended support until 2026. As far as GPO is concerned, I haven't made any changes to the default options that would affect antivirus and before this Norton update got released about a week or two ago, I have been running Norton fine for years.
Hello again. I'm not sure whether you are in a home or corporate environment since the latter can be see while using a corporate issued device in a remote work environment. May we ask. What version and build of Windows are on computers affected? LTSB allows IT Admins to remain on older versions and builds that can save them the hassles of downtime, upgrades and updates that would otherwise take a ton of time and expense to perform. It may also not update the core of Windows in a manner that would keep third party software functioning properly. I'm wondering if your Windows version and current issues, fit that scenario.
Another thought is GPO ( Group Policy ) restrictions may also be at play. Have you considered the following?
https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/deploy-manage-report-microsoft-defender-antivirus?view=o365-worldwide
Have you manually removed ALL folders and directories related to Norton AFTER performing the R&R, and, have you done the "remove only" scenario? Step #5 in the article explains further.
https://support.norton.com/sp/en/us/home/current/solutions/v60392881
SA
Thank you so much for your reply and I really appreciate it! I have disabled fast startup on all my computers to try to avoid weird things like this. I should clarify that when I restart the computer, it only drops Norton's CPU usage back to 0 instead of hogging 25-30% of it all the time. Norton still doesn't open even after a restart and will start the infinite 25% CPU usage again without opening when I try to open it after a restart.
Hello Joe, do you have "fast startup" enabled? If so disable it and reboot. Recheck for the issue still persisting.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
SA