Given an example WU log, follow these steps to diagnose the issue:
1. Filter the log on “FAILED” (case-sensitive) and pipe/redirect those lines to a separate file. This could be done in Powershell as in this example:
Select-String -Path "*.log" -Pattern "FAILED" -CaseSensitive > failures.txt
One other tool that can also be used for viewing Windows Update logs and filtering them is CMTrace, which is part of the Microsoft System Center 2012 R2 Configuration Manager:
Under the Tool menu, you will find a filtering option.
2) Results look something like this:
3) First focus on the most frequently occurring error codes between the brackets then the least frequent. Also notice that all the error codes are in the same column so it’s easy to identify which ones occur more frequently.
In this case, the 2 most frequently occurring errors are 8024000C and 80246013.
4) Perform a Google search on the error codes and prioritize solution with Microsoft website recommendations first, then preview others high on the hit list. You can also reference Microsoft’s Error Code list here for a general description of the error:
In this case by performing a simple Google search, we find that these are the most likely issues based on the search results:
8024000C: WUA corruption or issues with the system
80246013: Issue with Background Intelligent Transfer Service and corrupt data as well as permissions issue, which doesn’t allow the update to install itself.
5) It is also often recommended to run the Windows Update Troubleshooter:
This tool can often diagnose the issue and sometimes even resolve the issue(s).
Here’s an example of the Windows Update Troubleshooter finding and fixing 3 issues on a Windows 8.1 system:
Other Helpful References
- How to read the WindowsUpdate.log file:
- How to view the WindowsUpdate.log on Windows 10:
- Understanding the WindowsUpdate.log file for Advanced Users:
- Troubleshoot problems with the Windows Update Client:
- Microsoft TechNet script for Resetting Windows Update Agent:
The interface looks like this when you run it (choose option 2 to reset WU components):