What is ‘LocalserviceNoNetworkFirewall’ and How to Fix its High CPU Usage?
Fix: ‘LocalserviceNoNetworkFirewall’ High CPU Usage
LocalserviceNoNetworkFirewall is a part of Windows security and is used by Windows Defender (or by other Windows API-based firewalls) in their operations. Usually, this service does not use much CPU or memory.
But the issue arises, when this service starts eating a chunk of memory along with high CPU usage (in some cases, more than 50%) and causes the system to be so sluggish that it becomes impossible to use the system.

LocalserviceNoNetworkFirewall High CPU Usage
Many things can trigger a high CPU usage by the LocalserviceNoNetworkFirewall but we identified the following chiefly responsible for the issue:
- Conflicting Firewalls: If you are using another firewall (especially, that is using the Windows Defender API) along with the Windows firewall, the two may conflict with each other, resulting in high CPU usage.
- A Large Number of Conflicting Firewall Rules: If an old installation of a 3 rd party firewall has included thousands of inbound/outbound rules, while Windows defender has its own such rules, these conflicting rules may require the firewall to use the excessive CPU to execute all of them.
- Corrupt Installation of 3 rd Party Security Product: If the 3rd party security product like Avast Premium has become corrupt, then this corruption can cause the excessive use of the CPU by the LocalserviceNoNetworkFirewall.
- Corrupt Settings of Windows Firewall: The LocalserviceNoNetworkFirewall service may show a high CPU usage if the Windows firewall settings have become corrupt due to interference from the other security product.
Keep in mind that some of the users may fail to perform the under-mentioned solutions on their systems because the system can be very sluggish. In such a case, you may try the solutions after disconnecting the system from the Internet (either by unplugging the ethernet cable or switching off the router) or try them in the safe mode of your system.
Restart the Windows Firewall
The high CPU usage by the LocalserviceNoNetworkFirewall could be a temporary glitch of the Windows Firewall and restarting the same may solve the problem.
- Right-click Windows and open Task Manager.
Open the Task Manager from the Quick Access Menu - Now head to the Services tab and right-click on WinDefend (Microsoft Defender Antivirus Service).
Restart the Windows Defender Service - Then, in the sub-menu, select Restart and once the service is restarted, check if the CPU usage is back to normal.
Update the PC’s Windows to the Latest Build
The incompatibility between the outdated OS and other system modules (like a driver or a 3 rd party firewall) may cause the high CPU usage by LocalserviceNoNetworkFirewall. Here, updating the PC’s Windows to the latest build may solve the high CPU.
- Click Windows, search, and open the System Settings of Check for Updates.
Open Check for Updates - Now, in the Windows Update, click on Check for Updates.
Check for Windows Updates - If it shows some updates are available, then download and install those updates.
- Once the PC’s Windows is updated to the latest build, check if the high CPU usage by LocalserviceNoNetworkFirewall is normalized.
Disable/ Enable the 3 rd Party Security Firewall and Windows Defender Firewall
If you are using more than one firewall on your system i.e., Windows Firewall and a 3 rd party firewall (like GlassWire), then one may not be working properly with the other due to a glitch and causing the issue. In this context, disabling and enabling both firewalls may solve the problem.
- Right-click on the 3 rd party firewall like GlassWire in the system’s tray and select Exit.
Exit GlassWire from the System’s Tray - Now click Windows and type Windows Defender.
- Then right-click on Windows Defender Firewall with Advanced Security and select Run as Administrator.
Open Windows Defender as Administrator - Now click on Windows Defender Firewall Properties and for the following profiles, set the Firewall State to the off position to disable the Windows Firewall:
Open Windows Defender Firewall Properties - Then apply your changes and close the Windows Defender.
Disable Firewall for All the Profiles of Windows Defender Firewall - Again, open the Windows Defender and enable its Firewall as discussed above.
- Now close the Windows Defender and enable/launch the 3 rd party firewall to check if the LocalserviceNoNetworkFirewall issue is resolved.
Revert the Driver Update
If your system recently got through a driver update, especially, ATI Radeon driver, then that update may conflict with the system’s firewall, and reverting the update may solve the problem.
- Right-click Windows and open Device Manager.
Open Device Manager - Now expand the latest updated device (e.g., Display Adapters) and double-click on the device (e.g., ATI Radeon).
Double-click on Radeon Device in the Device Manager - Now head to the Driver tab and click on Roll Back driver (if applicable).
Roll Back the Radeon Driver - Then follow the prompts to revert the driver update and restart your system.
- Upon restart, check if the high CPU usage is resolved. If so, then you may defer the driver update, till the issue is reported to solve.
Reset the Windows Firewall to its Defaults
Any customization of the Windows firewall (e.g., a newly added inbound or outbound rule) may have caused the overload on the system, thus causing the issue. In such a scenario, resetting the Windows Firewall to its defaults may solve the problem.
- Click Windows, type, and open Windows Security.
Open Windows Security - Now, in the left pane, head to the Firewall & Network Protection.
- Then click on the Restore Windows Firewall to its Defaults.
Restore the Windows Firewall to the Defaults - Now head to the Virus & Threat Protection tab (in the left pane) and under Virus & Threat Protection Settings, click on Manage Settings.
Open Manage Settings Under Virus & Threat Protection Settings - Then open Add or Remove Exclusions under Exclusions.
Click on Add or Remove Exclusions Under Exclusions - Now click on Add an Exclusion and select Folder.
Add a Folder Exclusions in the Windows Security - Then enter the following path in the address bar:
- Now click on Select Folder and close the Windows Security.
Add Windows Defender in the Exclusions of Windows Security - Then restart your PC and upon restart, check if the high CPU usage issue is resolved.
Edit the Cisco Umbrella Settings
Many of the Cisco Umbrella (a cybersecurity product) users reported that this application caused the high CPU usage on their system’s due to a bug. If you are using the Umbrella application, then check if the same is not causing the issue for you. Before proceeding, make sure that you are using the latest version of the Cisco Umbrella client.
Disable IP Layer Enforcement Feature of Cisco Umbrella
- Navigate to the Centralized Settings of the Umbrella Roaming client and open its Advanced Settings.
- Now, in the section of Enable Intelligent Proxy, uncheck Enable IP-Layer Enforcement and click Continue to save your changes.
Uncheck Enable IP-Layer Enforcement in Cisco Umbrella - Now restart your phone and upon restart, check if the High CPU usage issue is resolved.
Disable the Cisco Umbrella Service
- Click Windows and type Services.
- Then, right-click on it and select Run as Administrator.
Open Services as Administrator - Now double-click on the Umbrella service and set its Startup type to Disabled.
Open the Umbrella Client Service - Then click on the Stop button and reboot your PC.
- Upon reboot, check if the High CPU usage is normalized.
- If not, then check if uninstalling the Umbrella client clears out the issue. If so, you may reinstall the client to check if the issue does not return. If it does, then you may contact Cisco support to find the feature triggering the issue.
Delete the Firewall Rules
If there are some firewall rules added to the Windows firewall e.g., from a previous installation of a 3 rd party firewall (like a Trend Micro), whereas the Windows firewall has its own set of similar rules, then that can overload the Windows firewall to execute all the conflicting rules. In such a case, deleting the firewall rules in the Windows firewall may solve the problem.
- Click Windows and type Windows Firewall.
- Then, right-click on Windows Firewall with Advanced Security and select Run as Administrator.
- Now, in the right pane, click on Export Policy and then save the file (just in case…).
Export Policy of the Windows Defender - Then select the Inbound Rules tab and in the right pane, delete the rules you do not want to keep or not required. It may take some time to complete but be careful, do not delete something essential.
- Now repeat the same in the Outbound Rules tab and check if the issue is resolved.
- If that did not work or you do not want to check every rule, then, in the left pane, select Windows Defender Firewall with Advanced Security and expand the Action menu.
- Now select Restore Default Policy and then confirm to restore the policy.
Restore Windows Defender Firewall to Default Policy - Then close the Windows Defender Firewall window and check if the CPU usage issue is resolved.
- If you cannot open the Windows Defender Firewall or its rules cannot be edited, then boot your system into the Safe Mode.
- Now click Windows and type WF.MSC.
- Then right-click on it and select Run as Administrator.
- Now check if repeating steps 4-6 solves the LocalserviceNoNetworkFirewall issue.
Reinstall the 3 rd Party Security Product
If you are using a 3 rd party security product like Avast Premium, its corrupt installation may conflict with the Windows Firewall and thus cause the issue at hand. In such a scenario, reinstalling the 3 rd party security product may solve the problem.
- Right-click Windows and open Apps & Features.
Open Apps & Features - Now click to expand the security product (e.g., Avast) and click on Uninstall.
Uninstall Avast Antivirus - Then follow the prompts to completely uninstall the product and reboot your PC.
- Upon reboot, check if the LocalserviceNoNetworkFirewall issue is resolved.
- If not, then download the security product removal tool from the OEM’s website (like the Avast website) and remove any left-over traces of the security product.
- Now check if the system is not sluggish anymore. If so, then you may reinstall your security product, if it does not cause the issue again.
- If that did not work, then clean boot your PC and check if that resolves the issue. If so, then you may find the problematic application/process/service by one by one re-enabling the ones that were disabled during the clean boot process.
Edit the System’s Registry
If nothing has worked for you so far, then editing the Windows Defender-related registry values may solve the problem.
Warning: Proceed at your own risk as editing the PC’s registry is a skillful task and if not done right, you may cause everlasting damage to your data/system.
- Firstly, to be safe, create a backup of the system’s registry.
- Now click Windows, type, and open Notepad.
Open Notepad - Then copy and paste the following in the Notepad:
- Then expand the File menu and click Save.
Save the File with .reg Extension - Now select a location to save the file, preferably on the desktop of your system, and enter the name for the file with .reg extension e.g., MpsSvc.reg.
- Then close the Registry Editor and right-click on the above-mentioned file (e.g., MpsSvc.reg).
- Now select Merge and then confirm to merge the registry keys.
Merge the Registry Key to the Registry - Then restart your system and upon restart, hopefully, the CPU will not be throttling.
If nothing works, then you may perform a clean installation of Windows to get rid of the high CPU usage by LocalserviceNoNetworkFirewall.
Fix LocalServiceNoNetworkFirewall High CPU or Power Usage
LocalServiceNoNetworkFirewall is a service used by Windows Defender Firewall and is a part of Windows security. In general scenarios, it doesn’t consume much memory space and resources. However, some users have complained that the LocalServiceNoNetworkFirewall service is consuming too much CPU or Power in the Task Manager of Windows 11/10. Some users reported that it consumes over 50% CPU on their PCs. For many users, it has made their system sluggish and slowed their PC making it almost difficult to use.

If you are dealing with the same problem, we are going to show you how you can get rid of this problem. In this post, we are going to discuss multiple working fixes that worked for users to resolve the problem. Let us check out.
Why does LocalServiceNoNetworkFirewall use so much CPU?
- If you are using a third-party firewall and it is conflicting with Windows Firewall, this issue can be caused.
- In case you have set up too many rules in Windows Firewall, it can result in excessive CPU usage of LocalserviceNoNetworkFirewall. You can try deleting custom firewall rules in that case.
- This issue can be caused if you are dealing with the corrupted installation of your third-party firewall program and it is conflicting with Windows Firewall. In that case, uninstalling and then reinstalling the third-party firewall might help you fix the issue.
- Another reason for this problem can be corrupted customizations or settings of the Windows Firewall. If the scenario is applicable, you can set the Windows Firewall to default configuration to resolve the problem.
Based on the scenario you think is best suited to you, you can try an appropriate fix from the guide to counter this problem.
Fix LocalServiceNoNetworkFirewall High CPU or Power Usage
- Restart Windows Firewall.
- Update Windows to the Latest Build.
- Disable, then Enable third-party Security Firewall and Windows Defender Firewall.
- Revert the Driver Update.
- Reset Windows Firewall to its Defaults.
- Delete the Firewall Rules.
- Reinstall the third-party security suite.
1] Restart Windows Firewall
- Firstly, open the Task Manager by using Ctrl + Shift + Esc hotkey.
- In Task Manager, go to the Services tab and locate the WinDefend (Microsoft Defender Antivirus Service) service.
- Now, right-click on the WinDefend service.
- Next, select the Restart option from the context menu.
- When the service is restarted, see if the problem is resolved now.
If the issue still persists, you will need to try some additional troubleshooting methods to fix it up. So, move on to the next potential fix.
2] Update Windows to the Latest Build
If you are using an outdated version of Windows OS, consider updating it to the latest build. Some incompatibility issues with OS and other system modules might be causing high CPU usage of the LocalServiceNoNetworkFirewall service. So, update your Windows and then see if the error is fixed now. Updating your Windows is recommended to improve the stability of your system and it also fixes some bugs.
To update Windows, open the Settings app and then go to the Windows Update section. Here, you can click on the Check for updates button and download and install all available updates. In case you are on the latest OS build and still encountering this problem, you can move on to the next fix.
3] Disable, then Enable third-party Security Firewall and Windows Defender Firewall
Are you using more than one firewall security on your PC? If yes, the problem might be caused due to that. To counter the issue, you can try disabling both the firewalls and then enable them again.
First of all, close the third-party firewall you are using. To do that, right-click on your firewall from the system tray and click on the Exit button to close it. You can also open that Task manager and end processes related to your third-party firewall.
After that, open the Windows Defender Firewall with Advanced Security as an administrator and then click on the Windows Defender Firewall Properties button. Now, set the Firewall State to Off for Domain Profile, Private Profile, and Public Profile. Then, click on the Apply > OK button to apply changes.
Next, you can open Windows Defender Firewall and enable/ set it to On. And then, launch your third-party firewall. See if this method fixes up the issue for you.
4] Revert the Driver Update
If you recently installed some driver update, there are chances that it might be conflicting with Windows Firewall. If the scenario is applicable, you can try rolling back recent driver updates and see if this resolves the issue for you.
5] Reset Windows Firewall to its Defaults
The high CPU usage of LocalServiceNoNetworkFirewall can be caused due to customizations of the firewall. For example, if you have added inbound or outbound rules or some more customizations to Firewall, it can overload your system. In that case, you can try resetting Windows Firewall to its default settings and see if the problem is fixed.
Firstly, open the Windows Security app from search and then go to the Firewall & Network Protection tab. Next, click on the Restore firewall settings to default button.
After that, go to the Virus & Threat Protection tab and then click the Manage Settings option. Then, press the Add or Remove Exclusions and tap on the Add an exclusion option, and then select Folder. Now, enter C:\ProgramData\Microsoft\Windows Defender\ location and click on Select Folder.
Finally, close Windows Security and restart your PC to check whether the problem is resolved now.
6] Delete the Firewall Rules
- Open Windows Firewall with Advanced Security and from the right-side pane, click on the Export Policy to save existing policy just to be on the safe side.
- Go to the Inbound Rules tab and then delete the custom rules you want to remove. However, make sure don’t delete important rules.
- Do the same for outbound rules by going to the Outbound Rules tab. See if this fixes the issue and if not, go to step (4).
- Click on the Action menu and select the Restore Default Policy option and confirm the process.
- Close the window and then check whether the problem is resolved.
7] Reinstall the third-party security suite
If you have installed a third-party security suite and it is not installed correctly or there are some corrupted installation files associated with it, there are chances it might be conflicting with Windows Firewall and thus, causing the issue in hand. In this case, you can try reinstalling the third-party firewall or security suite that you have installed on your system. So, first, uninstall the security suite via the Settings app. Then, reboot your PC and see if the CPU usage of LocalServiceNoNetworkFirewall has slowed down.
You can later download the setup for your security suite from its official website and install it back on your PC.
Why is my CPU usage so high for no reason?
If you have too low RAM and too many resource-hungry apps and software running on your system, it can cause high CPU usage. The high CPU usage on your system can also be a result of malware or virus running on your PC. To resolve this problem, you can try uninstalling unnecessary apps, run Chkdsk, disable Windows Search Indexer, update device drivers, examine the system health report, and run SFC & DISM scans. You can try some more tips to resolve the issue of high CPU usage on your PC.
Localservicenonetwork firewall что это
LocalserviceNoNetworkFirewall is a part of Windows security and is used by Windows Defender (or by other Windows API-based firewalls) in their operations. Usually, this service does not use much CPU or memory.
But the issue arises, when this service starts eating a chunk of memory along with high CPU usage (in some cases, more than 50%) and causes the system to be so sluggish that it becomes impossible to use the system.
High CPU Usage by LocalserviceNoNetworkFirewall
Many things can trigger a high CPU usage by the LocalserviceNoNetworkFirewall but we identified the following chiefly responsible for the issue:
- Conflicting Firewalls: If you are using another firewall (especially, that is using the Windows Defender API) along with the Windows firewall, the two may conflict with each other, resulting in high CPU usage.
- A Large Number of Conflicting Firewall Rules: If an old installation of a 3 rd party firewall has included thousands of inbound/outbound rules, while Windows defender has its own such rules, these conflicting rules may require the firewall to use the excessive CPU to execute all of them.
- Corrupt Installation of 3 rd Party Security Product: If the 3rd party security product like Avast Premium has become corrupt, then this corruption can cause the excessive use of the CPU by the LocalserviceNoNetworkFirewall.
- Corrupt Settings of Windows Firewall: The LocalserviceNoNetworkFirewall service may show a high CPU usage if the Windows firewall settings have become corrupt due to interference from the other security product.
Keep in mind that some of the users may fail to perform the under-mentioned solutions on their systems because the system can be very sluggish. In such a case, you may try the solutions after disconnecting the system from the Internet (either by unplugging the ethernet cable or switching off the router) or try them in the safe mode of your system.
Restart the Windows Firewall
The high CPU usage by the LocalserviceNoNetworkFirewall could be a temporary glitch of the Windows Firewall and restarting the same may solve the problem.
- Right-click Windows and open Task Manager.
Open the Task Manager from the Quick Access Menu - Now head to the Services tab and right-click on WinDefend (Microsoft Defender Antivirus Service).
Restart the Windows Defender Service - Then, in the sub-menu, select Restart and once the service is restarted, check if the CPU usage is back to normal.
Update the PC’s Windows to the Latest Build
The incompatibility between the outdated OS and other system modules (like a driver or a 3 rd party firewall) may cause the high CPU usage by LocalserviceNoNetworkFirewall. Here, updating the PC’s Windows to the latest build may solve the high CPU.
- Click Windows, search, and open the System Settings of Check for Updates.
Open Check for Updates - Now, in the Windows Update, click on Check for Updates.
Check for Windows Updates - If it shows some updates are available, then download and install those updates.
- Once the PC’s Windows is updated to the latest build, check if the high CPU usage by LocalserviceNoNetworkFirewall is normalized.
Disable/ Enable the 3 rd Party Security Firewall and Windows Defender Firewall
If you are using more than one firewall on your system i.e., Windows Firewall and a 3 rd party firewall (like GlassWire), then one may not be working properly with the other due to a glitch and causing the issue. In this context, disabling and enabling both firewalls may solve the problem.
- Right-click on the 3 rd party firewall like GlassWire in the system’s tray and select Exit.
Exit GlassWire from the System’s Tray - Now click Windows and type Windows Defender.
- Then right-click on Windows Defender Firewall with Advanced Security and select Run as Administrator.
Open Windows Defender as Administrator - Now click on Windows Defender Firewall Properties and for the following profiles, set the Firewall State to the off position to disable the Windows Firewall:
Open Windows Defender Firewall Properties - Then apply your changes and close the Windows Defender.
Disable Firewall for All the Profiles of Windows Defender Firewall - Again, open the Windows Defender and enable its Firewall as discussed above.
- Now close the Windows Defender and enable/launch the 3 rd party firewall to check if the LocalserviceNoNetworkFirewall issue is resolved.
Revert the Driver Update
If your system recently got through a driver update, especially, ATI Radeon driver, then that update may conflict with the system’s firewall, and reverting the update may solve the problem.
- Right-click Windows and open Device Manager.
Open Device Manager - Now expand the latest updated device (e.g., Display Adapters) and double-click on the device (e.g., ATI Radeon).
Double-click on Radeon Device in the Device Manager - Now head to the Driver tab and click on Roll Back driver (if applicable).
Roll Back the Radeon Driver - Then follow the prompts to revert the driver update and restart your system.
- Upon restart, check if the high CPU usage is resolved. If so, then you may defer the driver update, till the issue is reported to solve.
Reset the Windows Firewall to its Defaults
Any customization of the Windows firewall (e.g., a newly added inbound or outbound rule) may have caused the overload on the system, thus causing the issue. In such a scenario, resetting the Windows Firewall to its defaults may solve the problem.
- Click Windows, type, and open Windows Security.
Open Windows Security - Now, in the left pane, head to the Firewall & Network Protection.
- Then click on the Restore Windows Firewall to its Defaults.
Restore the Windows Firewall to the Defaults - Now head to the Virus & Threat Protection tab (in the left pane) and under Virus & Threat Protection Settings, click on Manage Settings.
Open Manage Settings Under Virus & Threat Protection Settings - Then open Add or Remove Exclusions under Exclusions.
Click on Add or Remove Exclusions Under Exclusions - Now click on Add an Exclusion and select Folder.
Add a Folder Exclusions in the Windows Security - Then enter the following path in the address bar:
- Now click on Select Folder and close the Windows Security.
Add Windows Defender in the Exclusions of Windows Security - Then restart your PC and upon restart, check if the high CPU usage issue is resolved.
Edit the Cisco Umbrella Settings
Many of the Cisco Umbrella (a cybersecurity product) users reported that this application caused the high CPU usage on their system’s due to a bug. If you are using the Umbrella application, then check if the same is not causing the issue for you. Before proceeding, make sure that you are using the latest version of the Cisco Umbrella client.
Disable IP Layer Enforcement Feature of Cisco Umbrella
- Navigate to the Centralized Settings of the Umbrella Roaming client and open its Advanced Settings.
- Now, in the section of Enable Intelligent Proxy, uncheck Enable IP-Layer Enforcement and click Continue to save your changes.
Uncheck Enable IP-Layer Enforcement in Cisco Umbrella - Now restart your phone and upon restart, check if the High CPU usage issue is resolved.
Disable the Cisco Umbrella Service
- Click Windows and type Services.
- Then, right-click on it and select Run as Administrator.
Open Services as Administrator - Now double-click on the Umbrella service and set its Startup type to Disabled.
Open the Umbrella Client Service - Then click on the Stop button and reboot your PC.
- Upon reboot, check if the High CPU usage is normalized.
- If not, then check if uninstalling the Umbrella client clears out the issue. If so, you may reinstall the client to check if the issue does not return. If it does, then you may contact Cisco support to find the feature triggering the issue.
Delete the Firewall Rules
If there are some firewall rules added to the Windows firewall e.g., from a previous installation of a 3 rd party firewall (like a Trend Micro), whereas the Windows firewall has its own set of similar rules, then that can overload the Windows firewall to execute all the conflicting rules. In such a case, deleting the firewall rules in the Windows firewall may solve the problem.
- Click Windows and type Windows Firewall.
- Then, right-click on Windows Firewall with Advanced Security and select Run as Administrator.
- Now, in the right pane, click on Export Policy and then save the file (just in case…).
Export Policy of the Windows Defender - Then select the Inbound Rules tab and in the right pane, delete the rules you do not want to keep or not required. It may take some time to complete but be careful, do not delete something essential.
- Now repeat the same in the Outbound Rules tab and check if the issue is resolved.
- If that did not work or you do not want to check every rule, then, in the left pane, select Windows Defender Firewall with Advanced Security and expand the Action menu.
- Now select Restore Default Policy and then confirm to restore the policy.
Restore Windows Defender Firewall to Default Policy - Then close the Windows Defender Firewall window and check if the CPU usage issue is resolved.
- If you cannot open the Windows Defender Firewall or its rules cannot be edited, then boot your system into the Safe Mode.
- Now click Windows and type WF.MSC.
- Then right-click on it and select Run as Administrator.
- Now check if repeating steps 4-6 solves the LocalserviceNoNetworkFirewall issue.
Reinstall the 3 rd Party Security Product
If you are using a 3 rd party security product like Avast Premium, its corrupt installation may conflict with the Windows Firewall and thus cause the issue at hand. In such a scenario, reinstalling the 3 rd party security product may solve the problem.
- Right-click Windows and open Apps & Features.
Open Apps & Features - Now click to expand the security product (e.g., Avast) and click on Uninstall.
Uninstall Avast Antivirus - Then follow the prompts to completely uninstall the product and reboot your PC.
- Upon reboot, check if the LocalserviceNoNetworkFirewall issue is resolved.
- If not, then download the security product removal tool from the OEM’s website (like the Avast website) and remove any left-over traces of the security product.
- Now check if the system is not sluggish anymore. If so, then you may reinstall your security product, if it does not cause the issue again.
- If that did not work, then clean boot your PC and check if that resolves the issue. If so, then you may find the problematic application/process/service by one by one re-enabling the ones that were disabled during the clean boot process.
Edit the System’s Registry
If nothing has worked for you so far, then editing the Windows Defender-related registry values may solve the problem.
Warning: Proceed at your own risk as editing the PC’s registry is a skillful task and if not done right, you may cause everlasting damage to your data/system.
- Firstly, to be safe, create a backup of the system’s registry.
- Now click Windows, type, and open Notepad.
Open Notepad - Then copy and paste the following in the Notepad:
- Then expand the File menu and click Save.
Save the File with .reg Extension - Now select a location to save the file, preferably on the desktop of your system, and enter the name for the file with .reg extension e.g., MpsSvc.reg.
- Then close the Registry Editor and right-click on the above-mentioned file (e.g., MpsSvc.reg).
- Now select Merge and then confirm to merge the registry keys.
Merge the Registry Key to the Registry - Then restart your system and upon restart, hopefully, the CPU will not be throttling.
If nothing works, then you may perform a clean installation of Windows to get rid of the high CPU usage by LocalserviceNoNetworkFirewall.
Localservicenonetwork firewall что это
Мелкософтовскую поддержку спрашивать бессмысленно, спрошу тут, так как вероятность того, что конфигурации Windows примерно совпадают, и у кого-то возник подобный issue, довольно велика.
Итак, система Windows 8.1, VS2013+VS2015, Hyper-V, естественно. Проблема возникла во второй раз (на прошедшей неделе возникло то-же самое, но на рабочем PC; там «решить» проблему удалось полной переисталляцией Windows 10 и всего остального с «нуля», но на домашней рабочей станции этого очень бы хотелось избежать!)
Началось все вчера, после инсталляции порции windows updates (на рабочем PC было то-же самое, но апдейты устанавливались автоматически, а дома я собственными руками разрешил MS «убить» систему 🙁 С другой стороны, какой у нас еще есть выход?! (вопрос риторический)).
После рестарта, резко замедлилось открытие сайтов; как и на рабочем PC, «виновник» — процесс svchost.exe группы сервисов LocalServiceNoNetwork, а точнее, MpsSvc (сервис Windows Firewall), «отъевший» 650MB RAM из-за memory leak-а и висящий на треде в ожидании (видимо, в говнокоде этого треда индусский баг и сидит) — конечный endpoint ntdll.dll!NtDeviceIoControlFile+0xa.
Как и на рабочем PC, сначала я заподозрил руткит или троян, но сканирование всевозможными антивирусами и антируткитами ни тогда, ни вчера на домашнем PC, ничего не выявило. Видимо, в случае Windows руткиты и не нужны — MS справляется с работой самостоятельно. Не помогают ни откат на предыдущий restore point, ни даже рестарт в «Safe mode with network» (sic!).
Отключение сервиса firewall-а решает проблему «замедленного интернета», но:
— становится невозможной инсталляция приложений из магазина (да и Бог с ними), но..
— прекаращает работу XAML designer в Visual Studio, равно как и Blend 🙁 — вот это очень существенно!
Какого . редактору XAML нужен Windows Firewall — Бог его знает! Вот что пишет:
System.Exception
The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again.
error 0x80073D0A: Failed to install package App.aff9eef24.ae049.a409a.aa96f.ae8c0a6054050_1.0.0.0_x86_NorthAmerica_8wekyb3d8bbwe because the firewall service is not running. Ensure that the firewall service is enabled and started.
На работе переинсталляция с «нуля» заняла около дня, но там только две VS «с обвязкой» + Office + плюс тройка корпоративных приложений; дома дело обстоит куда хуже 🙁 Да, «вареза» у меня нет вообще; большая часть бесплатных программ — с открытым кодом (как Far Manager или Miranda NG). Из «подозрительных» установлен только Punto Switcher, про который, после того, как Yandex купил его у разработчика, ходит много темных слухов. С другой стороны, последний раз он апдейтился больше года назад, и никаких side effects за ним замечено не было. Более того, до вчерашних windows updates, все работало «как часы».
Собственно, вопрос: у кого-нибудь подобное наблюдается/наблюдалось? Не надеюсь на то, что кто-то предложит рабочее решение (на работе «убил» день, пробуя всевозможные дебильные «советы» индусских MS MVP, самым «дельным» из которых оказался «reinstall everything from the scratch»). Просто, чтобы хоть чуток успокоить душу относительно сверх-скрытных руткитов от FBI/ФСБ.
эмулятор вин моб 10 запускается? можешь создать еще одного юзера и залогиниться?
Сообщение отредактировал ixorek — 01.11.15, 18:09
ixorek, ты имеешь ввиду, с отключенным firewall-ом или с включенным (с багом)? С отключенным запускается, отладка идет, все штатно, за исключением XAML редактора. С включенным сервисом, запускается, но VS не может к нему подключиться (таймаут срабатывает).
P.S. Ты апдейты последние, которые помечены как optional, для Windows 8.1 x64, у себя устанавливал?
[UPDATE] Пока возил дочку на плаванье, за полтора часа после рестарта фаервол «восстановился» частично:
— сервис, хоть и «отожрал» 529 MB памяти, перестал «съедать» процессорное время (после перезагрузки «жрет» 13% — это на 8-ядерном i7!)
— XAML редактор в VS открывается (равно как и Blend)
— скорость открытия сайтов (вернее, DNS resolution) восстановилась, стала быстрой, какой и должна быть
— апплет «Windows Firewall» Control Panel стал запускаться
Что работает с ошибкой: «Advanced settings» из апплета Control Panel-и «WIndows firewall» (т.е. mmc.exe с соответствующими snap-in-ами), при попытке показа ‘Inbound rules» или «Outbound rules» крэшится (правда, успевая вывести часть правил).
а, у тебя вин 8.1, у меня была похожая по симптомам война на вин 10. если в кратце, если будешь делать апгрейд до 10ки, делай чистую инсталяцию, при апгрейде там что то рушится и некоторые вещи перестают работать, отвалившийся XAML designer, это самое маленькое зло.
когда в винде все плохо, нужно попробовать создать еще один чистый акаунт и попробовать в нем, так вот 10ка у меня самоубилась до состояния нельзя создать новый акаунт
Сообщение отредактировал ixorek — 01.11.15, 21:23
[UPDATE 2] Победил-таки проблему! Как я писал выше, после часа «торможения» firewall «попустило», что даже апплет стал открываться. Что я сделал — выполнил «reset to defaults», очистивший все правила, перегрузился и — о, чудо! — все заработало опять, как и раньше. Видимо, один из последних апдейтов (то-ли секьюрити апдейт, то-ли windows) добавил новые правила, вступившие в «интерференцию» с текущими. Но сложно сказать что-то точнее.