Detailed description:
I was investigating unusually poor battery life on a Lenovo ThinkPad T14s Gen 2 running Windows 11 with Norton 360 Deluxe fully updated.
During light use, LocalServiceNoNetworkFirewall repeatedly caused CPU usage to jump by roughly 10–15% every few seconds. I checked the service details and confirmed the activity was in the BFE / Windows Filtering Platform service host.
I then captured the issue using Windows Performance Recorder / Windows Performance Analyzer. During the high-CPU periods, the dominant call path included:
rpcrt4.dll!RPC_INTERFACE::DispatchToStubWorker
→ BFE.DLL!BfeRpcTransactionCommit
→ BFE.DLL!BfeTxnCommit
→ BFE.DLL!BfeTxnCoordinatorCommit
→ BFE.DLL!BfeObjectMgrCommitPhaseOne
The pattern repeated every few seconds.
I uninstalled Norton 360 Deluxe and rebooted. Immediately afterward, the recurring BFE CPU spikes disappeared and have not returned.
The laptop also became noticeably cooler and battery drain improved dramatically under comparable use. With Norton installed, a discharge test went from 100% to 31% in about 3 hours 22 minutes, despite using only about 30% display brightness. After removing Norton, battery drain was substantially slower while using about 50% brightness and the same kind of light workload.
netsh wfp show state also showed numerous Norton / Norton LifeLock / NLOK WFP providers, filters and callouts. I also saw Avast-labelled WFP components even though I have never installed Avast separately, which may be related to the current Norton/Gen networking stack.
I have retained the WPR/WPA .etl trace and WFP state data and can provide them privately to Norton engineering if useful.
Has anyone else seen similar LocalServiceNoNetworkFirewall / BFE CPU activity with current Norton 360 builds?
