Windows 11: 23H2 · 1.0 to 25H2 · 1.0

This policy controls the auto[removed: ][added: -]update interval for package-based sources.[added: The default source for Windows Package Manager is configured such that an index of the packages is cached on the local machine. The index is downloaded when a user invokes a command, and the interval has passed.] If you disable or do not configure this setting, the default interval or the value specified in [removed: settings will be used by the Windows Package Manager.][added: the Windows Package Manager settings will be used.] If you enable this setting, the number of minutes specified will be used by the Windows Package Manager.

[removed: This policy allows you to specify ][added: Specifies ]how your client(s) can discover Microsoft Connected Cache servers dynamically. [removed: Options available are: 0 = Disable DNS-SD. ]1 = DHCP Option 235[removed: . ] 2 = DHCP Option 235 [removed: Force. If this policy is not configured, the client will attempt to automatically find a cache server using DNS-SD. If set to 0, the client will not use DNS-SD to automatically find a cache server. If set to 1 or 2, the client will query DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if configured.][added: Force]

This policy setting allows you to manage the deployment of [removed: Windows][added: packaged Microsoft] Store apps when the user is signed in using a special profile. Special profiles are the following user profiles, where changes are discarded after the user signs off: Roaming user profiles to which the "Delete cached copies of roaming profiles" Group Policy setting applies Mandatory user profiles and super-mandatory profiles, which are created by an administrator Temporary user profiles, which are created when an error prevents the correct profile from loading User profiles for the Guest account and members of the Guests group If you enable this policy setting, Group Policy allows deployment operations (adding, registering, staging, updating, or removing an app package) of [removed: Windows][added: packaged Microsoft] Store apps when using a special profile. If you disable or do not configure this policy setting, Group Policy blocks deployment operations of [removed: Windows][added: packaged Microsoft] Store apps when using a special profile.

This policy setting allows you to manage the installation of trusted line-of-business (LOB) or developer-signed [removed: Windows][added: packaged Microsoft] Store apps. If you enable this policy setting, you can install any LOB or developer-signed [removed: Windows][added: packaged Microsoft] Store app (which must be signed with a certificate chain that can be successfully validated by the local computer). If you disable or do not configure this policy setting, you cannot install LOB or developer-signed [removed: Windows][added: packaged Microsoft] Store apps.

Manages a sideloaded apps' ability to auto-update in the background.[removed: ] If you enable this policy, sideloaded apps will not auto-update in the background. If you disable this policy, sideloaded apps will auto-update in the background. Default is 'disabled' (key not present).

[removed: Disallow][added: Specify to disallow] downloads from Microsoft Connected Cache servers when the device connects via VPN. [removed: By default,][added: When unchecked] the device is allowed to download from Microsoft Connected Cache when connected via VPN.[added: Check the box to block these downloads.]

Manages a sideloaded apps' ability to auto-update in the background on a metered network.[removed: ] If you enable this policy, sideloaded apps will not auto-update in the background on a metered network. If you disable this policy, sideloaded apps will auto-update in the background on a metered network. Default is 'disabled' (key not present).

Specifies the [removed: download ]method that Delivery Optimization can use [removed: in downloads of Windows Updates, Apps and App updates. The following list shows the supported values: ][added: to download content on behalf of various Microsoft products. ]0 = HTTP only, no peering[removed: . ] 1 = HTTP blended with peering behind the same NAT[removed: . ] 2 = HTTP blended with peering across a private [removed: group. Peering occurs on devices in the same Active Directory Site (if exist) or the same domain by default. When this option is selected, peering will cross NATs. To create a custom ]group[removed: use Group ID in combination with Mode 2. ][added: ]3 = HTTP blended with Internet [removed: Peering. ][added: peering ]99 = [removed: Simple download mode with][added: HTTP only, no peering,] no [removed: peering. Delivery Optimization downloads using HTTP only and does not attempt to contact the Delivery Optimization ][added: use of DO ]cloud service[removed: s. ] 100 = Bypass [removed: mode. Windows 10: Do not use Delivery Optimization and use BITS instead. ][added: mode, deprecated in ]Windows [removed: 11: Deprecated, use Simple mode instead.][added: 11]

[removed: Group ID must be set as a GUID. This Policy specifies ][added: Specifies ]an arbitrary group ID that the device belongs to.[removed: Use this if you need to create a single group for Local Network Peering for branches that are on different domains or are not on the same LAN. Note: this is a best effort optimization and should not ][added: A GUID must ]be [removed: relied on for an authentication of identity.][added: used.]

This policy setting lets you control whether [removed: Windows][added: packaged Microsoft] Store apps can open files using the default desktop app for a file type. Because desktop apps run at a higher integrity level than [removed: Windows][added: packaged Microsoft] Store apps, there is a risk that a [removed: Windows][added: packaged Microsoft] Store app might compromise the system by opening a file in the default desktop app for a file type. If you enable this policy setting, [removed: Windows][added: packaged Microsoft] Store apps cannot open files in the default desktop app for a file type; they can open files only in other [removed: Windows][added: packaged Microsoft] Store apps. If you disable or do not configure this policy setting, [removed: Windows][added: packaged Microsoft] Store apps can open files in the default desktop app for a file type.

This policy setting lets you control whether [removed: Windows][added: packaged Microsoft] Store apps can open URIs using the default desktop app for a URI scheme. Because desktop apps run at a higher integrity level than [removed: Windows][added: packaged Microsoft] Store apps, there is a risk that a URI scheme launched by a [removed: Windows][added: packaged Microsoft] Store app might compromise the system by launching a desktop app. If you enable this policy setting, [removed: Windows][added: packaged Microsoft] Store apps cannot open URIs in the default desktop app for a URI scheme; they can open URIs only in other [removed: Windows][added: packaged Microsoft] Store apps. If you disable or do not configure this policy setting, [removed: Windows][added: packaged Microsoft] Store apps can open URIs in the default desktop app for a URI scheme. Note: Enabling this policy setting does not block [removed: Windows][added: packaged Microsoft] Store apps from opening the default desktop app for the http, https, and mailto URI schemes. The handlers for these URI schemes are hardened against URI-based vulnerabilities from untrusted sources, reducing the associated risk.

This policy setting lets you control whether Microsoft accounts are optional for [removed: Windows][added: packaged Microsoft] Store apps that require an account to sign in. This policy only affects [removed: Windows][added: packaged Microsoft] Store apps that support it. If you enable this policy setting, [removed: Windows][added: packaged Microsoft] Store apps that typically require a Microsoft account to sign in will allow users to sign in with an enterprise account instead. If you disable or do not configure this policy setting, users will need to sign in with a Microsoft account.