Norton Security History

This problem has been mention a while ago by another poster. On Norton Security history, I am getting the high severity warning for Remote Access Protection Disabled. But when checking, they appears be nothing wrong and the remote desktop is turned off. Is this a bug in the software, or should I be concerned.

Thanks
William

1 Like

I get the same thing but only when I shut down the computer. It is timed exactly to the minute that is done. The 22.24.xxx used to have something similar stating User Logged OFF along with User Logged On for boot/restart.

I did have the same problem. I could solve it (for now),
using the norton uninstall tool, just unistall norton.
And reinstall it from the my norton page.

1 Like

I did uninstall and reinstall Norton. It work for a few days, but its now back again.

Thanks anyway.

Best
William

Yeah i have the same issue. It’s defnitly a bug linked to either Windows 11 or newer computers (PC that are as new as 2022 i would say maybe even 2020)

On my Wife’s PC, which is relatively old and has still Win10 in it works perfectly, none of the bugs mentioned here on the comunity forums seems to exist on her PC.

On my PC, put together by myself in 2022, i have the remote access disabled bug, which happens whenever we shutdown the pc or restart it. And also the Startup scan Data error when the anti virus scans Norton’s owns folder :rofl:.

That being said, everything seems to work very fine tough in exception of these 2 issues said above.

And honestly i gave up on worrying too, i just turned ON “enable debbug logs” for Norton and every week i let the anti virus send it to Gen symantec or whatever place it goes… this way maybe they will figure something out… someday

1 Like

fwiw ~

png_21226

png_21227

png_21228

How risks are detected here
Learn more about Intrusion Prevention here

This is either a bug in their code or a scare tactic. I saw the same thing appear yesterday. All my settings were correct. A simple reboot cleared the issue. Thus far its not returned. This bug is also how the brute force attacks are being logged. A Norton fix with the coding is in order.

SA