sccm updates stuck at downloading 0 percent

TL;DR

A deployment pinned at 0 percent is a content transfer that started and stalled: check ContentTransferManager.log and DataTransferService.log for the job state, confirm the client can reach the DP over HTTP or HTTPS, look for BITS errors, and check that the Network Access Account or PKI certificate path is valid.

sccm updates stuck at downloading 0 percent

Use this when

• Software Center shows updates downloading at 0 percent indefinitely.
• Other deployments with applications download fine, or also stall, on the same client.
• The stall affects clients at one site or on VPN.

Not for this skill when

• The deployment deadline has not arrived and the client is correctly waiting. Check the deployment schedule first.
• The client is in a maintenance window blackout. The stall is policy, not transfer failure.

Steps

1. Read ContentTransferManager.log and DataTransferService.log and note the job ID and its last state or error. Verify: a concrete transfer error or a suspended state is recorded
2. Check the BITS service is running and list jobs with bitsadmin or Get-BitsTransfer for a suspended or error state. Verify: the job state matches the ConfigMgr logs
3. From the client, browse to the DP content URL shown in the logs. Verify: the DP responds without certificate or 401 errors
4. If the job is suspended by BITS policy or a metered connection setting, clear that condition and resume the job. Verify: bytes transferred begin increasing in the DTS log
5. Restart the SMS Agent Host service if the transfer subsystem is wedged, then re-evaluate the deployment. Verify: a new transfer job is created and progresses past 0 percent

Variant phrasings

sccm updates stuck downloading 0 percent bits

The BITS root-cause phrasing.

software center downloading 0 percent forever

The user-symptom phrasing.

content transfer manager job suspended fix

The log-based phrasing.

Compatibility: Compatibility: Configuration Manager current branch, BITS-based content transfer on Windows 10 and 11 clients.

Why it happens

Software Center shows the deployment state, not the transfer detail. Underneath, Content Transfer Manager creates a BITS job against a specific DP URL. BITS can suspend for policy, network cost, or errors, and the deployment layer simply waits, so the UI sits at 0 percent while the real story is in the transfer logs and the BITS job state.

Edge cases / pitfalls

• A client clock that is wrong breaks DP certificate validation and stalls HTTPS transfers; check time sync on stubborn cases.
• Peer cache and Delivery Optimization change where bytes come from; the logs still name the actual source chosen.
• Deleting the CCM cache mid-transfer makes the stall permanent until the deployment re-evaluates; avoid it as a first move.

Provenance

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