Fix it now
These two codes are unrelated in mechanism and get filed together because they arrive together. 0x8024001E is WU_E_SERVICE_STOP – the operation did not complete because the service or system was being shut down. 0x80243004 is WU_E_TRAYICON_FAILURE, a failure creating an icon in the notification area. Only one of them is about updates failing.
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
- Ask first whether the machine was shut down, restarted or put to sleep during the scan. A single 0x8024001E with an obvious cause needs nothing beyond running the scan again.
- Run the scan manually while signed in – Settings, Windows Update, Check for updates – and leave the machine alone until it finishes.
- If it fails again, run the two commands above in that order. Microsoft documents DISM first because it repairs the component store that SFC then uses as its source.
- Restart, then scan again and note whether the code changes. A different code after the repair is progress.
- If you are on a server or Server Core and updates are actually installing, treat 0x80243004 and 0x80243FFF as cosmetic and stop chasing them.
If DISM cannot reach Windows Update, give it a source: DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\server\c$\windows /LimitAccess.
If the scan completes and updates install, you are done. If not, the next section separates the three families these six codes belong to.
Why it happens
There are three different things in this code list and treating them as one failure is why they are hard to clear. One is an operation that was interrupted. One is the Automatic Updates user interface failing. One is stored results the client could not read back. Only the first has anything to do with an update not installing.
0x8024001E is WU_E_SERVICE_STOP: the operation did not complete because the service or system was being shut down. It is a statement about timing, not damage. Something stopped the service or the machine while work was in flight – a restart, a sleep transition, a maintenance script that cycles services, or a management tool doing its rounds. A single occurrence around a known restart is not a fault at all.
0x80243004 and 0x80243FFF are the interface family. The first is WU_E_TRAYICON_FAILURE, a failure creating an icon in the taskbar notification area; the second is WU_E_AUCLIENT_UNEXPECTED, a user interface error not covered by another WU_E_AUCLIENT_* code. On a server, on Server Core, or in any session with no desktop, an attempt to create a notification icon has nowhere to go. If updates are installing, these are noise.
0x80243001 is the odd one and it is worth knowing: WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION means the download and installation results could not be read from the registry because of an unrecognised data format version. The update may well have installed; what failed was reading back what happened.
Two codes in this list – 0x80245006 and 0x8024CC0E – have no published meaning at all. Microsoft’s redirector range documents 0x80245001, 0x80245002, 0x80245003 and 0x80245FFF, and the driver utility range ends at WU_E_DRV_UNEXPECTED 0x8024CFFF. Neither of the two in between is published. Earlier versions of this article gave them meanings; those meanings had no source and are gone.
Something is stopping the service while it works
You have this one if 0x8024001E repeats predictably, and the System log shows the update service stopping at around the same time each day.
- Open Event Viewer, Windows Logs, System and look for Service Control Manager entries showing
wuauservstopping. - Look for scheduled tasks or management scripts that cycle update services as a maintenance routine, and stop them running during scan windows.
- Check power settings under Settings, System, Power so an unattended machine is not sleeping mid-scan.
- Rerun the scan and let it complete without interruption.
The update client’s own files are damaged
You have this one if The failure happens immediately on every attempt, including a manual scan on a machine nobody is touching.
- Run
DISM.exe /Online /Cleanup-image /Restorehealth, thensfc /scannow, then restart. That order is Microsoft’s, and it matters: SFC repairs from the store that DISM has just repaired. - Where the machine has no working update path, supply the source with
/Source:and/LimitAccess. - Rescan and read the code again rather than assuming the repair fixed it.
Re-registering wuapi.dll, wuaueng.dll, wups.dll and wups2.dll with regsvr32 is widely repeated and is not Microsoft’s published repair for current builds. DISM and SFC are.
Interface codes on a machine with no desktop
You have this one if 0x80243004 or 0x80243FFF on a server, on Server Core, or on a machine used only as a remote host.
- Check whether updates are actually installing. If they are, these codes are cosmetic and there is nothing to fix.
- Drive updates from PowerShell or your management tooling rather than expecting the notification path to work in a session that has none.
- If updates genuinely are not installing, look for a real cause elsewhere and stop attributing it to the icon.
Results are written but cannot be read back
You have this one if 0x80243001, and update history looks wrong or incomplete while the updates themselves appear installed.
- Confirm what is actually installed with
Get-HotFixrather than trusting the history view. - Stop the Windows Update service, rename
C:\Windows\SoftwareDistribution, and start it again so the store is rebuilt in the current format. - Rescan. History starts empty afterwards, which is expected.
Something in the path is answering instead of the service
You have this one if Failures only from one network, only behind one proxy, or only on machines that pass through an inspecting appliance.
- Check the proxy the system account uses, which is not the one in your browser:
netsh winhttp show proxy. - Clear a stale system proxy with
netsh winhttp reset proxy, or set the right one withnetsh winhttp set proxy. - Exempt the Windows Update host names from TLS inspection and captive portal interception.
- Run
Get-WindowsUpdateLogand read what the client was actually returned rather than inferring it from the code.
Full reference
What each code in the list is
| Code | Family | Published meaning |
|---|---|---|
0x8024001E |
Interruption | WU_E_SERVICE_STOP: the service or system was being shut down |
0x80243004 |
Interface | WU_E_TRAYICON_FAILURE: could not create a notification area icon |
0x80243FFF |
Interface | WU_E_AUCLIENT_UNEXPECTED: a UI error no other AUCLIENT code covers |
0x80243001 |
Results | WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION: results unreadable, unrecognised format version |
0x80245006 |
Unpublished | No acceptable source states a meaning |
0x8024CC0E |
Unpublished | No acceptable source states a meaning |
Telling an interruption from a real fault
| Pattern | What it usually means |
|---|---|
| Once, around a restart or a sleep | A genuine interruption; rerun the scan |
| Every time at roughly the same point | Something is stopping the service on a schedule |
| Only on servers or Server Core | Interface codes in a session with no desktop |
| Only behind one proxy | Something in the path, not the client |
| Started when an endpoint agent was deployed | The agent is acting on update components |
Getting a readable log
Get-WindowsUpdateLog merges the client’s ETW traces into a static WindowsUpdate.log, written to C:\Windows\Logs\WindowsUpdate. It is a snapshot: it does not keep updating the way the old text log did, so run it again after each attempt. Read the entries immediately before the failure rather than searching for the code itself, because the code is the summary and the line above it is usually the reason.
When an endpoint agent is involved
- Check the product’s quarantine and blocking history for entries naming Windows servicing binaries or the
SoftwareDistributionfolder. - Apply the exclusions the vendor documents for Windows servicing rather than inventing your own.
- Test with protection paused only if your policy allows it, and put it back.
- If the product is misidentifying system components, report it rather than leaving a permanent exclusion in place.
Supporting services worth checking
The update client does not work alone. Confirm the Background Intelligent Transfer Service and the Cryptographic Services are running and not disabled, and that the Update Orchestrator service has not been disabled by a tuning script. A client that appears to abort immediately is sometimes a client whose dependencies were switched off by something that promised to make the machine faster.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x8024001E |
WU_E_SERVICE_STOP: the operation did not complete because the service or system was being shut down | Microsoft Learn |
0x80243004 |
WU_E_TRAYICON_FAILURE: a failure occurred creating an icon in the taskbar notification area | Microsoft Learn |
0x80245006 |
Seen while the client selects an update service; no acceptable source publishes a meaning, and the documented redirector codes are 0x80245001 to 0x80245003 and 0x80245FFF | not published by the vendor |
0x8024CC0E |
Seen in driver-related update operations; no acceptable source publishes a meaning, and the documented driver range ends at 0x8024CFFF | not published by the vendor |
0x80243FFF |
WU_E_AUCLIENT_UNEXPECTED: a user interface error not covered by another WU_E_AUCLIENT_* code | Microsoft Learn |
0x80243001 |
WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION: results could not be read from the registry because of an unrecognised data format version | Microsoft Learn |
Confirm the fix worked
- A manual scan completes without an abort code.
- Pending updates install and appear in
Get-HotFixwith a current date. - Event Viewer, Windows Logs, System no longer shows the update service stopping unexpectedly.
- One scheduled scan runs to completion with nobody watching it.
- On a server, updates install even though the interface codes may still appear, which is the expected outcome rather than a remaining fault.
Questions people ask about this
Is my Windows installation damaged?
Usually not. 0x8024001E is a timing statement – the service or the system was shutting down – and a single occurrence around a restart needs nothing but a rerun. Run DISM and SFC only if it repeats on a machine nobody is touching.
Should I worry about the interface codes on a server?
Not if updates are installing. 0x80243004 is a failure to create a notification area icon and 0x80243FFF is a general Automatic Updates interface error. In a session with no desktop there is nowhere to draw one.
What do 0x80245006 and 0x8024CC0E mean?
Nothing that any acceptable source publishes. Microsoft documents the neighbouring codes in both ranges but not these two. Diagnose them from the log and treat any confident explanation you find elsewhere with suspicion.
Does fixing this cost money?
No. Every step here is a built-in command, a service check or a log read. No code in this article relates to licensing.
Why not re-register the update DLLs?
Because Microsoft’s published repair for a damaged update client is DISM /RestoreHealth followed by sfc /scannow. The regsvr32 list circulates widely, is not published for current builds, and the file set differs between them.
