Please fix the bug in this thread immediately!
It’s confirmed that this isn’t a problem with individual PCs.
This is happening daily; it’s a top priority.
I’m fed up!
Please fix the bug in this thread immediately!
It’s confirmed that this isn’t a problem with individual PCs.
This is happening daily; it’s a top priority.
I’m fed up!
When will it be fixed?, a few posts on this since the update.
All notifications turned off.
Summary pops up every evening same time, interrupting gaming, takes over, so ruins game (or anything else). I bought so does not pop up anything, and has been working well for years until this update.
It is not the computers, PC works fine.
and not paying for anything else for as long as running fast.
@Selvakumar.S Would someone your side at Norton please chime into this thread with something regarding it being corrected? TIA.
SA
Same here… But this happens to me almost every day. I go into Smart Firewall and all the rules in program control have been obliterated. This, combined with the fact that the Norton application pops up centrally on the screen evey day now at the same time is just leading me to move provider.
Norton must really LOVE losing customers - that’s all I can think.
The issue with the Norton interface popping up should be resolved. Norton just released a fix.
Please run LiveUpdate and restart your systems and test.
New problem at the same old time: For several days, our TV streaming was interrupted at 9:49 PM by a Norton window suddenly popping up in the center of the screen (see here).
Tonight, the experience was different. Starting at the same time, 9:49 PM, the program we were watching on Amazon Prime Video started getting choppy and ground to a halt in less than half a minute. There was no Norton screen obscuring our view, but on the other hand the screen was frozen: there was no mouse cursor and Windows took minutes to even respond to Ctr-Alt-Del for the Task Manager.
When I finally got back to the desktop, Task Manager was reporting inordinately high memory usage by two Norton processes, NIItoolsSvc.exe and su_worker.exe.I tried to upload screenshots of Task Manager showing memory usage by these processes, but the upload function keeps failing. Suffice it to say that RAM usage was hovering from 87% to 93%, with three-quarters of that taken up by the two Norton processes. (The PC has 16GB of RAM installed.)
We were barely four minutes from the end of the show when this happened. I ended up having to reboot and wait for Windows to settle back down before we could go back to streaming, losing about a half-hour all told including the initial freezing and waiting for Task Manager to show up. But soon after we resumed streaming, the freezing from these two Norton services recurred. We had to resort to a laptop to finish watching literally the last 16 seconds of the program.
This is completely unacceptable performance by Norton 360.
We are currently on Norton 360, version 26.8.11404.0.
There seems to be an issue with version 26.8.1125 breaking internet connectivity by smothering outbound DNS traffic.
The full technical details – which traced the root cause to Norton’s WFP (Windows Filtering Platform) – I reported in another thread named:
“Norton 360 may be blocking DNS and Internet connectivity after recent update – Windows 10”.
*Reporting it here too, in case this is the more appropriate thread?
The root cause short summary:
Norton’s Windows Filtering Platform (WFP) callout drivers — registered under the provider tag `NLOK` — appear to register callouts at, among other layers:
- `FWPM_LAYER_ALE_AUTH_CONNECT_V4` / `V6` (connection authorization)
- `FWPM_LAYER_OUTBOUND_TRANSPORT_V4` / `V6` (outbound packet send)
In this build, these callouts did not return a timely classification for outbound DNS queries.
For UDP-based DNS, the connection-authorization step for the query itself never completed, so no packet was ever handed to the network stack.
For DNS-over-TCP attempts, the TCP handshake completed normally (passing through a different, correctly-functioning Norton-owned layer), but the subsequent query send at the outbound transport layer hung in the same way.
The behavior is consistent with a callout **pending** a classification indefinitely rather than explicitly permitting or denying it. It’s a failure mode that is externally indistinguishable from “nothing happening”.
Have the newer updates fixed the hooks breaking windows processes and making my computer unusable?
@bBlue Random thought and question for you. Does disabling IPv6 locally within your Windows internet adapter and a reboot correct anything?
SA
Hi @SoulAsylum
No, I did not try that as a troubleshooting step.
Because the fix (for myself and 3 other users) was uninstalling Norton, I won’t be able to test that currently.
And I wasn’t planning on reinstalling it until there was some confirmation or feedback from Norton Support – either that A) reinstalling is a proven fix, or B) a fix will be released asap.
My larger question is, based on the responses in the other thread I referenced:
Are we the ONLY 4 users in the world experiencing this issue!?
Are there no other user reports in other locations and sources?
Thanks.