Your Windows PC might be doing something you didn’t expect: quietly participating in
Delivery Optimization, Microsoft’s peer-assisted update system. In plain English, that means your computer can help distribute parts of Windows and Microsoft Store updates to other PCs, including devices on the internet, not just your own network. Microsoft says the goal is to reduce bandwidth use and make updates more reliable, but the trade-offs are real enough that many users will want to change the setting. com]
Background
Windows has long treated updating as a shared responsibility between the local machine and Microsoft’s cloud.
Delivery Optimization is the modern version of that idea, built to split update files into chunks and source those chunks from other devices when possible. Microsoft’s own documentation describes it as a cloud-managed downloader that can use alternate sources such as local peers, internet peers, and even cache infrastructure in enterprise environments.
That design is not accidental. Microsoft has spent years trying to make Windows Update feel faster, less wasteful, and more resilient on unstable connections. The company’s support pages explicitly note that sharing update data can reduce the internet bandwidth needed to keep multiple devices current, and that it may improve success rates on limited or unreliable internet connections.
At the same time, the feature has always carried a subtle trust problem. A user may understand that Windows is not sending documents or photos to strangers, but “my PC uploads update pieces to other computers” still sounds unsettling the first time you hear it. That reaction is understandable, especially because the activity happens in the background and can be easy to miss unless you dig into Windows Update settings or review activity monitoring.
The latest wave of concern is less about security and more about control. MakeUseOf’s framing captures a broader user sentiment: people are increasingly willing to accept background optimization only when they can clearly see the payoff. If the feature costs bandwidth, disk space, or performance, many home users would rather opt out than trade resources for a theoretical network benefit.
What Delivery Optimization Actually Does
Delivery Optimization is easiest to understand as a
peer-to-peer distribution layer for Microsoft content. Instead of downloading every update directly from Microsoft’s servers, your PC can pull pieces from other devices that already have those pieces, then combine them with pieces from Microsoft’s own infrastructure. That is true for Windows updates and Microsoft Store app downloads, and Microsoft documents the same pattern across Windows 10, Windows 11, and Microsoft 365 app delivery.
The important detail is that the system is chunk-based rather than file-based. Windows does not simply grab a whole package from one random PC. It requests smaller segments, checks authenticity, and reassembles the payload locally. Microsoft says the same security measures apply as with ordinary update delivery, and that Delivery Optimization uses secure Microsoft-provided information to validate the content it receives from peers.
How the sharing path works
In practical terms, Delivery Optimization can draw from several sources depending on policy and edition. A device may use the public internet, a device on the same local network, or a dedicated cache in enterprise settings. Microsoft’s documentation notes that peer-to-peer sharing is enabled by default for local-network sharing in Windows client Enterprise, Professional, and Education editions, while home behavior is governed by the user-facing toggle.
That flexibility is why Microsoft likes the feature. It scales well across offices, schools, and households with multiple PCs. It can also reduce pressure on Microsoft’s content delivery network, which matters when billions of devices are all trying to install updates on roughly the same schedule.
For consumers, though, the benefit can be more abstract. If you have fast broadband, a single PC, and plenty of storage, the feature may feel like background noise. If you are on a data cap, a hotspot, or a slower connection, it can feel like Windows is taking resources you would rather reserve for something else.
- It can download update parts from other PCs.
- It can upload parts of update files to other PCs.
- It applies to Windows Update and Microsoft Store content.
- It is designed to improve speed, reliability, and bandwidth efficiency.
Why Microsoft Built It
The logic behind Delivery Optimization is not hard to defend. Windows is an enormous installed base, and update traffic creates real infrastructure costs. By turning millions of PCs into distributed sources for update chunks, Microsoft reduces repeated downloads from its own servers and can make updates more efficient for inconsistent connections.
There is also a special benefit for organizations. Enterprises can use peer-assisted delivery to cut WAN traffic, especially in branch offices or campuses where many devices need the same payload. Microsoft Learn shows the feature being tuned through Intune and other management tools with controls for bandwidth, cache age, cache size, and peer selection.
Enterprise math versus home-user intuition
ments, the equation is simple: fewer direct downloads from the internet can mean lower cost and better predictability. An admin can steer where content comes from and how much bandwidth the service may consume, which makes the feature part of a broader patch-management strategy rather than a hidden nuisance.
Home users do not usually think in those terms. They think in terms of
my connection, my data, my PC. That mismatch explains why a feature built for efficiency can feel invasive, even when it is technically safe and working as intended. (
learn.microsoft.com)
Microsoft’s rationale remains coherent, but its user experience depends heavily on transparency. When the feature is obvious and adjustable, it looks like an optimization. When it is invisible and active, it can feel like Windows is freeloading on your network. (
support.microsoft.com)
The Real Downsides for Users
The biggest complaint is
background bandwidth consumption. Even if the upload rate is modest, any service that sends data in the background can compete with gaming, streaming, video calls, cloud backups, or large downloads. That competition becomes more noticeable on slower connections or when several household devices are active at once.
The second issue is storage. Microsoft says Delivery Optimization creates a local cache and keeps files for a short time, which is useful for sharing but not free. On space-constrained systems, especially laptops with small SSDs, the cache can become a quiet storage hog.
When cache turns into clutter
This cache behavior is one of the reasons people discover Delivery Optimization only after they need disk space. If you have ever looked at a storage report and found several gigabytes tied up in a folder you barely knew existed, you are not alone. MakeUseOf’s example of reclaiming nearly 20 GB by clearing old Delivery Optimization files illustrates how the accumulation can become unexpectedly large on some systems.
The third concern is performance variability. Microsoft does not market the feature as a performance risk, but user reports have linked Delivery Optimization to memory growth and occasional sluggishness on certain machines. Those reports are not universal, and they may reflect bugs or edge-case behavior rather than the intended design, but they are enough to make cautious users think twice.
- Bandwidth can be consumed in the background.
- Disk space can be used by the cache.
- RAM pressure has been reported by some users.
- Gaming and video calls may feel the impact first.
- The trade-ofes**.
Privacy and Security: What Matters and What Doesn’t
The feature does not expose your personal files in the way people often fear. Microsoft states that Delivery Optimization only handles the same update and app content you would already get from Windows Update and Microsoft Store, and it uses security checks to verify authenticity. That means the service is not mining your private documents to upload them to random computers.
Still, privacy is not only about file contents. It is also about network behavior, predictability, and consent. If your PC is uploading data to peers on the internet, you may reasonably want that activity to be opt-in, limited, or at least clearly bounded by policy.
Security validation is not the same as user comfort
Microsoft’s validation model is strong enough to address the obvious malware concern. It does not eliminate the discomfort some users feel about giving a PC permission to contribute upload capacity to strangers’ update downloads. That is a policy question as much as a technical one.
For business environments, the feature is easier to justify because administrators can apply controls centrally. For consumers, the burden shifts to settings awareness. If you never open the Delivery Optimization page, you may never realize your PC has been participating in this kind of background traffic.
That disconnect is why Delivery Optimization has become a recurring talking point in Windows optimization guides. It is technically legitimate, but emotionally it sits in the same category as other background services that users only notice when they start hunting for wasted bandwidth or disk space.
How to Turn It Off
The simplest fix is to turn off sharing from other devices. On Windows 11, Microsoft says to open
Settings > Windows Update > Advanced options > Delivery Optimization, then disable the
Allow downloads from other devices toggle. When that is off, your PC downloads updates directly from Microsoft and does not upload to or download from other PCs.
If you want a compromise, you can keep the feature but restrictwork. That lets multiple PCs in the same home or office benefit from faster, shared delivery without sending update parts to devices on the internet. Microsoft explicitly documents that middle-ground option. (
support.microsoft.com)
Practical settings path
For most users, the decision tree is straightforward. If you care most about simplicity, turn the feature off. If you care about reducing repeated downloads across several machines in the same house, keep it limited to local devices. If you are on a metered or capped connection, Microsoft also says Delivery Optimization will not automatically send parts of updates to other PCs on the internet when that connection is marked as metered.
You can also control the service more aggressively in enterprise settings. Microsoft Learn shows bandwidth limits, cache age controls, and download-mode policies that administrators can enforce through Intune and related management layers. That is the kind of control home users wish they had in a simpler form.
- Turn off sharing entirely if you want zero peer traffic.
- Limit sharing to devices on my local network for a home-network compromise.
- Mark expensive connections as metered to reduce background usage.
- Use bandwidth caps if you want the feature but not the overhead.
Bandwidth Controls, Metered Connections, and the Middle Ground
Microsoft did not make Delivery Optimization all-or-nothing by accident. The company knows that many users want the efficiency benefits without the feeling that Windows is freelancing on their connection. That is why you can cap upload and download behavior, especially in managed environments where administrators must balance patch speed against network saturation.
The metered-connection setting is especially useful for laptops and hotspot users. Microsoft says a metered or capped connection prevents Delivery Optimization from automatically downloading or sending update parts to other PCs on the internet. In effect, it tells Windows to behave more politely on expensive links.
Why the middle ground matters
This is one of those Windows features where
how you use it matters more than whether it exists. A desktop on fiber with several PCs in the home may benefit from peer-sharing. A single laptop on a mobile hotspot almost certainly should not. The right setting depends less on ideology than on your actual network conditions.
That distinction also explains why some e service at all. If your network is fast and unconstrained, Delivery Optimization may be effectively invisible. The louder the complaints, the more likely they come from people near the margins: data caps, low storage, or modest hardware.
In other words, thleryone. It is a context-sensitive compromise, and Windows is often at its most controversial when it assumes that what is efficient for the network must also be acceptable for the user.
Enterprise Versus Consumer Impact
Enterprises usually see Delivery Optimization as part of a broader
update orchestration strategy. Microsoft’s documentation emphasizes policy controls, cache management, peer selection, and bandwidth governance, all of which make sense when hundreds or thousands of endpoints must be updated without overwhelming a WAN link or VPN.
Consumers experience the same mechanism in a much more personal way. They do not manage update rings or cache servers. They just notice that Windows may be using their connection to support someone else’s download, or that the cache is taking up room on a small SSD. That mismatch makes the feature feel heavier than the technical description suggests.
Why admins accept what consumers reject
Admins can justify the feature by pointing to lower WAN traffic, lower dependency on a single origin server, and more predictable patch rollout across managed devices. They can also test and constrain behavior with policy. Consumers, by contrast, usually evaluate the service through the lens of annoyance: did it slow a call, consume a cap, or chew up storage?
That is why the same technology can be praised in one setting and resented in another. In a school district, it can be a network-saver. On a family laptop with 128 GB of storage, it can be one more thing to clean up.
The broader lesson is familiar across Windows: features built for fleet management often land awkwardly in consumer settings. Delivery Optimization is not unique in that regard, but it is unusually visible because it touches bandwidth, privacy perceptions, and disk usage all at once.
Storage, RAM, and Performance Concerns
Microsoft’s official line focuses on efficiency, not resource drain. But the feature’s local cache means it will inevitably consume disk space, and some users have reported memory behavior that seems out of proportion to the promise of a background optimization tool. Those reports deserve caution, but they are common enough to affect how users judge the feature.
The cache itself is not inherently a problem. Cache is part of how Windows works: it speeds future operations by preserving content temporarily. The issue is that on small drives and lower-memory systems, even a well-intentioned cache can become one more contributor to a broader sense of system bloat.
The hidden cost of convenience
This is where perception and engineering diverge. Microsoft sees a temporary cache and peer-enabled efficiency. Users see gigabytes of storage used for something they did not knowingly request. Both views are valid, but only one of them is experienced every day at the desktop.
The same goes for memory complaints. If a service appears to balloon in RAM usage, even if only under specific conditions, that can erode trust fast. A background component that should be invisible becomes the first suspect when a PC starts feeling sluggish.
That is why users who never run into the issue may still want the feature off simply to reduce uncertainty. A system can be technically correct and still emotionally expensive. Delivery Optimization sits right in that uncomfortable space.
Strengths and Opportunities
The strongest argument for Delivery Optimization is that it solves a real distribution problem in a scalable way. It also gives Microsoft and IT administrators meaningful levers to manage patch traffic instead of treating every endpoint as an isolated island. In the right environment, the feature is smart, economical, and practical.
- Reduces duplicate downloads from Microsoft’s servers.
- Helps large fleets update more efficiently.
- Improves delivery on unreliable connections.
- Can accelerate downloads on multi-PC networks.
- Supports granular policy control in enterprise environments.
- Works with Windows Update, Microsoft Store, and other Microsoft content.
- Offers a local-network-only compromise for cautious users.
Risks and Concerns
The main risk is not malware or exposure of personal files; it is the combination of hidden background activity, bandwidth use, storage consumption, and occasional resource complaints. For users with limited data, small SSDs, or modest hardware, those costs can outweigh the convenience. The feature also creates a trust issue because many users dislike any service that looks like it is using their network without obvious benefit.
- Can consume upload bandwidth in the background.
- May contribute to sluggishness on slow or congested links.
- Uses disk space for a local cache.
- Can be confusing for users who do not want peer sharing.
- May be undesirable on metered or hotspot connections.
- Has been associated with memory-growth complaints in some reports.
- Feels invasive to users who prefer explicit control over background traffic.
Looking Ahead
The future of Delivery Optimization will likely depend less on whether Microsoft keeps the feature and more on how much visibility and control it gives users. Microsoft already offers a fairly rich policy surface for enterprises and a simple toggle for consumers, but the feature still lacks the kind of everyday clarity that would make it feel natural to most people. If Windows wants users to keep it enabled, it needs to make the benefits more visible and the costs easier to predict.
That is especially important as Windows continues to straddle two worlds: consumer convenience and fleet-scale management. The more Microsoft tries to unify update delivery across those environments, the more likely it is to encounter friction from users who just want a quiet, private, low-overhead PC. The ideal next step is not removing peer-to-peer delivery entirely, but making sure it behaves in a way that matches user expectations instead of surprising them.
What to watch next:
- Whether Microsoft adds more prominent explanations in Windows Update.
- Whether memory and cache complaints trigger servicing changes.
- Whether consumer settings gain finer bandwidth controls.
- Whether enterprise policy remains the main place for real tuning.
- Whether more users move toward local-network-only sharing.
- Whether metered connection behavior becomes more intuitive by default.
In the end, Delivery Optimization is a useful idea with uneven optics. It is safe in the narrow security sense Microsoft describes, but it is not free, invisible, or universally welcome. For users who value bandwidth, storage, and control, turning off “Allow downloads from other devices” is a sensible, low-risk choice; for everyone else, leaving it on with local-only sharing may strike the better balance. Either way, the real story is not that Windows is secretly doing something malicious, but that convenience always comes with a bill, and Windows is finally making users read the fine print.
Source: MakeUseOf
Windows is using your internet to send updates to strangers — here's the setting to stop it