A large Windows 11 update should not turn a fast broadband connection into a stuttering mess, yet that is exactly what can happen when Delivery Optimization is allowed to consume too much of the line. Microsoft’s update-sharing system is designed to make downloads faster and more resilient, especially across homes and organizations with multiple PCs, but its default behavior is not always aligned with a household that is gaming, streaming, video conferencing, or simply trying to use the internet without interruption.

What’s Actually Happening When Updates Arrive

Delivery Optimization is Microsoft’s content-distribution system for Windows updates, Store apps, and certain other Microsoft-delivered content. Instead of relying exclusively on Microsoft’s servers, Windows can obtain portions of a download from other PCs that already have the same files—locally or across the internet.

The system works in pieces. A PC may retrieve some portions from Microsoft, other portions from nearby devices, and potentially additional portions from internet peers if that sharing mode is enabled. Windows verifies downloaded content before installation, so peer delivery is not a mechanism for exchanging personal files.

For a household with multiple Windows PCs, this can reduce the need to repeatedly pull the same multi-gigabyte update from the internet. However, the trade-off is that a PC that can receive update pieces may also upload cached pieces to peers, depending on the selected mode. On an asymmetric residential connection—where download speed is far higher than upload speed—background upload traffic can be especially disruptive. A household might have 500 Mbps downstream but only 20 Mbps upstream. Saturating much of that upload capacity can cause latency, packet loss, unstable game sessions, robotic-sounding voice chat, and buffering during live streams.

Why Windows Doesn’t Always Get It Right

Delivery Optimization has built-in dynamic bandwidth management. By default, Windows attempts to adjust its use of available capacity rather than blindly using every available bit of throughput. However, dynamic does not always mean unnoticeable.

According to Microsoft’s documentation, background downloads can target up to roughly 45% of available bandwidth, and foreground, user-initiated downloads can target up to roughly 90%. Those values are understandable from an update-delivery perspective—if a user actively tells Windows to download a major feature update, Windows assumes the user wants it completed promptly. But an update downloader that can use most of the connection is not ideal when the same machine must remain responsive for real-time activity.

That’s where manually configured limits matter. They replace a dynamic, system-determined target with a ceiling that better reflects the actual needs of a household or workstation.

The Fix: Bandwidth Limits That Work

To set your own limits, navigate to Settings > Windows Update > Advanced options > Delivery Optimization > Advanced options. Depending on your Windows 11 build, you’ll see bandwidth controls under headings such as Download settings, Background download settings, and Foreground download settings.

Windows offers two ways to configure download throttling:
- Percentage of measured bandwidth
- Absolute bandwidth limit, expressed as Mbps or an equivalent fixed-rate value

Absolute caps are easier to reason about. For example, a user could limit background update downloads to 5 Mbps or 10 Mbps. A connection with 100 Mbps download service might tolerate a background cap of 10 Mbps without any noticeable impact on browsing, streaming, or gaming. A slower 25 Mbps connection may need a more conservative ceiling, perhaps 2 Mbps to 5 Mbps. The advantage is consistency: a fixed 5 Mbps cap remains 5 Mbps regardless of how Windows estimates current network conditions.

Percentage limits adapt to faster connections. Setting a background update download limit to 10% means Delivery Optimization scales its use relative to measured available bandwidth. On a high-speed fiber connection, that might allow updates to complete quickly without monopolizing the line. The drawback is that percentage settings depend on Windows’ bandwidth measurement and can be less intuitive.

Microsoft itself recommends absolute-value limits for lower-bandwidth environments.

Foreground vs. Background: Don’t Treat Them the Same

Windows distinguishes between background downloads (automatic, non-interactive tasks) and foreground downloads (user-initiated activity, like starting a download from Windows Update). Background updates are usually the real annoyance—they begin unexpectedly and compete with everything else.

A sensible home configuration often looks like this:
- Keep background downloads at a low, conservative limit.
- Allow foreground downloads a moderately higher limit.
- Use a more restrictive profile during work hours, competitive gaming sessions, or on limited broadband plans.
- Raise the foreground cap temporarily when a major update needs to finish quickly and the connection is otherwise free.

One common claim is that manually pressing Download & install causes Windows to ignore bandwidth caps. That is an oversimplification. User-initiated downloads may be classified as foreground and thus use the foreground configuration rather than the more conservative background configuration. If foreground settings are left unrestricted, a user-initiated update can still consume a large portion of the connection. For complete control, configure both a lower cap for background downloads and a higher but still reasonable cap for foreground downloads.

Beyond Downloads: Upload Control and Other Tricks

Upload saturation is often more destructive than download saturation because it directly harms latency. Delivery Optimization’s upload behavior deserves as much attention as download throttling.

Disable internet peer sharing if it provides no value. The simplest solution is to set Allow downloads from other devices to Off, preventing Delivery Optimization from exchanging content with both local and internet peers. For homes with multiple PCs, the Devices on my local network option retains the benefit of sharing among systems inside the home while preventing broader internet peer sharing.

Use Delivery Optimization upload limits. If you choose to keep internet peer sharing enabled, you can impose a monthly upload data limit (measured in gigabytes) and a percentage limit for upload bandwidth. The monthly cap is especially valuable for connections with data allowances, mobile broadband, or usage-sensitive plans.

Metered connections add a useful safety net. Marking a Wi‑Fi or Ethernet connection as metered (Settings > Network & internet > Wi‑Fi > [Your connected network] > Metered connection) tells Windows to handle data usage more conservatively. On a metered connection, Delivery Optimization does not automatically download or upload parts of updates to other PCs on the internet. This is particularly useful for laptop users on phone hotspots, cellular broadband, satellite internet with strict caps, or hotel Wi‑Fi.

Active hours prevent restarts, not congestion. It’s worth clarifying that Active hours tell Windows when the PC is normally in use so the system can avoid automatically restarting to complete an update. They do not throttle downloads or uploads. Think of the settings this way:
- Delivery Optimization bandwidth limits manage network impact.
- Delivery Optimization sharing mode manages peer-to-peer behavior.
- Metered connection manages data-sensitive network behavior.
- Active hours manage update restart timing.

When to Just Turn It Off

For a single-PC household, disabling peer sharing entirely is a reasonable choice. There is no local fleet of devices to benefit from cached update files, and the potential bandwidth-saving benefit is limited. To do so, go to Settings > Windows Update > Advanced options > Delivery Optimization and turn Allow downloads from other devices off. Then pair it with the bandwidth limits described above.

To verify your changes are working, use the Activity Monitor inside Delivery Optimization (Settings > Windows Update > Advanced options > Delivery Optimization > Activity monitor). It shows data received from Microsoft, local-network peers, internet peers, upload activity, and average download speeds. After a large cumulative or feature update, a single-PC household will likely see little benefit from peer sharing.

Looking Ahead: Microsoft’s Approach to Update Management

Delivery Optimization is not inherently a problem. It is a sensible distribution technology that can reduce redundant downloads and improve update reliability. In a well-managed office or multi-PC home, local peer sharing can be genuinely useful. The issue is that Windows cannot fully understand a user’s immediate priorities—it doesn’t know that a ranked match is about to begin, a cloud backup must complete before a deadline, or a family member is on a video call.

Microsoft’s continued investment in update infrastructure means these settings will likely become more nuanced over time. The company has already deprecated older bandwidth policies in favor of more granular controls, and future builds may offer smarter background optimization. For now, the power is in your hands. A few minutes spent tuning Delivery Optimization can make Windows 11 a much better housemate on any network.