LocalServiceNoNetworkFirwall Running on Windows 11 with Norton 360

With Norton 360 running, Task Manger show that LocalServiceNoNetworkFirwall is running using 6% of cpu.

I have not seen this happen before with Norton running and am concerned that Norton is broken. Did a full scan and found nothing.

Any suggestions of what is happening?

Hello @RedDog2

What DIY Troubleshooting have your tried other than Full Scan?

Did you run Norton LiveUpdate + Restart (not Shut down) machine?

Did you try Troubleshooting? → Reset to Default &or Repair Norton
Note: Reset to Default resets Cloud Backup

Did you confirm?
Base Filtering Engine → Running Automatic


Windows Defender Firewall → Running Automatic

===============================================

fwiw ~ may be related:
https://community.norton.com/t/noticable-increase-in-cpu-utilisation-by-the-windows-localservicenonetworkfirewall-process/517736

===============================================

The process LocalServiceNoNetworkFirewall is a grouping of Windows services that includes the Windows Defender Firewall and the Base Filtering Engine (BFE). When you run Norton 360, this process should typically remain idle or low-impact because Norton’s Smart Firewall takes over most filtering duties.

If you are seeing high CPU or memory usage from this process while Norton is active, it usually indicates a conflict between Windows’ built-in security and Norton’s layers.

Common Fixes for Conflicts

  1. Restart the Base Filtering Engine (BFE):
  • Open Task Manager (Ctrl+Shift+Esc).
  • Find LocalServiceNoNetworkFirewall, right-click it, and select Go to details.
  • Right-click the highlighted service and select Go to service(s).
  • Locate BFE (Base Filtering Engine), right-click it, and select Restart.
  1. Reset Windows Firewall Defaults:
  • Sometimes, corrupt rules from previous installations cause the built-in firewall to loop.
  • Go to Settings > Network & internet > Advanced network settings > Windows Firewall.
  • Click Restore firewalls to default.
  1. Check for “Periodic Scanning”:
  • Norton may conflict if Windows Defender’s “Limited Periodic Scanning” is on.
  • Go to Windows Security > Virus & threat protection > Microsoft Defender Antivirus options and ensure Periodic scanning is toggled Off.
  1. Change Norton to “Windows Settings Mode”:
  • In recent Norton 360 versions (v24+), users have found success by letting Windows manage the core network profile.
  • In the Norton main window, look for Settings > Firewall and see if an option for Windows Settings Mode is available to resolve connection or performance blocks.

Why this happens with Norton 360

  • Corrupt Installation: A “dirty” update can leave Norton and Windows fighting for control over the same network ports. Using the Norton 360 Remover tool often fixes this by cleaning out old registry rules .
  • Network Profile Flips: Norton sometimes incorrectly flags a home network as “Public,” causing the Windows Firewall process to spike as it applies stricter security rules. Ensure your network is set to Private in both Windows and Norton settings.

=============================

=============================

AI sourced content may make mistakes

I did confirm that Base Filtering Engine & Windows Defender Firewall are running in Automatic.

Ran Norton LiveUpdate and it did have an update which required restart. After restart, LocalServiceNoNetworkFirwall was not listed in Task Manger.

So far, things seem normal.

1 Like

Hello @RedDog2
Thanks for sharing your progress