SCCM Client Stuck Downloading: Fixing Applications Stuck at 0%

Fixing SCCM Clients Stuck at 0% Downloading Applications

If a client is stuck at 0% trying to download an application from Software Center — having successfully requested it from the software catalog, but never actually progressing — and this is affecting multiple clients pointed at the same Distribution Point, the DP’s IIS Application Pool is a common place to check before assuming it’s a client-side fault. Log in to the Distribution Point server itself and open IIS Manager. Browse to Application Pools and find the SMS Distribution Points Pool (or similarly named pool depending on your Configuration Manager version). If it’s showing as stopped, right-click it and choose Start. An application pool stopping unexpectedly is often a symptom of something else — repeated crashes, excessive memory use, or IIS’s own recycling settings kicking in more aggressively than expected — so if it keeps stopping after you restart it, check the Windows Event Log on the DP (System and Application logs) around the time it stopped, since that will usually point you at the actual root cause rather than just the symptom.

Still the Right First Check in 2026 (Updated for 2026)

This is still the first thing worth checking on a current Configuration Manager site (build 2603) running on Windows Server 2025 or earlier supported server versions — the SMS Distribution Points Pool stopping in IIS remains the most common cause of clients stalling at 0% on an otherwise-healthy Distribution Point. If the pool keeps stopping repeatedly rather than being a one-off, it’s also worth checking IIS’s Application Pool recycling settings (Advanced Settings > Recycling) — a pool set to recycle on a fixed schedule or after a low private-memory threshold can look like a crash when it’s actually just IIS doing scheduled housekeeping at an inconvenient time for active downloads.

Resources

• guide