For WU issues, the Event Name is “WindowsUpdateFailure3” and typically paired with a fault bucket of type 5. Bobcares, as a part of our Windows Hosting Support offers solutions to every query that comes our way.

What is Event Name “WindowsUpdateFailure3?”

When we see a “WindowsUpdateFailure3,” the first place to look is the Application event log for events that have the “Information” level and Event ID 10001. WU issues often have an associated fault bucket of type 5 and are identified by the Event Name “WindowsUpdateFailure3”. We should use those codes in the Web searches to find the exact cause of the issue.

If none of the general steps given below work, or if we just want to reset Windows Update without doing too much debugging, then they should fix about 90% of Windows Update errors. This should work with Windows 7, 8, 8.1, 10, and most variations.

1. Confirm that the Windows Firewall service is enabled and setup to run automatically. The service must be working, but it need not be activated. It’s simple to check for, and if it’s not operating, we probably have WUS problems.

2. Turn off the BITS services. Make sure the Windows Update service didn’t restart itself by refreshing the view of the services (F5 if using the Services MMC) after stopping it. If so, give it another stop.

3. To restart the Windows Update download process, remove the C:\Windows\SoftwareDistribution folder.

4. Purge C:\ProgramData\Microsoft\Network\Downloader of all files.

5. Give the system a restart. Start the BITS service first, then the Windows Update service, and it should still function if we are in a situation where we are unable to restart the computer.

6. Although some faulty files were found, Windows Resource Protection was unable to repair them. The CBS.Log windir\Logs\CBS\CBS.log contains data. C:\Windows\Logs\CBS\CBS.log is one example.

Troubleshooting

1. Download SFCFix and save it to the desktop.

2. Save any work and close all programs.

3. Download the attachment SFCFix.zip and save it to the desktop.

4. Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

5. SFCFix will launch and complete its process.

6. Once done, a file named SFCFix.txt will appear on the desktop. Post this logfile as an attachment in the next reply.

7. Run the System File Checker by opening Command Prompt as an administrator.

8. Type SFC /Scannow and press Enter.

9. Wait for the scan to complete. If it fails, attach a new copy of the CBS log.

10. Run DISM RestoreHealth by opening Command Prompt as an administrator.

11. Type DISM /online /cleanup-image /RestoreHealth and press Enter.

12. Open the Network Troubleshooter by pressing the Windows key, typing “Network problems,” and selecting “Identify and repair network problems.”

13. Follow the steps in the wizard to diagnose and resolve the network problems.

14. Open Command Prompt as an administrator by clicking on Start menu, typing “cmd,” right-clicking on it, and selecting “Run as administrator.”

15. Copy and paste each of the following commands one by one and press Enter after each:

16. Restart the computer.

17. After the restart, run the Windows Updates again.

[Need to know more? Get in touch with us if you have any further inquiries.]

Conclusion

To sum up, our Support team went over the details to fix Event Name “WindowsUpdateFailure3.”