## TL;DR
0x80240034 means the download finished but the update is waiting on a stuck state, often a duplicate or superseded entry in the local datastore or an earlier operation that never closed. Restart the update services, clear the download cache, check for a pending restart that must clear first, and let the agent re-detect.

```text
windows update error 0x80240034 how to fix
```

## Use this when
- An update repeatedly shows 0x80240034 in Update history.
- The update downloads to 100 percent and then fails without installing.
- Several updates queue behind one that will not clear.

## Not for this skill when
- The client reports to WSUS and the update is not approved there. That is an approval state, not this code.
- Downloads fail before completing. Work the download error code instead.

## Steps
1. Restart the machine to clear any pending rename or restart operation, then check for updates again. Verify: the pending state either clears or reproduces on a clean boot
2. Stop Windows Update and BITS, rename the SoftwareDistribution folder, and restart the services. Verify: a new SoftwareDistribution folder is created on the next detection
3. Run the Windows Update Troubleshooter from Settings, Troubleshoot, Other troubleshooters. Verify: it reports and fixes a datastore or service registration fault, or reports none
4. Check for updates and watch the previously stuck KB. Verify: it installs or fails with a new, more specific code you can act on
5. If the code persists for one KB only, install that KB standalone from the Update Catalog. Verify: Update history shows it installed

## Variant phrasings
### windows update stuck pending 0x80240034
The state-focused phrasing.
### update downloads but wont install 0x80240034
The symptom phrasing for download-complete, install-never-starts.
### 0x80240034 duplicate update datastore
The datastore root-cause phrasing.

Compatibility: Compatibility: Windows 10 and 11; the same datastore reset applies on Server.

## Why it happens
The update agent tracks each update in a local datastore. When an operation is interrupted, entries can be left in a state where the agent believes work is still in progress for that update, so every new attempt short-circuits to the same status code. Rebuilding the datastore forces a fresh detection against the catalog, which is why the reset works.

## Edge cases / pitfalls
- A datastore reset makes the client re-detect everything; on WSUS fleets expect a longer first scan.
- If a feature update is the stuck item, use the Installation Assistant rather than repeated datastore resets.
- Repeated instant re-failure after a reset points at the component store; escalate to DISM repair.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xNGXGkdUV4a60piq7UqgAA