When the metered connection toggle does not explain everything — updates stay stuck after you turn it off, the toggle seems ignored, or different networks behave inconsistently — you need the diagnostic pass. Metered-related update blocking has several layers: the UI toggle, the underlying network cost database, Group Policy, the download queue state, and Delivery Optimization. This guide works through them systematically so you find the actual layer causing your blockage.

If you have not covered the basics, the companion guide on fixing metered connection blocking handles the straightforward cases first.

The key insight for stubborn metered cases is that Windows tracks network cost in two places: the friendly toggle you see in Settings, and a lower-level cost database keyed by network profile that the update engine actually consults. Normally they agree. After driver updates, profile corruption, or VPN shenanigans, they can disagree \u2014 the toggle says unmetered while the engine still sees a costly network. The fixes below address both layers, which is why they succeed where toggle-flipping alone fails. Policy locks add a third layer, closely related to update settings greyed out by policy .

Why this happens

  • Stale queue after unblocking: The metered block is lifted but wedged BITS jobs and confused cache state keep downloads stalled.
  • Per-network flag confusion: The flag is per-network profile; switching between home Wi-Fi, hotspots, and Ethernet means different flags apply at different times.
  • Network cost database mismatch: The underlying DefaultMediaCost registry data disagrees with the UI toggle, usually after network driver changes or profile corruption.
  • Policy overrides: Group Policy or MDM settings restricting updates regardless of the metered toggle.
  • Delivery Optimization restrictions: Metered flags also throttle peer-to-peer update delivery, which can stall downloads even when direct downloads are allowed.
  • Corrupt network profiles: Damaged network profiles that misreport their metered state to the update engine.
  • VPN virtual adapters: VPN connections creating virtual adapters with their own metered flags that override the physical connection’s setting.
  • Data Saver interactions: Mobile-adjacent features and third-party data savers layering additional restrictions on top of Windows’ own.

How to fix it

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

Fix 1: Map which network is actually metered

  1. Go to Settings, Network & internet, and check the metered toggle for every network profile — Wi-Fi, Ethernet, and any VPN virtual adapters.
  2. Note which connection is active right now and what its flag says. The active connection’s flag is the one that matters.
  3. If you use a VPN, check its virtual adapter’s setting too — it can carry its own metered flag.

Fix 2: Toggle deliberately and observe

  1. Turn the metered flag off for your unlimited connection.
  2. Go to Windows Update and click Check for updates. Watch for 10 minutes.
  3. If downloads start, the flag was the blocker — but if they stall again, continue; the queue needs resetting (Fix 4).
  4. If nothing changes at all, the block is at a deeper layer — continue to Fix 3.

Fix 3: Inspect the network cost database and policies

  1. Open regedit and check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost — the values should reflect reality (Ethernet and Wi-Fi typically unmetered by default).
  2. On Pro editions, open gpedit.msc and review Windows Update policies for download restrictions.
  3. If the machine is work-managed (Settings, Accounts, Access work or school), accept that MDM policy may be intentional and check with IT before changing anything.

Fix 4: Reset the stalled download queue

  1. Open an elevated Command Prompt.
  2. Run net stop wuauserv, net stop bits, net stop cryptsvc.
  3. Run bitsadmin /reset /allusers to clear wedged jobs.
  4. Delete the contents of C:\Windows\SoftwareDistribution.
  5. Restart the services, reboot, and check for updates.

Fix 5: Fix corrupt network profiles

  1. In Settings, Network & internet, forget the problematic Wi-Fi network and reconnect fresh — this rebuilds its profile including the metered flag.
  2. For Ethernet, disable and re-enable the adapter in Network Connections (ncpa.cpl).
  3. Re-check the metered toggle on the rebuilt profile and set it correctly.
  1. Go to Settings, Windows Update, Advanced options, Delivery Optimization.
  2. On limited connections, turn off “Allow downloads from other PCs” to stop upload bandwidth use.
  3. Set bandwidth limits for background downloads so updates trickle instead of stalling or hogging the link.

Fix 7: Establish a sustainable update routine

  1. Decide per network: unlimited = unmetered, limited = metered with manual download overrides for security updates.
  2. For capped connections, download the monthly cumulative update once via the Microsoft Update Catalog on unlimited Wi-Fi and install offline.
  3. Document the setup. Reference documentation for these behaviors is at the Microsoft Windows support hub .

Fix 8: Rebuild the network profile from scratch

A corrupt profile can misreport its cost forever.

  1. In Settings, Network & internet, forget the Wi-Fi network entirely and reconnect \u2014 this builds a fresh profile with default cost.
  2. For Ethernet, open ncpa.cpl, disable the adapter, wait 10 seconds, and re-enable it.
  3. Immediately set the metered toggle correctly on the fresh profile before Windows auto-detects anything.
  4. Check for updates. A rebuilt profile eliminates the whole class of “toggle says one thing, engine does another” problems.
  5. Document the working configuration \u2014 note which network uses which flag \u2014 so the next new network does not restart the mystery.

Closing

Metered-connection troubleshooting is about layers: the toggle you see, the cost database underneath, the policies above, the profiles beneath, and the queue state left behind. Work them in order and the actual blocker reveals itself \u2014 usually a stale queue, a corrupt profile, or a per-network surprise rather than anything exotic. Once mapped, a metered setup is genuinely pleasant: security updates on your terms, data cap intact, no mysteries, and no more wondering why updates behave differently on every network.

Frequently asked questions

How do I confirm a metered connection is really the blocker?
Check the metered toggle for your active network in Settings, Network & internet. Then look at Windows Update: on a metered connection it typically shows updates as available with a manual Download button rather than auto-downloading. If toggling metered off immediately starts downloads, you have confirmed the cause.
Why do updates stay stuck even after I turn metered off?
Because the blocked attempts left the download queue in a stalled state — wedged BITS jobs or a confused cache. Turning the flag off removes the block, but the queue still needs a reset: restart the services or clear the SoftwareDistribution cache as covered below.
Can Group Policy force metered behavior?
Yes. Policies can restrict update downloads in ways that mimic or override the metered toggle, especially on work-managed laptops. If the UI toggle changes nothing, policy is the next place to look — and on managed devices, the answer may be that IT intends the restriction.
What's the difference between this guide and the basic metered fix?
The companion fix guide handles the common toggle-level resolutions — the quick wins. This troubleshooting guide is for the stubborn cases: policy overrides, registry cost settings, stalled queues that survive the toggle change, corrupt network profiles, and per-network confusion when switching between connections. Start with the companion guide; come here when the basics did not fully resolve things.