sccm error 0x80070070 not enough disk space update deployment

TL;DR

Error 0x80070070 is out of disk space, and in SCCM deployments it usually strikes the client: the cache plus the extracted update payload plus the space the installer needs for servicing exceeds what a small system drive can offer. Free real space on the client, enlarge or relocate the client cache where appropriate, and check for old software distribution content. Fix space first - retrying the deployment onto a full disk just fails at a different percentage.

sccm error 0x80070070 not enough disk space update deployment

Use this when

• Deployment or client logs show 0x80070070 for updates, especially large cumulative updates.
• Affected machines share a small system drive, a nearly full cache, or heavy user profiles on the same volume.
• Other, smaller updates install fine on the same machines.

Not for this skill when

• The site server or distribution point volume is full. Free or extend that server volume instead.
• The client has ample free space and the error appears in a different context such as imaging. Check that context specifically.

Steps

1. Measure before acting: on a failing client record total and free space on the system drive, the size of the Configuration Manager client cache, and the size of the Windows SoftwareDistribution download folder. Compare the free space with the deployment size shown in the console, remembering installs need working room beyond the download itself. Verify: you have real numbers for free space, cache size, and required space that prove the shortfall
2. Free space safely: clear the client cache of superseded content through the Configuration Manager control panel cache settings, run the built-in disk cleanup for update cleanup and temporary files, and remove the renamed old distribution folders left from earlier repairs. Avoid deleting user data as a first move. Verify: free space rises above the deployment size plus a comfortable servicing margin, and the cache no longer holds superseded packages
3. If the model of machine chronically runs small, increase the client cache size in client settings for that collection and consider excluding the cache from any third-party cleanup that refills the drive with temp data between scan and install. Deploy the changed client settings and confirm they apply on the test client. Verify: the test client shows the new cache size and receives the updated client settings without errors
4. Re-run the deployment on the test client and monitor ContentTransferManager and UpdatesHandler logs while watching free space during download, extraction, and install. Note the lowest free space point, because that is the true requirement for the rest of the fleet. Verify: the update installs on the test client and you know the minimum free space the deployment actually consumed
5. Turn the finding into a fleet rule: add a pre-deployment collection or query for machines below that free space threshold, remediate them with your standard cleanup, and only then make the deployment required for that group. Verify: a low-space collection exists, its members are remediated or excluded deliberately, and deployment failures for 0x80070070 stop growing

Why it happens

Cumulative updates are deceptive about space: the package downloads into the client cache, extracts to a larger working set, and the servicing stack keeps rollback copies while it works. A drive that looks adequate at scan time can hit zero during install, and both Windows and Configuration Manager surface that as 0x80070070. Machines built with small system partitions, or drives filled by years of cache and profiles, fail predictably while roomier machines sail through, which makes the error look random until space is measured per machine. Restoring headroom and then gating deployments on a measured threshold removes both the symptom and the recurrence.

Variants and edge cases

0x80070070 only for feature updates via SCCM

Feature updates need far more working space than cumulative updates. Use the upgrade readiness values for required space and remediate or offer the upgrade only to machines that meet it.

Cache keeps refilling the drive after cleanup

Another deployment or application is repopulating the cache. Review required deployments targeting the device and their content sizes before blaming the update itself.

0x80070070 on servers with a small OS volume

Server OS volumes sized for older releases often cannot service current cumulative updates. Extend the volume in the hypervisor where possible rather than repeatedly cleaning.

Compatibility: Applies to Microsoft Configuration Manager current branch deployments to Windows 10, Windows 11, and Windows Server clients.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_u5E-h7e96O6RvGElgc8nfg