In modern enterprise networks, remote branches, and multi-device homes running Windows 11, concurrent operating system updates, Microsoft Store downloads, Microsoft 365 app installations, and Intune Win32 package deployments can quickly saturate internet bandwidth. When twenty workstations on the same local subnet attempt to download a 4GB feature update simultaneously, standard client-to-cloud downloads cause severe network congestion.
To eliminate this bottleneck, Microsoft developed Delivery Optimization (DO). Delivery Optimization is a cloud-managed peer-to-peer caching client that enables Windows 11 PCs to source update packages, applications, and drivers from other computers on the same local network (LAN) or private Active Directory group rather than repeatedly downloading identical bytes from Microsoft content delivery networks (CDNs). Using PowerShell, administrators can configure peer-to-peer modes, define private Group IDs, throttle background bandwidth consumption, and audit peer caching efficiency directly from the command line.
Architecture of Delivery Optimization in Windows 11
Delivery Optimization coordinates peer transfers using a cloud-orchestrated tracking service. Its core operational workflow functions as follows:
- Cloud Coordination: When a Windows 11 client initiates an update download, it contacts the Delivery Optimization cloud service to register its public IP, private subnet, and Group ID.
- Peer Discovery: The cloud service returns a swarm list containing nearby peers that already possess portions of the requested payload.
- Local P2P Handshake: The client establishes secure, encrypted HTTP/HTTPS connections over local port 7680 (default) to peer PCs on the local network, downloading content chunks in parallel.
- Cryptographic Verification: Each downloaded block is cryptographically verified against hash values supplied directly by Microsoft, preventing tampered or corrupted files from being accepted from local peers.
If local peers are unavailable or slower than designated thresholds, Delivery Optimization automatically falls back to standard HTTP downloads from Microsoft CDNs.
Inspecting Active Delivery Optimization Status and Cache Telemetry
Before modifying download policies, inspect your current Delivery Optimization status and historical bandwidth savings using the native DeliveryOptimization PowerShell module.
Launch an elevated PowerShell session and execute:
Get-DeliveryOptimizationStatus | Select-Object FileID, FileSize, TotalBytesDownloaded, PercentPeerCaching, BytesFromPeers, BytesFromHttp
To view aggregate lifetime telemetry indicating the percentage of bandwidth saved through peer caching across your workstation, run:
Get-DeliveryOptimizationPerfSnapThisMonth
This cmdlet outputs a summary showing total bytes retrieved from internet CDNs versus total bytes sourced directly from local peers, providing immediate ROI visibility.
Understanding and Configuring Delivery Optimization Download Modes
The primary control governing peer sharing is the DODownloadMode setting. Delivery Optimization supports six distinct operating modes:
| Mode Value | Mode Name | Behaviour & Deployment Scope |
|---|---|---|
0 |
HTTP Only | Peer-to-peer disabled. All content is fetched directly from Microsoft CDNs. |
1 |
LAN / Subnet | Peers on the same local area network and subnet share files with each other. |
2 |
Group | Peers share content only with devices sharing an identical Active Directory site or custom Group ID GUID. |
3 |
Internet | Peers can share content across the internet with other computers connected to the same public IP/ISP subnet. |
99 |
Simple Mode | Direct HTTP downloads only; bypasses the Delivery Optimization cloud service entirely. |
100 |
Bypass Mode | Delivery Optimization is completely bypassed; uses legacy BITS transfer engine. |
To configure the download mode via PowerShell, update the Delivery Optimization policy registry keys located under HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization:
$RegPath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization"
if (-not (Test-Path $RegPath)) {
New-Item -Path $RegPath -Force | Out-Null
}
# Configure LAN peer-to-peer sharing (Mode 1)
Set-ItemProperty -Path $RegPath -Name "DODownloadMode" -Value 1 -Type DWord
To enforce Group Mode (Mode 2) restricted to a specific office wing, configure a unique Group ID GUID across participating machines:
# Enable Group Mode (Mode 2)
Set-ItemProperty -Path $RegPath -Name "DODownloadMode" -Value 2 -Type DWord
# Assign custom Group ID GUID
Set-ItemProperty -Path $RegPath -Name "DOGroupId" -Value "c8f2a14e-9b21-4d37-8850-209a8bf04d88" -Type String
Throttling Bandwidth and Upload Limits via PowerShell
In environments with sensitive branch uplinks, you must prevent Delivery Optimization from saturating background upload bandwidth while serving files to other peers.
To configure foreground and background bandwidth restrictions:
# Limit background download speed to 40% of available bandwidth
Set-ItemProperty -Path $RegPath -Name "DOMaxBackgroundDownloadBandwidth" -Value 40 -Type DWord
# Limit background upload bandwidth to 30%
Set-ItemProperty -Path $RegPath -Name "DOMaxUploadBandwidth" -Value 30 -Type DWord
# Set monthly peer upload data cap (in Gigabytes, e.g. 50 GB)
Set-ItemProperty -Path $RegPath -Name "DOMonthlyUploadDataCap" -Value 50 -Type DWord
Configuring Cache Size, Retention, and Battery Policies
By default, Delivery Optimization caches downloaded files in C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\Cache.
To manage local disk footprint and prevent SSD exhaustion:
# Set maximum cache size as percentage of drive capacity (e.g. 15%)
Set-ItemProperty -Path $RegPath -Name "DOMaxCacheSize" -Value 15 -Type DWord
# Set maximum cache age in seconds (e.g. 604800 seconds = 7 days)
Set-ItemProperty -Path $RegPath -Name "DOMaxCacheAge" -Value 604800 -Type DWord
# Prevent uploading to peers while running on battery power (laptops)
Set-ItemProperty -Path $RegPath -Name "DOAllowUploadOnBattery" -Value 0 -Type DWord
Verifying Local Firewall Rules for Port 7680
Delivery Optimization relies on TCP and UDP port 7680 for inbound and outbound local peer communication. If Windows Defender Firewall blocks this port, peer discovery fails silently.
To verify that the default firewall rule is active and enabled:
Get-NetFirewallRule -DisplayName "*Delivery Optimization*" | Select-Object Name, DisplayName, Enabled, Direction, Action
If the inbound rule is missing or disabled, enable it via PowerShell:
Enable-NetFirewallRule -Name "DOM-In-TCP"
To monitor active peer connections in real time during an update download, execute:
Get-NetTCPConnection -LocalPort 7680 -State Established
This displays the remote IP addresses of local workstations currently streaming update chunks from your device.