Skip to content

Commit 48736e8

Browse files
committed
AB#7617: Troubleshoot Windows Update Error 0x8024001E
New article for [CI 7617](https://dev.azure.com/KMOps/ContentExperience/_queries/edit/7617)
1 parent 83db0e3 commit 48736e8

1 file changed

Lines changed: 124 additions & 0 deletions

File tree

Lines changed: 124 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,124 @@
1+
---
2+
title: Troubleshoot Windows Update Error 0x8024001E
3+
description: Learn how to fix Windows Update error 0x8024001E on Windows Client computers or Azure Windows VMs.
4+
ms.date: 11/26/2024
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, dougking, v-appelgatet
9+
ms.custom:
10+
- sap:windows servicing, updates and features on demand\windows update - install errors unknown or code not listed
11+
- pcy:WinComm Devices Deploy
12+
appliesto:
13+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
14+
- ✅ <a href=https://learn.microsoft.com/lifecycle/products/azure-virtual-machine target=_blank>Supported versions of Azure Virtual Machine</a>
15+
---
16+
17+
# Troubleshoot Windows Update error 0x8024001E
18+
19+
This article describes how to troubleshoot Windows Update error code 0x8024001E. Several issues can cause this error, so this article describes how to identify some of the specific causes.
20+
21+
## Symptoms
22+
23+
You install a Windows update, but the installation fails and you see error code 0x8024001E. You might see additional symptoms as well. Review the following list of symptoms to see if they apply to your issue. If so, they might provide insight into the cause of your specific issue.
24+
25+
- [Symptom 1: Security update doesn't install](#symptom-1-security-update-doesnt-install)
26+
- [Symptom 2: An unexpected system restart disrupts installation](#symptom-2-an-unexpected-system-restart-disrupts-installation)
27+
- [Symptom 3: A scheduled task disrupts installation](#symptom-3-a-scheduled-task-disrupts-installation)
28+
- [Symptom 4: Windows Server Update Service (WSUS) issue, and secondary error code 0x800f0821](#symptom-4-windows-server-update-service-wsus-issue-and-secondary-error-code-0x800f0821)
29+
30+
### Symptom 1: Security update doesn't install
31+
32+
If the update that you tried to install is a security update, check the UpdateSessionOrchestrator logs located in C:\ProgramData\USOShared\Logs\System. Look for entries that resemble the following example:
33+
34+
```output
35+
*Error Originate:DownloadHandler::UpdateDownloadResult:1893* -> [hr] : -2145124322 (0x8024001E);
36+
*Download finished* -> [Results] : {85604fae-a5c5-4f6d-9012-3d86be1bccce}:2021-01 Update for Windows Server 2016 for x64-based Systems (KB4589210):hr=0x8024001e;
37+
*Error Originate:DownloadHandler::UpdateDownloadResult:1893* -> [hr] : -2145124322 (0x8024001E);
38+
*Download finished* -> [Results] : {abd74871-ea87-49aa-b3fe-866aca9b23f2}:2021-03 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5000803):hr=0x8024001e;
39+
```
40+
41+
### Symptom 2: An unexpected system restart disrupts installation
42+
43+
If the computer or virtual machine (VM) restarts before the update finishes installing, the update might not install correctly. To see if this issue occurred, check the CBS logs. Look for entries that resemble the following example:
44+
45+
```output
46+
Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
47+
Info CBS TiWorker signaled for shutdown, going to exit.
48+
Info CBS CbsCoreFinalize: ExecutionEngineFinalize
49+
Info CBS Execution Engine Finalize
50+
```
51+
52+
### Symptom 3: A scheduled task disrupts installation
53+
54+
To see if this issue occurred, use Event Viewer to review the Microsoft-Windows-TaskScheduler/Operational event log. Look for sequences of events that resemble the following examples:
55+
56+
```output
57+
Information 104 Microsoft-Windows-TaskSchedu1er Task registration NT AUTHORITY\SYSTEM User "NT AUTHORITY\SYSTEM" updated Task Scheduler task "\Microsoft\Windows\WindowsUpdate\Schedu1ed start"
58+
Information 201 Microsoft-Windows-TaskSchedu1er Action completed NT AUTHORITY\SYSTEM Task Scheduler successfully completed task "\Check WSUS Reg" instance "{EE5B1773-676A-4E12-9ee6-12727FA2CAD9}" action "C:\windows\system32\cmd.exe" with return code 0.
59+
Information 102 Microsoft-Windows-TaskSchedu1er Task completed NT AUTHORITY\SYSTEM Task Scheduler successfully finished "{EE5B1773-676A-4E12-90Ø6-12727FA2CAD9}" instance of the "\Check WSUS Reg" task for user "NT AUTHORITY\SYSTEM".
60+
```
61+
62+
Use this event information to identify which scheduled task interfered with the update installation.
63+
64+
### Symptom 4: Windows Server Update Service (WSUS) issue, and secondary error code 0x800f0821
65+
66+
In WSUS environments, a WSUS issue might prevent an update from installing and generate error code 0x8024001E and a secondary error code (0x800f0821). To see if this issue occurred, use Event Viewer to review the System event logs. Look for sequences of events that resemble the following examples:
67+
68+
```output
69+
Error Installation Failure: Windows failed to install the following update with error 0x8024001E: 2023-11 Cumulative Update for Windows
70+
Information The Windows Update service entered the stopped state.
71+
Information The Windows Update service entered the running state.
72+
```
73+
74+
## Cause
75+
76+
The following conditions can cause error code 0x8024001E:
77+
78+
- The update source files on the computer might be corrupted or incomplete.
79+
- The computer might not have enough available disk space to install the update.
80+
- Intermittent connectivity might disrupt the update process.
81+
- Server maintenance, scheduled tasks, or other server outages might disrupt the update process.
82+
83+
## Resolution
84+
85+
> [!IMPORTANT]
86+
> Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
87+
88+
Follow these steps:
89+
90+
1. If you identify a scheduled task that disrupts the update, disable that scheduled task.
91+
1. If you're using WSUS, make sure that WSUS is working correctly. For more information about managing WSUS, see [Windows Server Update Services best practices](../mem/configmgr/update-management/windows-server-update-services-best-practices.md).
92+
1. Make sure that the C:/ drive has at least 10-15 GB of free space.
93+
1. Rename the software distribution folder. Open a Windows Command Prompt window, and then run the following commands:
94+
95+
```console
96+
net stop wuauserv
97+
rename c:\windows\SoftwareDistribution softwaredistribution.old
98+
net start wuauserv
99+
```
100+
101+
1. Restart the following services:
102+
103+
- Windows Update service (WUAServ) (if you didn't already restart it)
104+
- Update Orchestrator Service for Windows Update service (UsoSvc)
105+
- Background Intelligent Transfer Service (BITS)
106+
107+
1. Try again to install the update. Use one of the following methods:
108+
109+
- Open **Windows Settings**, and select **Windows Update**. Follow the prompts to check for and install updates.
110+
- Manually download updates from [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/). At the command prompt, run the following commands:
111+
112+
```console
113+
expand -f:*x64.cab c:\temp\filename.msu c:\temp
114+
dism /online /add-package /packagepath:c:\temp\Windows10-KB***-x64.cab
115+
```
116+
117+
> [!IMPORTANT]
118+
> Make sure that the computer or VM doesn't restart during the update process except when the update process requires a restart.
119+
120+
If the issue persists, contact Microsoft Support.
121+
122+
**Partial Use of AI disclaimer**
123+
124+
Certain sections of this document have been generated or enhanced using artificial intelligence (AI) technology.

0 commit comments

Comments
 (0)