In this article, we shall discuss the fix to Windows Update Fails with Error 0x80092004 (Windows Update Logs in Windows: 2023-KB5022498 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 failed)”. We can unravel more information from the Windows Event Log. Windows Events provides a standard, centralized way for applications (and the operating system) to record important software and hardware events. Please see how to Fix the Port used for the Virtualhost is not an Apache Listen Port, and how to Create a Child and Tree Domain.
Note: This error can be especially frustrating for users who have recently provisioned their PCs or are trying to upgrade their machines. These updates play a crucial role in maintaining the system, as they fix specific bugs and vulnerabilities within the operating system.
Without these updates, unresolved issues may lead to further complications and could significantly impact the machine’s performance and security.
Note: Starting with Windows 10 build 9926, Windows Update logs are no longer saved to “%windir%\Windowsupdate.log”. Windows Update client now uses Event Tracing for Windows (ETW) to generate diagnostic logs saved as .etl files in the “%windir%\Logs\WindowsUpdate” folder. This method improves performance and reduces disk space usage. However, the logs are not immediately readable as written.
As discussed above, the Windows Event Log is go to for a quick investigation into AU installations, pending installations, or client reboots. The installer writes entries such as following:
- Detection of corrupted configuration data.
- Success or failure of the installation; removal or repair of a product.
- Errors that occur during product configuration.
You may be interested in these articles: How to install, upgrade and uninstall Chocolatey, how to install, upgrade and uninstall software with Chocolatey, and how to install applications with Winget CLI on Windows.
Detect Windows Update Failure with Error 0x80092004
Use your Event log file to filter by “source” to display only one of the three event sources at a time. When filtering by Windows Update Agent. You will likely see many events about the successful installation of updates and whether those updates required a reboot.
The AU client logs everything to the System Event log as we can see from the image below. To read Windows Update event logs in Event Viewer. Please launch the Windows Event Viewer.
Note this issue occurred across multiple machines in my lab environment. The same updates deploy fine to other machines with the same OS and applications.
Also, from the Event Viewer, under the Application and Services Logs\Microsoft\Windows\WindowsUpdateClient. In the left pane, navigate to the location below, and open the Operational log.
Applications and Service Logs\Microsoft\Windows\WindowsUpdateClient
You can now select event logs in the middle pane of Event Viewer to see their details.
Error messages from log
- The description for Event ID 26 from source Microsoft-Windows-WindowsUpdateClient cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
- The description for Event ID 41 from source Microsoft-Windows-WindowsUpdateClient cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Please see How to find out who restarted Windows Server, and the Various methods to Install .NET Framework in Windows. Also, see how to Check .NET Framework version on Windows.
Reasons for Windows Update 0x80092004 Error
1: This error occurs on newly provisioned devices as it is the case for me. Microsoft recommends the February 14, 2023 update for Windows 10 versions 20H2, 21H2, and 22H2, which includes cumulative reliability improvements for .NET Framework 3.5 and 4.8.1.
Microsoft recommends fulfilling the prerequisites as discussed in this blogpost by Microsoft.
2: Also, NetFramework 4.8 and 4.8.1 have separate updates which Microsoft has combined into a double update (KB5022729). Since this has already failed before, we have already separated this into individual updates (KB5022502 and KB5022498) and found that it fails on the 4.8.1 part.
The error indicates a missing signed file component from the core .NET Framework 4.8.1 installation. PCs that previously received the full .NET Framework 4.8.1 updates do not encounter this issue.
Please see how to Install and Manage Applications with Winget, how to install Windows Package Manager (Winget CLI), and Windows App Package: How to Bundle MSIX packages.
Prerequisites/Recommendation
You must have .NET Framework 3.5 or 4.8.1 installed to apply this update. Restart your PC after applying the update if any affected files are in use. We recommend exiting all .NET Framework-based applications before applying the update.
You can now install .NET updates using the Windows Package Manager CLI (winget) as well. This update (kb5022498) provides security improvement for CVE-2023-21808 (.NET Framework Remote Code Execution Vulnerability), and CVE-2023-21722 (.NET Framework Denial of Service Vulnerability).
Note: There are tons of recommendations online such as to have the Windows Update Components repaired, and to run the System File Checker and DISM etc. For me, I did not try any of these. I took a look at the reference Microsoft documentation I shared above and installed the necessary .Net Framework prerequisites. And was able to install the latest Windows Updates.
I hope you found this article on “How to fix Windows Update Fails with Error 0x80092004′ useful. Please feel free to leave a comment below.
