NLM Errors in the Windows SCCM Client


1.    Stop the windows update service, rename or delete the Software Distribution folder (%windir%\softwareDistribution) and start windows update service. This approach provides a fresh start with a new Windows Update data store if the Datastore.edb file is corrupted.
2.    Open Windows update log file under path C:\Windows\WindowsUpdate.log and check latest logs especially NLM error.
3.    Download below KB article from Microsoft catalog site. KB2919355 or you can download the the patches from the below link.
4.    Uninstall all patches(KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, KB2934018, KB2919442) if it is installed and restart server
5.    Install KB2919355 now on server and restart server again.
6.    Restart the windows update service, Go to control panel, open configuration manager, Go to Actions tab and trigger software update scan cycle and software update deployment evaluation cycle & check the logs.
7.    Wait for 15-30 Minutes, fresh bunch of patches will be available in software center.

Logs that can be used in for Troubleshooting :

  • locationservices.log =>This log is used to check the correct software update point has been detected by the client , to check the management point and distribution point entries.
  • wuahander.log => when the software update scan cycle initiated, Windows update agent will contact WSUS for scanning and if is successful,a state message will be sent to site server confirming that,software update scan is completed successfully which can be seen from this log.
  • windowsupdate.log => If Software update scan is not successful then,you should look at this log for more information. This log Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.
  • Updatesdeployment.log => This log shows the number of updates and deployments being targeted to a machine.
  • Updatesstore.log =>Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle .
  • Rebootcoordinator.log =>Provides information about the process for coordinating system restarts on client computers after software update installations.

Popular posts from this blog

How to reset the IE settings Through command Line (CMD)

Running CLI Commands in ESXi using plink software