Windows 11: 22H2 · 3.0 to 25H2 · 1.0

[removed: This policy allows you to delay the use of an HTTP source in a ][added: For ]background download[added: s] that [removed: is allowed to ]use [removed: P2P. After the max delay has reached, ][added: P2P, specifies ]the [removed: download will resume using HTTP, either downloading the entire payload or complementing the bytes that could not be downloaded ][added: time to wait before starting to download ]from [removed: Peers. Note that a download that is waiting for peer sources, will appear to be stuck for ]the [removed: end user. The recommended value is 1 hour (3600).][added: HTTP source.]

[removed: Set this policy to delay the fallback from Cache Server to ][added: For background downloads that use a cache server, specifies ]the [removed: HTTP source for a background content download by X seconds. Note: if you set the policy ][added: time to wait before falling back ]to [removed: delay background ]download from [removed: http, it will apply first (to allow downloads from peers first).][added: the original HTTP source.]

[removed: Set this policy to delay the fallback from Cache Server to ][added: For foreground downloads that use a cache server, specifies ]the [removed: HTTP source for a foreground content download by X seconds. Note: if you set the policy ][added: time to wait before falling back ]to [removed: delay foreground ]download from [removed: http, it will apply first (to allow downloads from peers first).][added: the original HTTP source.]

[removed: This policy allows you to delay the use of an HTTP source in a ][added: For ]foreground [removed: (interactive) download ][added: downloads ]that [removed: is allowed to ]use [removed: P2P. After the max delay has reached, ][added: P2P, specifies ]the [removed: download will resume using HTTP, either downloading the entire payload or complementing the bytes that could not be downloaded ][added: time to wait before starting to download ]from [removed: Peers. Note that a download that is waiting for peer sources, will appear to be stuck for ]the [removed: end user. The recommended value is 1 minute (60).][added: HTTP source.]

This policy setting lets you turn on Content URI Rules to supplement the static Content URI Rules that were defined as part of the app manifest and apply to all [removed: Windows][added: packaged Microsoft] Store apps that use the enterpriseAuthentication capability on a computer. If you enable this policy setting, you can define additional Content URI Rules that all [removed: Windows][added: packaged Microsoft] Store apps that use the enterpriseAuthentication capability on a computer can use. If you disable or don't set this policy setting, [removed: Windows][added: packaged Microsoft] Store apps will only use the static Content URI Rules.

[removed: Set this policy to restrict peer selection to a specific source. Options available are: ][added: Specifies the source of group ID used for peer selection. 0 = Not Set ]1 = AD Site[removed: . ] 2 = Authenticated domain SID[removed: . ] 3 = DHCP Option ID[removed: . ] 4 = DNS Suffix[removed: . ] 5 = [removed: AAD Tenant ID. When set, the Group ][added: Entra ]ID [removed: will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also set. The options set in this policy only apply to Group (2) download mode. If Group (2) isn't set as Download mode, this policy will be ignored. For option 3 - DHCP Option ID, the client will query DHCP Option ][added: Tenant ]ID[removed: 234 and use the returned GUID value as the Group ID.]

Specifies the maximum background download bandwidth in KiloBytes/second that the device can use across all concurrent download activities using Delivery Optimization.[removed: The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads. ]

Specifies the maximum time in seconds that each file is held in the Delivery Optimization cache after downloading successfully.[removed: The value 0 (zero) means "unlimited"; Delivery Optimization will hold the files in the cache longer and make the files available for uploads to other devices, as long as the cache size has not exceeded.]

Specifies the maximum cache size that Delivery Optimization [removed: uses][added: can utilize,] as a percentage of [added: the ]available [removed: disk size (1-100).][added: drive space.]

Specifies the maximum foreground download bandwidth in KiloBytes/second that the device can use across all concurrent download activities using Delivery Optimization.[removed: The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads. ]

Specifies the minimum download QoS (Quality of [removed: Service or speed)][added: Service) in KiloBytes/sec] for background [removed: downloads in KiloBytes/second. This policy affects the blending of peer and HTTP sources. Delivery Optimization complements the download from HTTP source to achieve the specified minimum QoS value.][added: downloads.]

[removed: Specify any value between 1 and 100 (in percentage) to allow ][added: Specifies ]the [removed: device to upload data to LAN and Group peers while on DC power (Battery). The recommended value ][added: minimum battery level required for uploading ]to [removed: set if you allow uploads on battery is 40 (for 40%). The device can download from peers ][added: peers, ]while on battery [removed: regardless of this policy. The value 0 means "not-limited"; The cloud service set default value will be used.][added: power.]

Specifies the required minimum [added: total ]disk size [removed: (capacity ]in [removed: GB)][added: GB] for the device to use [removed: Peer Caching. The cloud service set default value will be used. Recommended values: 64 GB to 256 GB. Note: If the DOModifyCacheDrive policy is set, the disk size check will apply to the new working directory specified by this policy.][added: P2P.]

Specifies the minimum content file size in MB [removed: enabled][added: eligible] to use [removed: Peer Caching. Recommended values: 1 MB to 100000 MB.][added: P2P.]

Specifies the minimum [added: total ]RAM size in GB required to use [removed: Peer Caching. For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching. Recommended values: 1 GB to 4 GB.][added: P2P.]

Specifies the maximum [removed: total ]bytes in GB that Delivery Optimization is allowed to upload to Internet peers in each calendar month.[removed: The value 0 (zero) means "unlimited"; No monthly upload limit is applied if 0 is set.]

Specifies the maximum background download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.[removed: The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for background downloads.]

Specifies if the DNS client would use the DDR protocol. The Discovery of Designated Resolvers (DDR) protocol allows Windows to move from unencrypted DNS to encrypted DNS when only the IP address of a resolver is known. If you enable this policy, the DNS client will use the DDR protocol. If you disable this policy setting, or if you do not configure this policy setting, [removed: computers][added: the DNS client] will use locally configured settings.

Specifies the maximum foreground download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.[removed: The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for foreground downloads.]

Specifies if the DNS client will perform name resolution over [removed: DNS over HTTPS (DoH).][added: encrypted protocols.] By default, the DNS client will do classic DNS name resolution (over UDP or [removed: TCP).][added: TCP port 53).] This setting can enhance the DNS client to use [removed: DoH protocol][added: encrypted protocols] to resolve domain names. To use this policy setting, click Enabled, and then select one of the following options from the drop-down list: Prohibit [removed: DoH: No DoH][added: encryption: no encrypted] name resolution will be performed. Allow [removed: DoH: Perform DoH queries][added: encryption: Use encrypted name resolution] if the configured [removed: DNS ]servers support it. If they don't support it, try classic name resolution. Require [removed: DoH:][added: encryption:] Allow only [removed: DoH][added: encrypted] name resolution. If there are no [removed: DoH capable ][added: configured ]DNS servers [removed: configured,][added: that handle encryption,] name resolution will fail. [added: In addition to the generic encryption policy, additional policies can be configured at the individual protocol level. For example, in order to force DoT name resolution only, a combination of "Require encryption" and "Block DoH" would be needed (vice versa to force DoH). For the example above, it is the admin's responsibility to ensure that if DoT is forced, there are valid DoT servers configured on the machine (vice versa for DoH). ]If you disable this policy setting, or if you do not configure this policy setting, [removed: computers][added: the DNS client] will use locally configured settings. DDR (Discovery of Designated Resolvers) plaintext traffic [removed: is][added: will be] allowed as it is necessary for auto-discovering [removed: DoH][added: encryption] settings.

[removed: Set this policy ][added: Specifies ]to restrict peer selection [removed: via][added: using the] selected [removed: option. Options available are: ][added: method, in addition to the DownloadMode policy. ]0 = [removed: NAT.][added: None] 1 = Subnet mask[removed: .] 2 = Local discovery [removed: (DNS-SD). The default value has changed from 0 (no restriction) to 1 (restrict to the subnet). These options apply to both Download Mode LAN (1) and Group (2).][added: (DNS-SD)]

This policy setting allows you to prevent Windows from [removed: retrieving device metadata from the Internet. ][added: downloading applications associated with device metadata. ]If you enable this policy setting, Windows does not [removed: retrieve][added: download applications associated with] device metadata for installed [removed: devices from the Internet. ][added: devices. ]This policy setting overrides the setting in the Device Installation Settings dialog box (Control Panel > System and Security > System > Advanced System Settings > Hardware tab). If you disable or do not configure this policy setting, the setting in the Device Installation Settings dialog box controls whether Windows [removed: retrieves device metadata from the Internet.][added: downloads applications associated with device metadata.]