N-central Troubleshooting
Resource usage spikes and slow response caused by svchost.exe
Last Modified
Tue Jun 18 20:07 GMT 2019
Description
- This article addresses usage spikes and slow response in N-able N-central after installing the agent.
Environment
- N-able N-central
Solution
- These issues are related to a problem in te Windows Update API found in mid-2015, which was not fixed until the November 2015 release of the Windows Update Agent.
- Due to the way that this break affects our Patch Management, our product cannot detect nor apply these as needed, until N-able N-central 10.2 SP1 (10.2.1.268).
- If there are resource usage spikes during asset scans and/or patch detection scans, verify that the devices' Windows Update Agents are as up to date as possible, ideally newer than December 2015's release.
- Please note that we have not seen newer versions of the Windows Update Agent for older Operating Systems such as SBS, Server 2003 and Server 2008.
- Please also refer to the minimum requirements for usingN-able N-central Patch Management: MSP N-able N-central Patch Management: Windows Update Agent version and OS Requirements
- Note: You may be able to use a script or amp to call wusa.exe if you are running an older version of N-able N-central. More information about this executable can be found in Description of the Windows Update Standalone Installer in Windows.