“Pending download.” That’s all Windows Update says, for days, while your laptop quietly falls behind on patches. No error code, no warning — just a queue that never moves. If you’re on a hotspot, a capped plan, or any network flagged as metered, this isn’t a malfunction. It’s Windows protecting your data allowance. But protection you can’t override when you need to is just another word for broken.

This troubleshooting guide maps the whole metered-connection update problem: how to confirm metering is the actual cause (and not something else wearing its symptoms), how to unstick the queue, and the techniques for updating surgically without data waste. For the quick best-practice routine, our best-way guide covers the 5-minute version.

The most common misdiagnosis here: assuming metering is the problem when it’s actually a stuck queue from a previous network. If you recently switched from a metered hotspot to unmetered home Wi-Fi and updates still won’t download, the queue may be wedged in its old state — Fix 2’s pause/resume cycle is specifically for that. Always verify the current network’s metered flag (Fix 1) rather than assuming based on where you were yesterday.

Why this happens

  • Metered flag on the active network: The direct cause — auto-downloads paused by policy.
  • Wrong network flagged: Home broadband mistakenly marked metered months ago and forgotten.
  • Hotspot auto-metering: Tethering defaults to metered without asking.
  • Stuck queue state: “Pending download” entries that don’t resume after the flag changes.
  • Store apps also deferred: Parallel stalling in Microsoft Store updates confusing diagnosis.
  • Delivery Optimization disabled: No peer sources, slower recovery when allowed.
  • Confusion with paused updates: A set pause looking identical to a metered block.

How to fix it

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

Fix 1: Confirm metering is the actual cause

Don’t fix the wrong problem.

  1. Settings > Network & internet → open your active connection → check the Metered connection toggle.
  2. Settings > Windows Update → check whether updates are paused (a pause banner looks similar).
  3. If metered is ON and updates show “pending download,” metering is your cause. If metered is OFF and nothing downloads, you have a different update problem — start with our update-service guide .

Fix 2: Unstick the queue after changing the flag

Flag changes don’t always propagate to queued items.

  1. Toggle the metered setting (or enable Download updates over metered connections), then pause updates for a week.
  2. Wait 2 minutes, resume updates, and click Check for updates.
  3. The pause/resume cycle forces the queue to re-evaluate against the new policy.

Fix 3: The surgical manual-download method

Zero data waste, full control.

  1. Identify needed KBs from Update history or the pending list.
  2. Download each .msu from the Microsoft Update Catalog on an unmetered connection.
  3. Install locally — the metered laptop’s network is never involved.

Fix 4: Correct mislabeled networks

The forgotten-flag problem.

  1. Review every known Wi-Fi network under Settings > Network & internet > Wi-Fi > Manage known networks.
  2. Any uncapped network (home, office) with metering ON: open it and switch the flag OFF.
  3. Keep hotspots and cellular flagged. This single audit fixes a surprising number of “updates never run” cases.

Fix 5: Configure Store apps separately

Don’t let the Store side confuse the picture.

  1. Open Microsoft Store > profile > Settings → check App updates behavior on metered connections.
  2. Update critical apps manually over unmetered connections to keep the two queues independent.

Fix 6: Set data guardrails for forced metered updating

When you must update on the capped network.

  1. Delivery Optimization > Advanced options: set absolute bandwidth caps for background downloads. A cap of 5–10 Mbps keeps the update from saturating a hotspot and killing everything else you’re doing while it downloads.
  2. Monitor Settings > Network & internet > Data usage during the update. Check it before starting (baseline), midway, and after — if the numbers don’t match what the update should cost, something else is eating data in the background (OneDrive sync and Store updates are the usual suspects; pause them).
  3. Download order matters: security cumulatives first, drivers second, feature updates only with ample allowance. Microsoft’s metered-update documentation is at the Windows update support hub . If the allowance runs out mid-queue, the remaining items simply wait — they don’t fail, they just pause, which is the graceful behavior you want.

Fix 7: Build the monthly update ritual

Prevention beats troubleshooting.

  1. After each data-plan reset: 30-minute session — unmeter, full update, re-meter.
  2. Between sessions: manual KBs for urgent items only.
  3. Quarterly: re-audit known networks for flag drift.

Closing

Metered-connection update trouble is a policy problem, not a technical failure — which means it yields to deliberate policy management rather than repair tools. Confirm the cause, manage the flags, unstick the queue, and build the monthly ritual. Your updates stay current, your data cap stays intact, and “pending download” becomes a status you see only when you choose to.

The deeper lesson generalizes beyond metered connections: most “Windows Update is broken” complaints are really “Windows Update is obeying a policy I forgot I set.” Paused updates, deferred upgrades, metered flags, active-hours restrictions — the system is full of well-meaning brakes, and troubleshooting starts with checking which brakes are engaged before assuming the engine is damaged. That one habit — checking policy before repairing machinery — will serve you in every corner of Windows administration. Policies are quiet, persistent, and easy to forget; machinery is loud and obvious. Troubleshooting the quiet layer first saves you from rebuilding things that were never broken. Keep this guide’s diagnostic order in mind for next time — confirm the flag, unstick the queue, manage the policy — and metered-connection mysteries resolve in minutes instead of days. The queue is patient; there’s no penalty for letting updates wait until the conditions are right.

Frequently asked questions

Why do updates say 'pending download' forever on my hotspot?
Hotspot and cellular connections are marked metered by default, and Windows queues most updates as ‘pending download’ rather than fetching them. It’s not an error — it’s the data-protection behavior working as designed. The fixes below show how to push specific updates through or update around the restriction.
What's the difference between pausing updates and a metered block?
Pausing is a deliberate, time-limited hold you set (1–5 weeks); a metered block is an indefinite network-policy hold that lasts as long as the flag is on. They look similar in the UI (nothing downloads), but the fixes differ — pausing is cancelled with one click, metering needs the network-level changes below.
Do metered connections block Microsoft Store app updates too?
Yes — Store apps also defer updates on metered connections by default, with a separate toggle in the Microsoft Store settings. If you’re troubleshooting broadly stalled updating on a capped connection, check both Windows Update and Store settings, since fixing only one leaves the other still stalled.
Can my VPN make Windows think the connection is metered?
VPNs don’t set the metered flag, but they can cause similar symptoms: stalled downloads from CDN issues or proxy interference. If updates stall on a VPN even with metering off, disconnect the VPN and test — that’s a different problem with different fixes.