KB5055523 sits in your Windows Update queue like a parked car: 0% downloaded, an hour gone, nothing happening. Clicking retry just resets the same frozen number. On Dell laptops this particular stall has a familiar fingerprint — Dell’s own updater services and a corrupted Windows download cache fighting over the same payload — and it responds to a specific sequence of fixes rather than random button-mashing.

The pattern usually goes like this: the update appears, starts downloading, then freezes at a round number. Task Manager shows no meaningful network traffic from update processes. Everything else on the laptop works fine, which makes it feel personal — but it’s mechanical. The downloader has wedged on a bad cache entry, a locked file, or a service conflict, and it needs you to clear the wedge. If you’re dealing with its predecessor instead, our KB5036893 stuck-downloading guide for Dell covers the same machinery.

Two ground rules before you start: keep the laptop plugged in, and don’t run Dell SupportAssist scans while troubleshooting. Then work top to bottom — each fix is more thorough than the last, and most people are unstuck by Fix 5.

Why this happens

  • Wedged Delivery Optimization cache: The peer-to-peer download cache can disagree with Microsoft’s manifest, freezing progress at a fixed percentage with no error surfaced.
  • SupportAssist payload contention: Dell SupportAssist and Windows Update both reach for driver packages; when Dell’s service holds a lock, the Windows download stalls.
  • Corrupted BITS queue: The Background Intelligent Transfer Service owns the actual transfer. A corrupted job queue makes it report ‘downloading’ while moving zero bytes.
  • Metered network flag: A metered Wi-Fi or hotspot connection silently blocks large cumulative update downloads — the UI just shows a frozen bar.
  • Low disk space for staging: KB packages need free space well beyond their download size for extraction and signature verification.
  • Third-party antivirus interception: Real-time scanners can lock each incoming chunk, preventing the downloader from assembling the final package.
  • Stale update orchestrator state: The Update Orchestrator service can get stuck in a ‘busy’ state from a previous interrupted session, blocking new downloads.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm it’s actually stuck, then restart BITS and Windows Update

First verify with data, not vibes: two hours with zero progress and flat network traffic means stuck. Restarting the transfer services clears the most common transient wedge.

  1. Open Task Manager → Performance and confirm update network activity is essentially zero over 10 minutes.
  2. Press Win + R, type services.msc, press Enter.
  3. Restart Background Intelligent Transfer Service and Windows Update (right-click → Restart).
  4. In Settings → Windows Update, click Retry and watch for 10–15 minutes.

Fix 2: Disable metered connection and reset Delivery Optimization

A hidden metered flag is the number-one silent blocker, and a stale peer cache is number two. Clear both in one pass.

  1. Settings → Network & internet → your Wi-Fi/Ethernet connection → set Metered connection to OFF.
  2. Settings → Windows Update → Advanced options → Delivery Optimization → toggle Allow downloads from other PCs off, wait 30 seconds, toggle back on.
  3. Click Clear under Activity monitor if the option appears, to drop stale peer data.
  4. Retry the download.

Fix 3: Pause Dell’s updater services during the download

SupportAssist and Dell Update are useful, but during a stuck KB they are suspects. Pause them, download, then restore.

  1. Open Dell SupportAssist → settings → pause automatic updates and scheduled scans.
  2. Open Task Manager → Services tab, find Dell-related services, and stop the updater ones (leave hardware-monitoring services alone).
  3. Restart the laptop to release any held file locks.
  4. Retry KB5055523 in Windows Update. Re-enable Dell’s updaters afterward via Dell Support guidance if needed.

Fix 4: Temporarily pause third-party antivirus

This is a diagnostic step, not a lifestyle change. If the download moves with protection paused, you’ve found your culprit.

  1. Open your third-party antivirus and pause real-time protection for 30 minutes.
  2. In Settings → Windows Update, click Retry.
  3. If the percentage starts climbing, let it finish, install, reboot — then immediately re-enable protection.
  4. Consider adding the SoftwareDistribution folder to your AV’s exclusions if the problem recurs.

Fix 5: Reset the Windows Update download cache

Renaming SoftwareDistribution and catroot2 forces Windows to rebuild its entire download workspace. This resolves the majority of hard stalls.

  1. Open an administrator Command Prompt.
  2. Run: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Run: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Run: net start wuauserv, net start cryptSvc, net start bits, net start msiserver.
  5. Check for updates — KB5055523 will start downloading fresh. The full procedure with explanations lives in how to reset Windows Update components on Windows 11 .

Fix 6: Clear disk space and run the troubleshooter

Tight SSDs stall the verification stage silently. Free space plus the built-in troubleshooter covers the environmental causes.

  1. Settings → System → Storage → Temporary files → remove Delivery Optimization Files and other safe categories.
  2. Confirm at least 12–15 GB free on C:.
  3. Settings → System → Troubleshoot → Other troubleshooters → run the Windows Update troubleshooter.
  4. Restart and retry the download.

Fix 7: Install KB5055523 manually from the Microsoft Update Catalog

When the built-in downloader refuses, go around it. The standalone .msu is the identical Microsoft-signed package.

  1. Visit the Microsoft Update Catalog and search KB5055523.
  2. Match the x64 package to your build (Settings → System → About).
  3. Run the .msu, restart when prompted.
  4. Verify in Settings → Windows Update → Update history that KB5055523 installed successfully.

Fix 8: Repair system files and check Dell firmware alignment

Last resort before escalation: fix the component store so any download validates, and make sure Dell firmware isn’t the blocker.

  1. Admin Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Restart.
  2. Visit Dell Support , enter your Service Tag, and check for BIOS/chipset updates newer than your current ones.
  3. Install any critical Dell firmware updates, reboot, then retry or manually install the KB.
  4. If it still fails, note the exact error code from Update history for Dell support.

Closing

KB5055523’s Dell download stall is a solved problem — it’s just a matter of clearing the right cache, pausing the right competing service, or sidestepping the downloader with a manual install. Start gentle, get progressively more thorough, and keep the manual Catalog package in your back pocket as the guaranteed way through. Related guides: KB5036893 stuck-downloading guide for Dell and how to reset Windows Update components on Windows 11 .

Frequently asked questions

What is KB5055523 and why does it stall on Dell machines?
KB5055523 is a Windows 11 cumulative update package. On Dell laptops it commonly stalls because Dell’s SupportAssist and Dell Update services compete for the same driver payloads, or because the SoftwareDistribution download cache has corrupted. The progress bar typically freezes at 0%, 20%, or 99% and retrying rarely helps until the underlying cache or conflict is cleared.
Should I disable my antivirus to let KB5055523 download?
Temporarily, yes — as a diagnostic step. Some third-party suites intercept each downloaded chunk for scanning and hold file handles that block assembly. Disable real-time protection for 30 minutes, retry the download, and re-enable it immediately after. Windows Security (Defender) rarely causes this, so the issue points at third-party products.
Will resetting the update cache delete my files?
No. Resetting SoftwareDistribution and catroot2 only removes Windows Update’s working files — partial downloads, manifests, and logs. Your documents, apps, settings, and installed updates are untouched. Windows rebuilds both folders automatically the next time it checks for updates. The renamed .old folders serve as your undo button if anything ever looks wrong, though in practice the rebuild just works.
How do I know the manual install actually worked?
After running the .msu and rebooting, go to Settings → Windows Update → Update history. KB5055523 should appear under Quality Updates with an install date. Also verify your build number in Settings → System → About matches the build the KB targets. If the KB is missing from history afterward, the install didn’t take — note any new error code before retrying.