Policy CSP - ADMX_WindowsExplorer
Tip
This CSP contains ADMX-backed policies which require a special SyncML format to enable or disable. You must specify the data type in the SyncML as <Format>chr</Format>
. For details, see Understanding ADMX-backed policies.
The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.
CheckSameSourceAndTargetForFRAndDFS
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/CheckSameSourceAndTargetForFRAndDFS
This policy setting allows you to prevent data loss when you change the target location for Folder Redirection, and the new and old targets point to the same network share, but have different network paths.
If you enable this policy setting, Folder Redirection creates a temporary file in the old location in order to verify that new and old locations point to the same network share. If both new and old locations point to the same share, the target path is updated and files aren't copied or deleted. The temporary file is deleted.
If you disable or don't configure this policy setting, Folder Redirection doesn't create a temporary file and functions as if both new and old locations point to different shares when their network paths are different.
Note
If the paths point to different network shares, this policy setting isn't required. If the paths point to the same network share, any data contained in the redirected folders is deleted if this policy setting isn't enabled.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | CheckSameSourceAndTargetForFRAndDFS |
Friendly Name | Verify old and new Folder Redirection targets point to the same share before redirecting |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | CheckSameSourceAndTargetForFRAndDFS |
ADMX File Name | WindowsExplorer.admx |
ClassicShell
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ClassicShell
This setting allows an administrator to revert specific Windows Shell behavior to classic Shell behavior.
- If you enable this setting, users can't configure their system to open items by single-clicking (such as in Mouse in Control Panel). As a result, the user interface looks and operates like the interface for Windows NT 4.0, and users can't restore the new features.
Enabling this policy will also turn off the preview pane and set the folder options for File Explorer to Use classic folders view and disable the users ability to change these options.
- If you disable or not configure this policy, the default File Explorer behavior is applied to the user.
Note
In operating systems earlier than Windows Vista, enabling this policy will also disable the Active Desktop and Web view. This setting will also take precedence over the "Enable Active Desktop" setting. If both policies are enabled, Active Desktop is disabled.
Also, see the "Disable Active Desktop" setting in User Configuration\Administrative Templates\Desktop\Active Desktop and the "Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon" setting in User Configuration\Administrative Templates\Windows Components\File Explorer.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ClassicShell |
Friendly Name | Turn on Classic Shell |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | ClassicShell |
ADMX File Name | WindowsExplorer.admx |
ConfirmFileDelete
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ConfirmFileDelete
Allows you to have File Explorer display a confirmation dialog whenever a file is deleted or moved to the Recycle Bin.
If you enable this setting, a confirmation dialog is displayed when a file is deleted or moved to the Recycle Bin by the user.
If you disable or don't configure this setting, the default behavior of not displaying a confirmation dialog occurs.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ConfirmFileDelete |
Friendly Name | Display confirmation dialog when deleting files |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | ConfirmFileDelete |
ADMX File Name | WindowsExplorer.admx |
DefaultLibrariesLocation
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DefaultLibrariesLocation
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DefaultLibrariesLocation
This policy setting allows you to specify a location where all default Library definition files for users/machines reside.
If you enable this policy setting, administrators can specify a path where all default Library definition files for users reside. The user won't be allowed to make changes to these Libraries from the UI. On every logon, the policy settings are verified and Libraries for the user are updated or changed according to the path defined.
If you disable or don't configure this policy setting, no changes are made to the location of the default Library definition files.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DefaultLibrariesLocation |
Friendly Name | Location where all default Library definition files for users/machines reside. |
Location | Computer and User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\Explorer |
ADMX File Name | WindowsExplorer.admx |
DisableBindDirectlyToPropertySetStorage
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableBindDirectlyToPropertySetStorage
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableBindDirectlyToPropertySetStorage
Changes the behavior of IShellFolder::BindToObject for IID_IPropertySetStorage to not bind directly to the IPropertySetStorage implementation, and to include the intermediate layers provided by the Property System. This behavior is consistent with Windows Vista's behavior in this scenario.
This disables access to user-defined properties, and properties stored in NTFS secondary streams.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DisableBindDirectlyToPropertySetStorage |
Friendly Name | Disable binding directly to IPropertySetStorage without intermediate layers. |
Location | Computer and User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | DisableBindDirectlyToPropertySetStorage |
ADMX File Name | WindowsExplorer.admx |
DisableIndexedLibraryExperience
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableIndexedLibraryExperience
This policy setting allows you to turn off Windows Libraries features that need indexed file metadata to function properly.
- If you enable this policy, some Windows Libraries features will be turned off to better handle included folders that have been redirected to non-indexed network locations.
Setting this policy will:
- Disable all Arrangement views except for "By Folder"
- Disable all Search filter suggestions other than "Date Modified" and "Size"
- Disable view of file content snippets in Content mode when search results are returned
- Disable ability to stack in the Context menu and Column headers
- Exclude Libraries from the scope of Start search.
This policy won't enable users to add unsupported locations to Libraries.
If you enable this policy, Windows Libraries features that rely on indexed file data will be disabled.
If you disable or don't configure this policy, all default Windows Libraries features will be enabled.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DisableIndexedLibraryExperience |
Friendly Name | Turn off Windows Libraries features that rely on indexed file data |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | DisableIndexedLibraryExperience |
ADMX File Name | WindowsExplorer.admx |
DisableKnownFolders
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableKnownFolders
This policy setting allows you to specify a list of known folders that should be disabled. Disabling a known folder will prevent the underlying file or directory from being created via the known folder API. If the folder exists before the policy is applied, the folder must be manually deleted since the policy only blocks the creation of the folder.
You can specify a known folder using its known folder id or using its canonical name. For example, the Sample Videos known folder can be disabled by specifying {440fcffd-a92b-4739-ae1a-d4a54907c53f} or SampleVideos.
Note
Disabling a known folder can introduce application compatibility issues in applications that depend on the existence of the known folder.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DisableKnownFolders |
Friendly Name | Disable Known Folders |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | DisableKnownFolders |
ADMX File Name | WindowsExplorer.admx |
DisableMotWOnInsecurePathCopy
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableMotWOnInsecurePathCopy
This policy setting determines the application of the Mark of the Web tag to files sourced from insecure locations.
If you enable this policy setting, files copied from unsecure sources won't be tagged with the Mark of the Web.
If you disable or don't configure this policy setting, files copied from unsecure sources will be tagged with the appropriate Mark of the Web.
Note
Failure to tag files from unsecure sources with the Mark of the Web can expose users' computers to security risks.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DisableMotWOnInsecurePathCopy |
Friendly Name | Do not apply the Mark of the Web tag to files copied from insecure sources |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | DisableMotWOnInsecurePathCopy |
ADMX File Name | WindowsExplorer.admx |
DisableSearchBoxSuggestions
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/DisableSearchBoxSuggestions
Disables suggesting recent queries for the Search Box and prevents entries into the Search Box from being stored in the registry for future references.
File Explorer shows suggestion pop-ups as users type into the Search Box. These suggestions are based on their past entries into the Search Box.
Note
If you enable this policy, File Explorer won't show suggestion pop-ups as users type into the Search Box, and it won't store Search Box entries into the registry for future references. If the user types a property, values that match this property will be shown but no data will be saved in the registry or re-shown on subsequent uses of the search box.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | DisableSearchBoxSuggestions |
Friendly Name | Turn off display of recent search entries in the File Explorer search box |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | DisableSearchBoxSuggestions |
ADMX File Name | WindowsExplorer.admx |
EnableShellShortcutIconRemotePath
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/EnableShellShortcutIconRemotePath
This policy setting determines whether remote paths can be used for file shortcut (.lnk file) icons.
If you enable this policy setting, file shortcut icons are allowed to be obtained from remote paths.
If you disable or don't configure this policy setting, file shortcut icons that use remote paths are prevented from being displayed.
Note
Allowing the use of remote paths in file shortcut icons can expose users' computers to security risks.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | EnableShellShortcutIconRemotePath |
Friendly Name | Allow the use of remote paths in file shortcut icons |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | EnableShellShortcutIconRemotePath |
ADMX File Name | WindowsExplorer.admx |
EnableSmartScreen
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/EnableSmartScreen
This policy allows you to turn Windows Defender SmartScreen on or off. SmartScreen helps protect PCs by warning users before running potentially malicious programs downloaded from the Internet. This warning is presented as an interstitial dialog shown before running an app that has been downloaded from the Internet and is unrecognized or known to be malicious. No dialog is shown for apps that don't appear to be suspicious.
Some information is sent to Microsoft about files and programs run on PCs with this feature enabled.
If you enable this policy, SmartScreen will be turned on for all users. Its behavior can be controlled by the following options:
Warn and prevent bypass
Warn.
If you enable this policy with the "Warn and prevent bypass" option, SmartScreen's dialogs won't present the user with the option to disregard the warning and run the app. SmartScreen will continue to show the warning on subsequent attempts to run the app.
If you enable this policy with the "Warn" option, SmartScreen's dialogs will warn the user that the app appears suspicious, but will permit the user to disregard the warning and run the app anyway. SmartScreen won't warn the user again for that app if the user tells SmartScreen to run the app.
If you disable this policy, SmartScreen will be turned off for all users. Users won't be warned if they try to run suspicious apps from the Internet.
If you don't configure this policy, SmartScreen will be enabled by default, but users may change their settings.
For more information, see Microsoft Defender SmartScreen.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | EnableSmartScreen |
Friendly Name | Configure Windows Defender SmartScreen |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\System |
Registry Value Name | EnableSmartScreen |
ADMX File Name | WindowsExplorer.admx |
EnforceShellExtensionSecurity
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/EnforceShellExtensionSecurity
This setting is designed to ensure that shell extensions can operate on a per-user basis. If you enable this setting, Windows is directed to only run those shell extensions that have either been approved by an administrator or that won't impact other users of the machine.
A shell extension only runs if there is an entry in at least one of the following locations in registry.
For shell extensions that have been approved by the administrator and are available to all users of the computer, there must be an entry at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved.
For shell extensions to run on a per-user basis, there must be an entry at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | EnforceShellExtensionSecurity |
Friendly Name | Allow only per user or approved shell extensions |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | EnforceShellExtensionSecurity |
ADMX File Name | WindowsExplorer.admx |
ExplorerRibbonStartsMinimized
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ExplorerRibbonStartsMinimized
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ExplorerRibbonStartsMinimized
This policy setting allows you to specify whether the ribbon appears minimized or in full when new File Explorer windows are opened.
If you enable this policy setting, you can set how the ribbon appears the first time users open File Explorer and whenever they open new windows.
If you disable or don't configure this policy setting, users can choose how the ribbon appears when they open new windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ExplorerRibbonStartsMinimized |
Friendly Name | Start File Explorer with ribbon minimized |
Location | Computer and User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | ExplorerRibbonStartsMinimized |
ADMX File Name | WindowsExplorer.admx |
HideContentViewModeSnippets
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/HideContentViewModeSnippets
This policy setting allows you to turn off the display of snippets in Content view mode.
If you enable this policy setting, File Explorer won't display snippets in Content view mode.
If you disable or don't configure this policy setting, File Explorer shows snippets in Content view mode by default.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | HideContentViewModeSnippets |
Friendly Name | Turn off the display of snippets in Content view mode |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | HideContentViewModeSnippets |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_Internet
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Internet
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Internet
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_Internet |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Internet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_InternetLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_InternetLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_InternetLockdown
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_InternetLockdown |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Internet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\3 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_Intranet
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Intranet
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Intranet
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_Intranet |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Intranet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_IntranetLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_IntranetLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_IntranetLockdown
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_IntranetLockdown |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Intranet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\1 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_LocalMachine
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_LocalMachine
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_LocalMachine
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_LocalMachine |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Local Machine Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\0 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_LocalMachineLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_LocalMachineLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_LocalMachineLockdown
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_LocalMachineLockdown |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Local Machine Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\0 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_Restricted
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Restricted
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Restricted
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can't preview items or get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_Restricted |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Restricted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\4 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_RestrictedLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_RestrictedLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_RestrictedLockdown
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can't preview items or get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_RestrictedLockdown |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Restricted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\4 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_Trusted
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Trusted
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_Trusted
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_Trusted |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Trusted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchPreview_TrustedLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_TrustedLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchPreview_TrustedLockdown
This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it's the zone of the thumbnail that's checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that's different than the location of the item.
If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
If you don't configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
Changes to this setting may not be applied until the user logs off from Windows.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchPreview_TrustedLockdown |
Friendly Name | Allow previewing and custom thumbnails of OpenSearch query results in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Trusted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\2 |
Registry Value Name | 180F |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_Internet
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Internet
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Internet
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_Internet |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Internet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_InternetLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_InternetLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_InternetLockdown
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_InternetLockdown |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Internet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\3 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_Intranet
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Intranet
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Intranet
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_Intranet |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Intranet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_IntranetLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_IntranetLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_IntranetLockdown
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_IntranetLockdown |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Intranet Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\1 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_LocalMachine
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_LocalMachine
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_LocalMachine
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_LocalMachine |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Local Machine Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\0 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_LocalMachineLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_LocalMachineLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_LocalMachineLockdown
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_LocalMachineLockdown |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Local Machine Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\0 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_Restricted
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Restricted
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Restricted
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can't perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_Restricted |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Restricted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\4 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_RestrictedLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_RestrictedLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_RestrictedLockdown
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can't perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_RestrictedLockdown |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Restricted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\4 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_Trusted
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Trusted
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_Trusted
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_Trusted |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Trusted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
IZ_Policy_OpenSearchQuery_TrustedLockdown
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_TrustedLockdown
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/IZ_Policy_OpenSearchQuery_TrustedLockdown
This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
If you don't configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | IZ_Policy_OpenSearchQuery_TrustedLockdown |
Friendly Name | Allow OpenSearch queries in File Explorer |
Location | Computer and User Configuration |
Path | IZ_SecurityPage > Locked-Down Trusted Sites Zone |
Registry Key Name | Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\2 |
Registry Value Name | 180E |
ADMX File Name | WindowsExplorer.admx |
LinkResolveIgnoreLinkInfo
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/LinkResolveIgnoreLinkInfo
This policy setting determines whether Windows traces shortcuts back to their sources when it can't find the target on the user's system.
Shortcut files typically include an absolute path to the original target file as well as the relative path to the current target file. When the system can't find the file in the current target path, then, by default, it searches for the target in the original path. If the shortcut has been copied to a different computer, the original path might lead to a network computer, including external resources, such as an Internet server.
If you enable this policy setting, Windows only searches the current target path. It doesn't search for the original path even when it can't find the target file in the current target path.
If you disable or don't configure this policy setting, Windows searches for the original path when it can't find the target file in the current target path.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | LinkResolveIgnoreLinkInfo |
Friendly Name | Do not track Shell shortcuts during roaming |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | LinkResolveIgnoreLinkInfo |
ADMX File Name | WindowsExplorer.admx |
MaxRecentDocs
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/MaxRecentDocs
"This policy setting allows you to set the maximum number of shortcuts the system can display in the Recent Items menu on the Start menu.
The Recent Items menu contains shortcuts to the nonprogram files the user has most recently opened.
If you enable this policy setting, the system displays the number of shortcuts specified by the policy setting.
If you disable or don't configure this policy setting, by default, the system displays shortcuts to the 10 most recently opened documents".
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | MaxRecentDocs |
Friendly Name | Maximum number of recent documents |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
ADMX File Name | WindowsExplorer.admx |
NoBackButton
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoBackButton
Hide the Back button in the Open dialog box.
This policy setting lets you remove new features added in Microsoft Windows 2000 Professional, so the Open dialog box appears as it did in Windows NT 4.0 and earlier. This policy setting affects only programs that use the standard Open dialog box provided to developers of Windows programs.
If you enable this policy setting, the Back button is removed from the standard Open dialog box.
If you disable or don't configure this policy setting, the Back button is displayed for any standard Open dialog box.
To see an example of the standard Open dialog box, start Notepad and, on the File menu, click Open.
Note
In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting doesn't apply to the new Windows Vista common dialog box style. Also, third-party applications with Windows 2000 or later certification to are required to adhere to this policy setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoBackButton |
Friendly Name | Hide the common dialog back button |
Location | User Configuration |
Path | WindowsComponents > File Explorer > Common Open File Dialog |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Comdlg32 |
Registry Value Name | NoBackButton |
ADMX File Name | WindowsExplorer.admx |
NoCacheThumbNailPictures
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoCacheThumbNailPictures
This policy setting allows you to turn off caching of thumbnail pictures.
If you enable this policy setting, thumbnail views aren't cached.
If you disable or don't configure this policy setting, thumbnail views are cached.
Note
For shared corporate workstations or computers where security is a top concern, you should enable this policy setting to turn off the thumbnail view cache, because the thumbnail cache can be read by everyone.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoCacheThumbNailPictures |
Friendly Name | Turn off caching of thumbnail pictures |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoThumbnailCache |
ADMX File Name | WindowsExplorer.admx |
NoCDBurning
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoCDBurning
This policy setting allows you to remove CD Burning features. File Explorer allows you to create and modify re-writable CDs if you have a CD writer connected to your PC.
If you enable this policy setting, all features in the File Explorer that allow you to use your CD writer are removed.
If you disable or don't configure this policy setting, users are able to use the File Explorer CD burning features.
Note
This policy setting doesn't prevent users from using third-party applications to create or modify CDs using a CD writer.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoCDBurning |
Friendly Name | Remove CD Burning features |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoCDBurning |
ADMX File Name | WindowsExplorer.admx |
NoChangeAnimation
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoChangeAnimation
This policy setting allows you to prevent users from enabling or disabling minor animations in the operating system for the movement of windows, menus, and lists.
- If you enable this policy setting, the "Use transition effects for menus and tooltips" option in Display in Control Panel is disabled, and can't be toggled by users.
Effects, such as animation, are designed to enhance the user's experience but might be confusing or distracting to some users.
- If you disable or don't configure this policy setting, users are allowed to turn on or off these minor system animations using the "Use transition effects for menus and tooltips" option in Display in Control Panel.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoChangeAnimation |
Friendly Name | Remove UI to change menu animation setting |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoChangeAnimation |
ADMX File Name | WindowsExplorer.admx |
NoChangeKeyboardNavigationIndicators
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoChangeKeyboardNavigationIndicators
Disables the "Hide keyboard navigation indicators until I use the ALT key" option in Display in Control Panel.
When this Display Properties option is selected, the underlining that indicates a keyboard shortcut character (hot key) doesn't appear on menus until you press ALT.
Effects, such as transitory underlines, are designed to enhance the user's experience but might be confusing or distracting to some users.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoChangeKeyboardNavigationIndicators |
Friendly Name | Remove UI to change keyboard navigation indicator setting |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoChangeKeyboardNavigationIndicators |
ADMX File Name | WindowsExplorer.admx |
NoDFSTab
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoDFSTab
This policy setting allows you to remove the DFS tab from File Explorer.
- If you enable this policy setting, the DFS (Distributed File System) tab is removed from File Explorer and from other programs that use the File Explorer browser, such as My Computer. As a result, users can't use this tab to view or change the properties of the DFS shares available from their computer.
This policy setting doesn't prevent users from using other methods to configure DFS.
- If you disable or don't configure this policy setting, the DFS tab is available.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoDFSTab |
Friendly Name | Remove DFS tab |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoDFSTab |
ADMX File Name | WindowsExplorer.admx |
NoDrives
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoDrives
This policy setting allows you to hide these specified drives in My Computer.
This policy setting allows you to remove the icons representing selected hard drives from My Computer and File Explorer. Also, the drive letters representing the selected drives don't appear in the standard Open dialog box.
- If you enable this policy setting, select a drive or combination of drives in the drop-down list.
Note
This policy setting removes the drive icons. Users can still gain access to drive contents by using other methods, such as by typing the path to a directory on the drive in the Map Network Drive dialog box, in the Run dialog box, or in a command window.
Also, this policy setting doesn't prevent users from using programs to access these drives or their contents. And, it doesn't prevent users from using the Disk Management snap-in to view and change drive characteristics.
- If you disable or don't configure this policy setting, all drives are displayed, or select the "Do not restrict drives" option in the drop-down list.
Also, see the "Prevent access to drives from My Computer" policy setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoDrives |
Friendly Name | Hide these specified drives in My Computer |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
ADMX File Name | WindowsExplorer.admx |
NoEntireNetwork
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoEntireNetwork
Removes all computers outside of the user's workgroup or local domain from lists of network resources in File Explorer and Network Locations.
If you enable this setting, the system removes the Entire Network option and the icons representing networked computers from Network Locations and from the browser associated with the Map Network Drive option.
This setting doesn't prevent users from viewing or connecting to computers in their workgroup or domain. It also doesn't prevent users from connecting to remote computers by other commonly used methods, such as by typing the share name in the Run dialog box or the Map Network Drive dialog box.
To remove computers in the user's workgroup or domain from lists of network resources, use the "No Computers Near Me in Network Locations" setting.
Note
It's a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoEntireNetwork |
Friendly Name | No Entire Network in Network Locations |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Network |
Registry Value Name | NoEntireNetwork |
ADMX File Name | WindowsExplorer.admx |
NoFileMenu
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoFileMenu
Removes the File menu from My Computer and File Explorer.
This setting doesn't prevent users from using other methods to perform tasks available on the File menu.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoFileMenu |
Friendly Name | Remove File menu from File Explorer |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoFileMenu |
ADMX File Name | WindowsExplorer.admx |
NoFileMRU
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoFileMRU
Removes the list of most recently used files from the Open dialog box.
If you disable this setting or don't configure it, the "File name" field includes a drop-down list of recently used files.
If you enable this setting, the "File name" field is a simple text box. Users must browse directories to find a file or type a file name in the text box.
This setting, and others in this folder, lets you remove new features added in Windows 2000 Professional, so that the Open dialog box looks like it did in Windows NT 4.0 and earlier. These policies only affect programs that use the standard Open dialog box provided to developers of Windows programs.
To see an example of the standard Open dialog box, start Wordpad and, on the File menu, click Open.
Note
In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting doesn't apply to the new Windows Vista common dialog box style. It's a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoFileMRU |
Friendly Name | Hide the dropdown list of recent files |
Location | User Configuration |
Path | WindowsComponents > File Explorer > Common Open File Dialog |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Comdlg32 |
Registry Value Name | NoFileMru |
ADMX File Name | WindowsExplorer.admx |
NoFolderOptions
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoFolderOptions
This policy setting allows you to prevent users from accessing Folder Options through the View tab on the ribbon in File Explorer.
Folder Options allows users to change the way files and folders open, what appears in the navigation pane, and other advanced view settings.
If you enable this policy setting, users will receive an error message if they tap or click the Options button or choose the Change folder and search options command, and they won't be able to open Folder Options.
If you disable or don't configure this policy setting, users can open Folder Options from the View tab on the ribbon.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoFolderOptions |
Friendly Name | Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoFolderOptions |
ADMX File Name | WindowsExplorer.admx |
NoHardwareTab
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoHardwareTab
Removes the Hardware tab.
This setting removes the Hardware tab from Mouse, Keyboard, and Sounds and Audio Devices in Control Panel. It also removes the Hardware tab from the Properties dialog box for all local drives, including hard drives, floppy disk drives, and CD-ROM drives. As a result, users can't use the Hardware tab to view or change the device list or device properties, or use the Troubleshoot button to resolve problems with the device.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoHardwareTab |
Friendly Name | Remove Hardware tab |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoHardwareTab |
ADMX File Name | WindowsExplorer.admx |
NoManageMyComputerVerb
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoManageMyComputerVerb
Removes the Manage item from the File Explorer context menu. This context menu appears when you right-click File Explorer or My Computer.
The Manage item opens Computer Management (Compmgmt.msc), a console tool that includes many of the primary Windows 2000 administrative tools, such as Event Viewer, Device Manager, and Disk Management. You must be an administrator to use many of the features of these tools.
This setting doesn't remove the Computer Management item from the Start menu (Start, Programs, Administrative Tools, Computer Management), nor does it prevent users from using other methods to start Computer Management.
Tip
To hide all context menus, use the "Remove File Explorer's default context menu" setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoManageMyComputerVerb |
Friendly Name | Hides the Manage item on the File Explorer context menu |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoManageMyComputerVerb |
ADMX File Name | WindowsExplorer.admx |
NoMyComputerSharedDocuments
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoMyComputerSharedDocuments
This policy setting allows you to remove the Shared Documents folder from My Computer.
When a Windows client is in a workgroup, a Shared Documents icon appears in the File Explorer Web view under "Other Places" and also under "Files Stored on This Computer" in My Computer. Using this policy setting, you can choose not to have these items displayed.
If you enable this policy setting, the Shared Documents folder isn't displayed in the Web view or in My Computer.
If you disable or don't configure this policy setting, the Shared Documents folder is displayed in Web view and also in My Computer when the client is part of a workgroup.
Note
The ability to remove the Shared Documents folder via Group Policy is only available on Windows XP Professional.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoMyComputerSharedDocuments |
Friendly Name | Remove Shared Documents from My Computer |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoSharedDocuments |
ADMX File Name | WindowsExplorer.admx |
NoNetConnectDisconnect
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoNetConnectDisconnect
Prevents users from using File Explorer or Network Locations to map or disconnect network drives.
If you enable this setting, the system removes the Map Network Drive and Disconnect Network Drive commands from the toolbar and Tools menus in File Explorer and Network Locations and from menus that appear when you right-click the File Explorer or Network Locations icons.
This setting doesn't prevent users from connecting to another computer by typing the name of a shared folder in the Run dialog box.
Note
This setting was documented incorrectly on the Explain tab in Group Policy for Windows 2000. The Explain tab states incorrectly that this setting prevents users from connecting and disconnecting drives.
Note
It's a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoNetConnectDisconnect |
Friendly Name | Remove "Map Network Drive" and "Disconnect Network Drive" |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoNetConnectDisconnect |
ADMX File Name | WindowsExplorer.admx |
NoNewAppAlert
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoNewAppAlert
This policy removes the end-user notification for new application associations. These associations are based on file types (e.g. *.txt) or protocols (e.g. http:)
If this group policy is enabled, no notifications will be shown. If the group policy isn't configured or disabled, notifications will be shown to the end user if a new application has been installed that can handle the file type or protocol association that was invoked.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoNewAppAlert |
Friendly Name | Do not show the 'new application installed' notification |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | NoNewAppAlert |
ADMX File Name | WindowsExplorer.admx |
NoPlacesBar
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoPlacesBar
Removes the shortcut bar from the Open dialog box.
This setting, and others in this folder, lets you remove new features added in Windows 2000 Professional, so that the Open dialog box looks like it did in Windows NT 4.0 and earlier. These policies only affect programs that use the standard Open dialog box provided to developers of Windows programs.
To see an example of the standard Open dialog box, start Wordpad and, on the File menu, click Open.
Note
In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting doesn't apply to the new Windows Vista common dialog box style. It's a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoPlacesBar |
Friendly Name | Hide the common dialog places bar |
Location | User Configuration |
Path | WindowsComponents > File Explorer > Common Open File Dialog |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Comdlg32 |
Registry Value Name | NoPlacesBar |
ADMX File Name | WindowsExplorer.admx |
NoRecycleFiles
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoRecycleFiles
When a file or folder is deleted in File Explorer, a copy of the file or folder is placed in the Recycle Bin. Using this setting, you can change this behavior.
If you enable this setting, files and folders that are deleted using File Explorer won't be placed in the Recycle Bin and will therefore be permanently deleted.
If you disable or don't configure this setting, files and folders deleted using File Explorer will be placed in the Recycle Bin.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoRecycleFiles |
Friendly Name | Do not move deleted files to the Recycle Bin |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoRecycleFiles |
ADMX File Name | WindowsExplorer.admx |
NoRunAsInstallPrompt
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoRunAsInstallPrompt
Prevents users from submitting alternate logon credentials to install a program.
This setting suppresses the "Install Program As Other User" dialog box for local and network installations. This dialog box, which prompts the current user for the user name and password of an administrator, appears when users who aren't administrators try to install programs locally on their computers. This setting allows administrators who have logged-on as regular users to install programs without logging off and logging on again using their administrator credentials.
Many programs can be installed only by an administrator.
If you enable this setting and a user doesn't have sufficient permissions to install a program, the installation continues with the current user's logon credentials. As a result, the installation might fail, or it might complete but not include all features. Or, it might appear to complete successfully, but the installed program might not operate correctly.
If you disable this setting or don't configure it, the "Install Program As Other User" dialog box appears whenever users install programs locally on the computer.
By default, users aren't prompted for alternate logon credentials when installing programs from a network share. If enabled, this setting overrides the "Request credentials for network installations" setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoRunAsInstallPrompt |
Friendly Name | Do not request alternate credentials |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoRunasInstallPrompt |
ADMX File Name | WindowsExplorer.admx |
NoSearchInternetTryHarderButton
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoSearchInternetTryHarderButton
If you enable this policy, the "Internet" "Search again" link won't be shown when the user performs a search in the Explorer window.
If you disable this policy, there will be an "Internet" "Search again" link when the user performs a search in the Explorer window. This button launches a search in the default browser with the search terms.
If you don't configure this policy (default), there will be an "Internet" link when the user performs a search in the Explorer window.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoSearchInternetTryHarderButton |
Friendly Name | Remove the Search the Internet "Search again" link |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | NoSearchInternetTryHarderButton |
ADMX File Name | WindowsExplorer.admx |
NoSecurityTab
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoSecurityTab
Removes the Security tab from File Explorer.
If you enable this setting, users opening the Properties dialog box for all file system objects, including folders, files, shortcuts, and drives, won't be able to access the Security tab. As a result, users will be able to neither change the security settings nor view a list of all users that have access to the resource in question.
If you disable or don't configure this setting, users will be able to access the security tab.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoSecurityTab |
Friendly Name | Remove Security tab |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoSecurityTab |
ADMX File Name | WindowsExplorer.admx |
NoShellSearchButton
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoShellSearchButton
This policy setting allows you to remove the Search button from the File Explorer toolbar.
- If you enable this policy setting, the Search button is removed from the Standard Buttons toolbar that appears in File Explorer and other programs that use the File Explorer window, such as My Computer and Network Locations.
Enabling this policy setting doesn't remove the Search button or affect any search features of Internet browser windows, such as the Internet Explorer window.
- If you disable or don't configure this policy setting, the Search button is available from the File Explorer toolbar.
This policy setting doesn't affect the Search items on the File Explorer context menu or on the Start menu. To remove Search from the Start menu, use the "Remove Search menu from Start menu" policy setting (in User Configuration\Administrative Templates\Start Menu and Taskbar). To hide all context menus, use the "Remove File Explorer's default context menu" policy setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoShellSearchButton |
Friendly Name | Remove Search button from File Explorer |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoShellSearchButton |
ADMX File Name | WindowsExplorer.admx |
NoStrCmpLogical
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoStrCmpLogical
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoStrCmpLogical
This policy setting allows you to have file names sorted literally (as in Windows 2000 and earlier) rather than in numerical order.
If you enable this policy setting, File Explorer will sort file names by each digit in a file name (for example, 111 < 22 < 3).
If you disable or don't configure this policy setting, File Explorer will sort file names by increasing number value (for example, 3 < 22 < 111).
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoStrCmpLogical |
Friendly Name | Turn off numerical sorting in File Explorer |
Location | Computer and User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoStrCmpLogical |
ADMX File Name | WindowsExplorer.admx |
NoViewContextMenu
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoViewContextMenu
Removes shortcut menus from the desktop and File Explorer. Shortcut menus appear when you right-click an item.
If you enable this setting, menus don't appear when you right-click the desktop or when you right-click the items in File Explorer. This setting doesn't prevent users from using other methods to issue commands available on the shortcut menus.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoViewContextMenu |
Friendly Name | Remove File Explorer's default context menu |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoViewContextMenu |
ADMX File Name | WindowsExplorer.admx |
NoViewOnDrive
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoViewOnDrive
Prevents users from using My Computer to gain access to the content of selected drives.
If you enable this setting, users can browse the directory structure of the selected drives in My Computer or File Explorer, but they can't open folders and access the contents. Also, they can't use the Run dialog box or the Map Network Drive dialog box to view the directories on these drives.
To use this setting, select a drive or combination of drives from the drop-down list. To allow access to all drive directories, disable this setting or select the "Do not restrict drives" option from the drop-down list.
Note
The icons representing the specified drives still appear in My Computer, but if users double-click the icons, a message appears explaining that a setting prevents the action.
Also, this setting doesn't prevent users from using programs to access local and network drives. And, it doesn't prevent them from using the Disk Management snap-in to view and change drive characteristics.
Also, see the "Hide these specified drives in My Computer" setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoViewOnDrive |
Friendly Name | Prevent access to drives from My Computer |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
ADMX File Name | WindowsExplorer.admx |
NoWindowsHotKeys
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoWindowsHotKeys
Turn off Windows Key hotkeys.
Keyboards with a Windows key provide users with shortcuts to common shell features. For example, pressing the keyboard sequence Windows+R opens the Run dialog box; pressing Windows+E starts File Explorer. By using this setting, you can disable these Windows Key hotkeys.
If you enable this setting, the Windows Key hotkeys are unavailable.
If you disable or don't configure this setting, the Windows Key hotkeys are available.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoWindowsHotKeys |
Friendly Name | Turn off Windows Key hotkeys |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoWinKeys |
ADMX File Name | WindowsExplorer.admx |
NoWorkgroupContents
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/NoWorkgroupContents
This policy setting allows you to remove computers in the user's workgroup and domain from lists of network resources in File Explorer and Network Locations.
If you enable this policy setting, the system removes the "Computers Near Me" option and the icons representing nearby computers from Network Locations. This policy setting also removes these icons from the Map Network Drive browser.
If you disable or don't configure this policy setting, computers in the user's workgroup and domain appear in lists of network resources in File Explorer and Network Locations.
This policy setting doesn't prevent users from connecting to computers in their workgroup or domain by other commonly used methods, such as typing the share name in the Run dialog box or the Map Network Drive dialog box.
To remove network computers from lists of network resources, use the "No Entire Network in Network Locations" policy setting.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | NoWorkgroupContents |
Friendly Name | No Computers Near Me in Network Locations |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | NoComputersNearMe |
ADMX File Name | WindowsExplorer.admx |
PlacesBar
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/PlacesBar
Configures the list of items displayed in the Places Bar in the Windows File/Open dialog.
- If you enable this setting you can specify from 1 to 5 items to be displayed in the Places Bar.
The valid items you may display in the Places Bar are:
Shortcuts to a local folders -- (ex. C:\Windows)
Shortcuts to remote folders -- (\server\share)
FTP folders.
web folders.
Common Shell folders.
The list of Common Shell Folders that may be specified:
Desktop, Recent Places, Documents, Pictures, Music, Recently Changed, Attachments and Saved Searches.
- If you disable or don't configure this setting the default list of items will be displayed in the Places Bar.
Note
In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting doesn't apply to the new Windows Vista common dialog box style.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | PlacesBar |
Friendly Name | Items displayed in Places Bar |
Location | User Configuration |
Path | WindowsComponents > File Explorer > Common Open File Dialog |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\comdlg32\Placesbar |
ADMX File Name | WindowsExplorer.admx |
PromptRunasInstallNetPath
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/PromptRunasInstallNetPath
Prompts users for alternate logon credentials during network-based installations.
This setting displays the "Install Program As Other User" dialog box even when a program is being installed from files on a network computer across a local area network connection.
If you disable this setting or don't configure it, this dialog box appears only when users are installing programs from local media.
The "Install Program as Other User" dialog box prompts the current user for the user name and password of an administrator. This setting allows administrators who have logged-on as regular users to install programs without logging off and logging on again using their administrator credentials.
If the dialog box doesn't appear, the installation proceeds with the current user's permissions. If these permissions aren't sufficient, the installation might fail, or it might complete but not include all features. Or, it might appear to complete successfully, but the installed program might not operate correctly.
Note
If it's enabled, the "Do not request alternate credentials" setting takes precedence over this setting. When that setting is enabled, users aren't prompted for alternate logon credentials on any installation.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | PromptRunasInstallNetPath |
Friendly Name | Request credentials for network installations |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | PromptRunasInstallNetPath |
ADMX File Name | WindowsExplorer.admx |
RecycleBinSize
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/RecycleBinSize
Limits the percentage of a volume's disk space that can be used to store deleted files.
If you enable this setting, the user has a maximum amount of disk space that may be used for the Recycle Bin on their workstation.
If you disable or don't configure this setting, users can change the total amount of disk space used by the Recycle Bin.
Note
This setting is applied to all volumes.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | RecycleBinSize |
Friendly Name | Maximum allowed Recycle Bin size |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
ADMX File Name | WindowsExplorer.admx |
ShellProtocolProtectedModeTitle_1
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ShellProtocolProtectedModeTitle_1
This policy setting allows you to configure the amount of functionality that the shell protocol can have. When using the full functionality of this protocol, applications can open folders and launch files. The protected mode reduces the functionality of this protocol allowing applications to only open a limited set of folders. Applications aren't able to open files with this protocol when it's in the protected mode. It's recommended to leave this protocol in the protected mode to increase the security of Windows.
If you enable this policy setting the protocol is fully enabled, allowing the opening of folders and files.
If you disable this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
If you don't configure this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ShellProtocolProtectedModeTitle_1 |
Friendly Name | Turn off shell protocol protected mode |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | PreXPSP2ShellProtocolBehavior |
ADMX File Name | WindowsExplorer.admx |
ShellProtocolProtectedModeTitle_2
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ShellProtocolProtectedModeTitle_2
This policy setting allows you to configure the amount of functionality that the shell protocol can have. When using the full functionality of this protocol, applications can open folders and launch files. The protected mode reduces the functionality of this protocol allowing applications to only open a limited set of folders. Applications aren't able to open files with this protocol when it's in the protected mode. It's recommended to leave this protocol in the protected mode to increase the security of Windows.
If you enable this policy setting the protocol is fully enabled, allowing the opening of folders and files.
If you disable this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
If you don't configure this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ShellProtocolProtectedModeTitle_2 |
Friendly Name | Turn off shell protocol protected mode |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Explorer |
Registry Value Name | PreXPSP2ShellProtocolBehavior |
ADMX File Name | WindowsExplorer.admx |
ShowHibernateOption
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ShowHibernateOption
Shows or hides hibernate from the power options menu.
If you enable this policy setting, the hibernate option will be shown in the Power Options menu (as long as it's supported by the machine's hardware).
If you disable this policy setting, the hibernate option will never be shown in the Power Options menu.
If you don't configure this policy setting, users will be able to choose whether they want hibernate to show through the Power Options Control Panel.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ShowHibernateOption |
Friendly Name | Show hibernate in the power options menu |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | ShowHibernateOption |
ADMX File Name | WindowsExplorer.admx |
ShowSleepOption
Scope | Editions | Applicable OS |
---|---|---|
✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/ShowSleepOption
Shows or hides sleep from the power options menu.
If you enable this policy setting, the sleep option will be shown in the Power Options menu (as long as it's supported by the machine's hardware).
If you disable this policy setting, the sleep option will never be shown in the Power Options menu.
If you don't configure this policy setting, users will be able to choose whether they want sleep to show through the Power Options Control Panel.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | ShowSleepOption |
Friendly Name | Show sleep in the power options menu |
Location | Computer Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | ShowSleepOption |
ADMX File Name | WindowsExplorer.admx |
TryHarderPinnedLibrary
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/TryHarderPinnedLibrary
This policy setting allows up to five Libraries or Search Connectors to be pinned to the "Search again" links and the Start menu links. The "Search again" links at the bottom of the Search Results view allow the user to reconduct a search but in a different location. To add a Library or Search Connector link, specify the path of the . Library-ms or .searchConnector-ms file in the "Location" text box (for example, "C:\sampleLibrary. Library-ms" for the Documents library, or "C:\sampleSearchConnector.searchConnector-ms" for a Search Connector). The pinned link will only work if this path is valid and the location contains the specified . Library-ms or .searchConnector-ms file.
You can add up to five additional links to the "Search again" links at the bottom of results returned in File Explorer after a search is executed. These links will be shared between Internet search sites and Search Connectors/Libraries. Search Connector/Library links take precedence over Internet search links.
The first several links will also be pinned to the Start menu. A total of four links can be included on the Start menu. The "See more results" link will be pinned first by default, unless it's disabled via Group Policy. The "Search the Internet" link is pinned second, if it's pinned via Group Policy (though this link is disabled by default). If a custom Internet search link is pinned using the "Custom Internet search provider" Group Policy, this link will be pinned third on the Start menu. The remaining link(s) will be shared between pinned Search Connectors/Libraries and pinned Internet/intranet search links. Search Connector/Library links take precedence over Internet/intranet search links.
If you enable this policy setting, the specified Libraries or Search Connectors will appear in the "Search again" links and the Start menu links.
If you disable or don't configure this policy setting, no Libraries or Search Connectors will appear in the "Search again" links or the Start menu links.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | TryHarderPinnedLibrary |
Friendly Name | Pin Libraries or Search Connectors to the "Search again" links and the Start menu |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | TryHarderPinnedLibrary |
ADMX File Name | WindowsExplorer.admx |
TryHarderPinnedOpenSearch
Scope | Editions | Applicable OS |
---|---|---|
❌ Device ✅ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later ✅ Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./User/Vendor/MSFT/Policy/Config/ADMX_WindowsExplorer/TryHarderPinnedOpenSearch
This policy setting allows you to add Internet or intranet sites to the "Search again" links located at the bottom of search results in File Explorer and the Start menu links. The "Search again" links at the bottom of the Search Results view allow the user to reconduct a search but in a different location. The Internet search site will be searched with the text in the search box. To add an Internet search site, specify the URL of the search site in OpenSearch format with {searchTerms} for the query string (for example, https://www.example.com/results.aspx?q={searchTerms}
).
You can add up to five additional links to the "Search again" links at the bottom of results returned in File Explorer after a search is executed. These links will be shared between Internet search sites and Search Connectors/Libraries. Search Connector/Library links take precedence over Internet search links.
The first several links will also be pinned to the Start menu. A total of four links can be pinned on the Start menu. The "See more results" link will be pinned first by default, unless it's disabled via Group Policy. The "Search the Internet" link is pinned second, if it's pinned via Group Policy (though this link is disabled by default). If a custom Internet search link is pinned using the "Custom Internet search provider" Group Policy, this link will be pinned third on the Start menu. The remaining link(s) will be shared between pinned Internet/intranet links and pinned Search Connectors/Libraries. Search Connector/Library links take precedence over Internet/intranet search links.
If you enable this policy setting, the specified Internet sites will appear in the "Search again" links and the Start menu links.
If you disable or don't configure this policy setting, no custom Internet search sites will be added to the "Search again" links or the Start menu links.
Description framework properties:
Property name | Property value |
---|---|
Format | chr (string) |
Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
Name | Value |
---|---|
Name | TryHarderPinnedOpenSearch |
Friendly Name | Pin Internet search sites to the "Search again" links and the Start menu |
Location | User Configuration |
Path | WindowsComponents > File Explorer |
Registry Key Name | Software\Policies\Microsoft\Windows\Explorer |
Registry Value Name | TryHarderPinnedOpenSearch |
ADMX File Name | WindowsExplorer.admx |