- Software and systems
- Operating system
0x80240002
Windows Update 0x80240002: WU_E_MAX_CAPACITY_REACHED
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
Microsoft defines 0x80240002 as: The maximum capacity of the update service was exceeded. Do not reset Windows Update from the code alone. First preserve the failed KB, update source and time, then discriminate one update versus every update, an active installer or restart, and whether the same state persists after one reboot.
Safety first
Stop and check this first
- Do not interrupt an active installer or repeatedly power-cycle the device.
Safe checks you can perform
- Preserve the failed update before changing state
- Run one controlled discriminator
- Stop before the generic reset loop
Leave these tasks to a qualified professional
- Do not attempt this professional task: Evidence-led Windows Update handoff for 0x80240002
What a technician must be able to justify
A technician is coming
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Evidence-led Windows Update handoff for 0x80240002
What they doMap the failing KB set, reboot-pending markers, installer ownership and server responses in WindowsUpdate.log before clearing queues or caches.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Preserve the failed update before changing state
In Settings > Windows Update > Update history, record the exact KB/title, 0x80240002, timestamp, Windows edition/build, restart-pending state and whether the source is Microsoft Update, WSUS or another managed service.
Do not interrupt an active installer or repeatedly power-cycle the device.
Evidence: Windows Update error reference
Run one controlled discriminator
Let the visible update or installer finish, restart once if Windows requests it, then retry only the named KB. Record whether the failure affects one item or the whole scan.
Do not interrupt an active installer or repeatedly power-cycle the device.
Evidence: Windows Update error reference
Stop before the generic reset loop
A cleared transient state is complete. The same state after reboot needs the owning operation, server response or restart-pending evidence; repeated retries add no diagnosis.
Do not interrupt an active installer or repeatedly power-cycle the device.
Evidence: Windows Update error reference
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and systems
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x80240002
- Windows Update 0x80240002
- WU_E_MAX_CAPACITY_REACHED
What it means
WU_E_MAX_CAPACITY_REACHED is the Windows Update Agent result for this condition: The maximum capacity of the update service was exceeded. The useful boundary is one update versus every update, an active installer or restart, and whether the same state persists after one reboot. Before paid repair or a managed-IT change, require this evidence: Map the failing KB set, reboot-pending markers, installer ownership and server responses in WindowsUpdate.log before clearing queues or caches.
Warnings and stop conditions
- Lowsource verified
Do not interrupt an active installer or repeatedly power-cycle the device.
Evidence: Windows Update error reference
Symptoms and causes
Probable causes · in order
- What the Microsoft code establishesConfirmed
Microsoft’s Windows Update reference maps 0x80240002 to WU_E_MAX_CAPACITY_REACHED: The maximum capacity of the update service was exceeded.
Evidence: Windows Update error reference
- The observation that changes the next branchPossible
Discriminate one update versus every update, an active installer or restart, and whether the same state persists after one reboot. A cleared transient state is complete. The same state after reboot needs the owning operation, server response or restart-pending evidence; repeated retries add no diagnosis.
Evidence: Windows Update error reference
Virtual technician
Does 0x80240002 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Windows Update error reference
Microsoft · 2026 · official_doc
Was this entry useful?