Windows Policy Identifiers

Each Windows Policy Identifier (POLID) is a 128-bit identifier that selects a registry value. The defining interpretation is by the SHLWAPI functions SHWindowsPolicyGetValue and SHWindowsPolicy. The selected registry value is the storage for a Windows policy.

The original implementation, in the SHLWAPI version 6.0 from Windows XP SP2, has each policy in some subkey of Software\Policies\Microsoft\Windows relative to either of HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER, the former having precedence. The SHLWAPI version 6.0 from Windows Vista extends the implementation, apparently with the intention of superseding the long-standing scheme of shell restrictions (which have 32-bit identifiers interpreted by the SHELL32 function SHRestricted). This adds many policies in subkeys of Software\Microsoft\Windows\CurrentVersion\Policies. Some of these have previous and continuing support as shell restrictions. Some are supported only through the new scheme. SHLWAPI version 6.1 continues this work of superseding old interfaces for reading policies, this time by collecting some of the Internet Explorer restrictions (which also have 32-bit identifiers, but are interpreted by the SHDOCVW function SHRestricted2).

None of this is documented by Microsoft. Each policy identifier has a name that is knowable from symbol files. Many, but certainly not all, of the policies have user-interface support, so that Microsoft does at least describe their effect, even usefully, though typically without formal documentation of the underlying registry values.

Enumeration

That a registry value is listed below means only that it appears in SHLWAPI’s tables of policies that are known to the SHWindowsPolicyGetValue and SHWindowsPolicy functions.

The TryHarderPinnedLibrary policy has user-interface support through the Group Policy Object Editor, as

Pin Libraries or Search Connectors to the “Search again” links and the Start menu links

in the Windows Explorer administrative template (shown under Windows Components).

The NoSystraySystemPromotion policy has user-interface support through the Group Policy Object Editor, as “Turn off automatic promotion of notification icons to the taskbar” in the “Start Menu and Taskbar” administrative template.

The NoInplaceSharing policy has user-interface support through the Group Policy Object Editor, as “Prevent users from sharing files within their user profile” in the Network Sharing administrative template (shown under Windows Components).

The NoPinningToDestinations policy has user-interface support through the Group Policy Object Editor, as “Do not allow pinning items in Jump Lists” in the “Start Menu and Taskbar” administrative template.

The NoSearchInternetTryHarderButton policy has user-interface support through the Group Policy Object Editor, as

Remove the Search the Internet “Search again” link

in the Windows Explorer administrative template (shown under Windows Components).

The HideSCAVolume policy has user-interface support through the Group Policy Object Editor, as “Remove the volume control icon” in the “Start Menu and Taskbar” administrative template.

The TaskbarNoResize policy has user-interface support through the Group Policy Object Editor, as “Prevent users from resizing the taskbar” in the “Start Menu and Taskbar” administrative template.

The TurnOffSPIAnimations policy has user-interface support through the Group Policy Object Editor, as “Turn off common control and window animations” in the Windows Explorer administrative template (shown under Windows Components).

The DisplayName_OpticalDisk policy has no known user-interface support.

The NoUserFolderInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Remove user folder link from Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoHTMLViewForWebDAV policy has no known user-interface support. Microsoft’s one known documentation of it is the Knowledge Base article When you use a screen reader program to read screen items in a WebDAV location in Windows Vista, the screen reader program does not work correctly.

The TurnOffSidebar policy has user-interface support through the Group Policy Object Editor, as “Turn off desktop gadgets” in the Desktop Gadgets administrative template (shown under Windows Components). The policy’s name is more readily related to the description in Windows Vista: “Turn off Windows Sidebar” in the Windows Sidebar administrative template (again shown under Windows Components).

The UseDefaultTile policy has user-interface support through the Group Policy Object Editor, as “Apply the default user logon picture to all users” in the User Accounts category of the Control Panel administrative template.

The NoNetworkConnections policy has user-interface support through the Group Policy Object Editor, as “Remove Network Connections from Start Menu” in the “Start Menu and Taskbar” administrative template. Though the NoNetworkConnections registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NONETWORKCONNECTIONS restriction in SHELL32 version 5.0 and higher.

The TaskbarNoNotification policy has user-interface support through the Group Policy Object Editor, as “Turn off balloon notifications” in the “Start Menu and Taskbar” administrative template.

The NoPreviewPane policy has user-interface support through the Group Policy Object Editor, as “Turn off Details Pane” in the Explorer Frame Pane administrative template (shown under Windows Explorer, which is in turn under Windows Components). Beware the mismatch between the Details Pane as explained for the user interface and the Preview Pane suggested by the registry value. Do not confuse with the policy described as “Turn off Preview Pane”, for which the underlying registry value is named NoReadingPane.

The HideContentViewModeSnippets policy has user-interface support through the Group Policy Object Editor, as “Turn off the display of snippets in Content view mode” in the Windows Explorer administrative template (shown under Windows Components).

The NoNTSecurity policy has user-interface support through the Group Policy Object Editor, as “Remove Windows Security item from Start menu” in the Remote Session Environment category of the Terminal Server administrative template (shown under Terminal Services, which is in turn under Windows Components). Though the NoNTSecurity registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSECURITY restriction in SHELL32 version 5.0 and higher.

The WPCEnableOnDomain policy has user-interface support through the Group Policy Object Editor, as “Make Parental Controls control panel visible on a Domain” in the Parental Controls administrative template (shown under Windows Components).

The NoSearchInternetInWordWheel policy would have user-interface support through the Group Policy Object Editor, as

Hide the “Search the Internet” link from the Search box drop down.

in the Instant Search administrative template (shown under Windows Components), but the template provides only the description and does not actually define the policy so that it can be listed.

The DisableBindDirectlyToPropertySetStorage policy has user-interface support through the Group Policy Object Editor, as “Disable binding directly to IPropertySetStorage without intermediate layers” in the Windows Explorer administrative template (shown under Windows Components). It is there dated from Windows Vista.

The UsePathEnvVarForCommandTemplates policy has no known user-interface support.

The DisplayName_RemovableDisk policy has no known user-interface support.

The NoFind policy has user-interface support through the Group Policy Object Editor, as “Remove Search link from Start Menu” in the “Start Menu and Taskbar” administrative template. Its availability is there put at “Windows Server 2003 and Windows XP operating systems only”, according to the template from Windows 7, but “at least Microsoft Windows 2000” according to the template from Windows Vista. The underlying registry value has even older support, including to be accessible as the REST_NOFIND restriction in SHELL32 version 4.0 and higher.

The NoPresentationSettings policy has user-interface support through the Group Policy Object Editor, as “Turn off Windows presentation settings” in the Presentation Settings administrative template (shown under Windows Components).

The TurnOffWinCal policy has user-interface support through the Group Policy Object Editor, as “Turn off Windows Calendar” in the Windows Calendar administrative template (shown under Windows Components).

The NoClose policy has user-interface support through the Group Policy Object Editor, as “Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands” in the “Start Menu and Taskbar” administrative template. It is there dated from Windows 2000, but is even older. Though the NoClose registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOCLOSE restriction from as long ago as SHELL32 version 4.0.

The UseOEMBackground policy has user-interface support through the Group Policy Object Editor, as “Always use custom logon background” in the Logon administrative template (shown under System).

The NoReadingPane policy has user-interface support through the Group Policy Object Editor, as “Turn off Preview Pane” in the Explorer Frame Pane administrative template (shown under Windows Explorer, which is in turn under Windows Components). Beware the mismatch between the Preview Pane as explained for the user interface and the Reading Pane suggested by the registry value.

The DisallowCpl policy has user-interface support through the Group Policy Object Editor, as “Hide specified Control Panel items” in the Control Panel administrative template. The specified items are taken from a subkey, also named DisallowCpl. Though the DisallowCpl registry value is not supported as a policy until Windows Vista, it is accessible as the REST_DISALLOWCPL restriction in SHELL32 version 5.0 and higher.

The NoChangingMousePointers policy has user-interface support through the Group Policy Object Editor, as “Prevent changing mouse pointers” in the Personalization category of the Control Panel administrative template.

The TaskbarNoPinnedList policy has user-interface support through the Group Policy Object Editor, as “Remove pinned programs from the Taskbar” in the “Start Menu and Taskbar” administrative template.

The NoDotBreakInLogicalCompare policy has no known user-interface support. Its only known use in Windows Vista is for the SHLWAPI function StrCmpLogicalW, including the copy that is linked into PROPSYS.DLL as an internal routine.

The PowerButtonAction policy has user-interface support through the Group Policy Object Editor, as “Change Start Menu power button” in the “Start Menu and Taskbar” administrative template. Options defined in the user interface set the dword of data to:

• 0x0001 for “Log off”;
• 0x0002 for Shut Down;
• 0x0004 for Restart;
• 0x0010 for Sleep;
• 0x0040 for Hibernate;
• 0x0100 for Switch User;
• 0x0200 for Lock

The ReallyEnforceShellExtSecurity policy has no known user-interface support.

The RestrictCpl policy has user-interface support as “Show only specified Control Panel items” in the Group Policy Object Editor, through the “Control Panel” administrative template. The specified items are taken from a subkey, also named RestrictCpl. Though the RestrictCpl registry value is not supported as a policy until Windows Vista, it is accessible as the REST_RESTRICTCPL restriction in SHELL32 version 5.0 and higher.

The NoSendToMenu policy has no known user-interface support.

The NoBalloonFeatureAdvertisements policy has user-interface support through the Group Policy Object Editor, as “Turn off feature advertisement balloon notifications” in the “Start Menu and Taskbar” administrative template.

The NoAutoplayfornonVolume policy has user-interface support through the Group Policy Object Editor, as “Turn off Autoplay for non-volume devices” in the AutoPlay Policies administrative template (shown under Windows Components).

The NoSetFolders policy has user-interface support through the Group Policy Object Editor, as “Remove programs on Settings menu” in the “Start Menu and Taskbar” administrative template. It is there dated from Windows 2000, but is even older. Though the NoSetFolders registry value is not supported as a policy until Windows Vista, it is the REST_NOSETFOLDERS restriction from as long ago as SHELL32 version 4.0.

The TaskbarNoDragToolbar policy has user-interface support through the Group Policy Object Editor, as “Prevent users from rearranging toolbars” in the “Start Menu and Taskbar” administrative template.

The NoToolbarOptions policy has no known user-interface support. Though the NoToolbarOptions registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x6000000E in SHDOCVW version 5.0 and higher (and even earlier, in some builds of SHDOCVW version 4.72, as restriction number 0x50000022).

The NoWindowMinimizingShortcuts policy has user-interface support through the Group Policy Object Editor, as “Turn off Aero Shake minimizing mouse gesture” in the Desktop administrative template.

The PreXPSP2ShellProtocolBehavior policy has user-interface support through the Group Policy Object Editor as “Turn off shell protocol protected mode” in the Windows Explorer administrative template (shown under Windows Components).

The HideSCANetwork policy has user-interface support through the Group Policy Object Editor, as “Remove the networking icon” in the “Start Menu and Taskbar” administrative template.

The NoChangingSoundScheme policy has user-interface support through the Group Policy Object Editor, as “Prevent changing sounds” in the Personalization category of the Control Panel administrative template.

The DisplayName_RemoteDrive policy has no known user-interface support.

The DisplayName_FixedDisk policy has no known user-interface support.

The HideFastUserSwitching policy has user-interface support through the Group Policy Object Editor, as “Hide entry points for Fast User Switching” in the Logon administrative template (shown under System).

The NoRestartOnTimer policy has no known user-interface support.

The UseFindFirstFileEnumeration policy has no known user-interface support.

The NoStartMenuNetworkPlaces policy has user-interface support through the Group Policy Object Editor, as “Remove Network icon from Start Menu” in the “Start Menu and Taskbar” administrative template. Though the NoStartMenuNetworkPlaces registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMNETWORKPLACES restriction in SHELL32 version 6.0 and higher.

The NoSMMyDocs policy has user-interface support through the Group Policy Object Editor, as “Remove Documents icon from Start Menu” in the “Start Menu and Taskbar” administrative template. Though the NoSMMyDocs registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMMYDOCS restriction in SHELL32 version 5.0 and higher.

The GoMenu policy has no known user-interface support.

The NoInstrumentation policy has user-interface support through the Group Policy Object Editor, as “Turn off user tracking” in the “Start Menu and Taskbar” administrative template. Though the NoInstrumentation registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x1A in SHDOCVW version 5.0 and higher.

The NoWindowsUpdate policy has user-interface support through the Group Policy Object Editor, as “Remove links and access to Windows Update” in the “Start Menu and Taskbar” administrative template. It is there dated to Windows 2000, but is a few years older. Though the NoWindowsUpdate registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOWINDOWSUPDATE restriction in SHELL32 version 4.72 and higher, and as restriction number 0x1B in SHDOCVW version 5.0 and higher.

The NoMyComputerIcon policy has user-interface support through the Group Policy Object Editor, as “Remove Computer icon on the desktop” in the Desktop administrative template. Though the {20D04FE0-3AEA-1069-A2D8-08002B30309D} registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOMYCOMPUTERICON restriction in SHELL32 version 6.0 and higher.

The DisableSearchBoxSuggestions policy has user-interface support through the Group Policy Object Editor as “Turn off display of recent search entries in the Windows Explorer search box” in the Windows Explorer administrative template (shown under Windows Components).

The NoStartMenuDownloads policy has user-interface support through the Group Policy Object Editor, as “Remove Downloads link from Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoStartMenuMyMusic policy has user-interface support through the Group Policy Object Editor, as “Remove Music icon from Start Menu” in the “Start Menu and Taskbar” administrative template. Though the NoStartMenuMyMusic registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMMYMUSIC restriction in SHELL32 version 6.0 and higher.

The DisplayName_Floppy policy has no known user-interface support.

The HideSCAHealth policy has user-interface support through the Group Policy Object Editor, as “Remove the Action Center icon” in the “Start Menu and Taskbar” administrative template.

The ClearRecentProgForNewUserInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Clear the recent programs list for new users” in the “Start Menu and Taskbar” administrative template.

The DisableThumbsDBOnNetworkFolders policy has user-interface support through the Group Policy Object Editor, as “Turn off the caching of thumbnails in hidden thumbs.db files” in the Windows Explorer administrative template (shown under Windows Components).

The HideSCAPower policy has user-interface support through the Group Policy Object Editor, as “Remove the battery meter” in the “Start Menu and Taskbar” administrative template. This policy was overlooked for user-interface support in Windows Vista because the template mistakenly defined the corresponding registry value as HideSCABattery.

The NoStartMenuSubFolders policy has user-interface support through the Group Policy Object Editor, as “Remove user’s folders from Start Menu” in the “Start Menu and Taskbar” administrative template. It is there dated from Windows 2000 but is much older. Though the NoStartMenuSubFolders registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSTARTMENUSUBFOLDERS restriction from as long ago as SHELL32 version 4.0.

The NoDefaultPrograms policy has user-interface support through the Group Policy Object Editor, as

Hide “Set Program Access and Computer Defaults” page

in the Programs administrative template (shown under Control Panel).

The EnableShellExecuteHooks policy has no known user-interface support.

The NoRemoteDestinations policy has user-interface support through the Group Policy Object Editor, as “Do not display or track items in Jump Lists from remote locations” in the “Start Menu and Taskbar” administrative template.

The QuickLaunchEnabled policy has user-interface support through the Group Policy Object Editor, as “Show QuickLaunch on Taskbar” in the “Start Menu and Taskbar” administrative template. Its availability is there limited to “Windows Vista only”.

The NoControlPanel policy has user-interface support through the Group Policy Object Editor, as “Prohibit access to the Control Panel” in the Control Panel administrative template. Though the NoControlPanel registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOCONTROLPANEL in SHELL32 version 5.0 and higher.

The NoSearchComputerLinkInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Remove Search Computer link” in the “Start Menu and Taskbar” administrative template.

The ForceExpandedSaveDialog policy has no known user-interface support.

The NoGetPrograms policy has user-interface support through the Group Policy Object Editor, as

Hide “Get Programs” page

in the Programs administrative template (shown under Control Panel).

The NoRecentDocsMenu policy has user-interface support through the Group Policy Object Editor, as “Remove Recent Items menu from Start Menu” in the “Start Menu and Taskbar” administrative template. It there dated to Windows 2000 but is a couple of years older. Though the NoRecentDocsMenu registry value is not supported as a policy until Windows 2000, it is accessible as the REST_NORECENTDOCSMENU restriction from as long ago as SHELL32 version 4.71.

The CheckSameSourceAndTargetForFRAndDFS policy has user-interface support through the Group Policy Object Editor, as “Verify old and new Folder Redirection targets point to the same share before redirecting” in the Windows Explorer administrative template (shown under Windows Components).

The AddSearchEverywhereLinkInStartMenu policy has no known user-interface support.

The NoSearchInternetLinkInStartMenu policy has no known user-interface support.

The NoFavoritesMenu policy has user-interface support through the Group Policy Object Editor, as “Remove Favorites menu from Start Menu” in the “Start Menu and Taskbar” administrative template. It there dated to Windows 2000 but is a couple of years older. Though the NoFavoritesMenu registry value is not supported as a policy until Windows 2000, it is accessible as the REST_NOFAVORITESMENU restriction from as long ago as SHELL32 version 4.71.

The PreventItemCreationInUsersFilesFolder policy has user-interface support through the Group Policy Object Editor, as “Prevent users from adding files to the root of their Users Files folder” in the Windows Explorer administrative template (shown under Windows Components).

The TaskbarNoThumbnail policy has user-interface support through the Group Policy Object Editor, as “Turn off taskbar thumbnails” in the “Start Menu and Taskbar” administrative template. Its availability is there limited to “Windows Vista only”.

The NoPinningToTaskbar policy has user-interface support through the Group Policy Object Editor, as “Do not allow pinning programs to the Taskbar” in the “Start Menu and Taskbar” administrative template.

The DontSetAutoplayCheckbox policy has user-interface support through the Group Policy Object Editor, as “Don’t set the always do this checkbox” in the AutoPlay Policies administrative template (shown under Windows Components).

The NormalizeLinkNetPidls policy has no known user-interface support. Microsoft’s one known documentation of it is the Knowledge Base article Two Windows appear when you double-click two shortcuts to the same folder in Windows XP. The NormalizeLinkNetPidls registry value is also accessible as the restriction 0x4000009E in the SHELL32 version 6.0 from Windows XP SP3 only.

The DisableThumbnails policy has user-interface support through the Group Policy Object Editor, as “Turn off the display of thumbnails and only display icons” in the Windows Explorer administrative template (shown under Windows Components).

The TaskbarNoAddRemoveToolbar policy has user-interface support through the Group Policy Object Editor, as “Prevent users from adding or removing toolbars” in the “Start Menu and Taskbar” administrative template.

The NoSMMyPictures policy has user-interface support through the Group Policy Object Editor, as “Remove Pictures icon from Start Menu” in the “Start Menu and Taskbar” administrative template. It is there dated to Windows XP but is slightly older. Though the NoSMMyPictures registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMMYPICS restriction in SHELL32 version 5.50 and higher.

The AddSearchInternetLinkInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Add Search Internet link to Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoMobilityCenter policy has user-interface support through the Group Policy Object Editor, as “Turn off Windows Mobility Center” in the Windows Mobility Center administrative template (shown under Windows Components).

The DisableHomeGroup policy has user-interface support through the Group Policy Object Editor, as “Prevent the computer from joining a homegroup” in the HomeGroup administrative template (shown under Windows Components).

The NoProgramsCPL policy has user-interface support through the Group Policy Object Editor, as “Hide the Programs Control Panel” in the Programs administrative template (shown under Control Panel).

The DisableThumbnailsOnNetworkFolders policy has user-interface support through the Group Policy Object Editor, as “Turn off the display of thumbnails and only display icons on network folders” in the Windows Explorer administrative template (shown under Windows Components).

The NoRun policy has user-interface support through the Group Policy Object Editor, as “Remove Run menu from Start Menu” in the “Start Menu and Taskbar” administrative template. It is there dated to Windows 2000 but is much older. Though the NoRun registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NORUN restriction from as long ago as SHELL32 version 4.0.

The NoSearchCommInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Do not search communications” in the “Start Menu and Taskbar” administrative template.

The NoInstalledUpdates policy has user-interface support through the Group Policy Object Editor, as

Hide “Installed Updates” page

in the Programs administrative template (shown under Control Panel).

The NoManualUpdates policy has no known user-interface support.

The CompareJunctionness policy has no known user-interface support. Microsoft’s one known documentation of it is the Knowledge Base article FIX: Windows Explorer tree view may display a folder that does not have a name or that has an incorrect name in Windows 2000 and in Windows XP.

The NoSMHelp policy has user-interface support through the Group Policy Object Editor, as “Remove Help menu from Start Menu” in the “Start Menu and Taskbar” administrative template. Though the NoSMHelp registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMHELP restriction in SHELL32 version 5.0 and higher.

The AllowCLSIDPROGIDMapping policy has no known user-interface support. Though the AllowCLSIDPROGIDMapping registry value is not supported as a policy until Windows Vista, it has an earlier history as a shell restriction: number 0x400000FF in the builds of SHELL32 version 6.0 from Windows XP SP3 and Windows Server 2003 SP2 only.

The NoSearchFullText policy has no known user-interface support.

The NoSearchFilesInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Do not search for files” in the “Start Menu and Taskbar” administrative template. Its availability is there said to be “At least Windows Vista”.

The NoSetTaskbar policy has user-interface support through the Group Policy Object Editor, as “Prevent changes to Taskbar and Start Menu Settings” in the “Start Menu and Taskbar” administrative template. It is there dated to Windows 2000 but is much older. Though the NoSetTaskbar registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSETTASKBAR restriction from as long ago as SHELL32 version 4.0.

The CopyEngineNoNotifyMSSearch policy has no known user-interface support.

The TaskbarLockAll policy has user-interface support through the Group Policy Object Editor, as “Lock all taskbar settings” in the “Start Menu and Taskbar” administrative template.

The NoDrivesInSendToMenu policy has no known user-interface support.

The NoStartMenuMyGames policy has user-interface support through the Group Policy Object Editor, as “Remove Games link from Start Menu” in the “Start Menu and Taskbar” administrative template.

Not that it matters in practice, but this policy is duplicated in SHLWAPI’s tables.

The NoLinksBar policy has no known user-interface support.

The PerInstanceIconHandlerForOffline policy has no known user-interface support. Microsoft’s one known documentation of it is the Knowledge Base article BUG: An HTML file or an XML file that you archived to a secondary storage device may appear without an icon in Windows Explorer on a client computer that is running Windows Server 2003 or Windows XP.

The NoStartMenuRecordedTV policy has user-interface support through the Group Policy Object Editor, as “Remove Recorded TV link from Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoWindowsFeatures policy has user-interface support through the Group Policy Object Editor, as

Hide “Windows Features”

in the Programs administrative template (shown under Control Panel).

The NoBrowserOptions policy has user-interface support through the Group Policy Object Editor, as “Tools menu: Disable Internet Options... menu option” in the “Browser menus” category of the Internet Explorer administrative template (shown under Windows Components). Though the NoBrowserOptions registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x60000004 in SHDOCVW version 5.0 and higher (and even earlier, in some builds of SHDOCVW version 4.72, as restriction number 0x5000001D).

The TryHarderPinnedOpenSearch policy has user-interface support through the Group Policy Object Editor, as

Pin Internet search sites to the “Search again” links and the Start menu

in the Windows Explorer administrative template (shown under Windows Components).

The NoStartMenuVideos policy has user-interface support through the Group Policy Object Editor, as “Remove Videos link from Start Menu” in the “Start Menu and Taskbar” administrative template.

The DisableIndexedLibraryExperience policy has user-interface support through the Group Policy Object Editor, as “Turn off Windows Libraries features that rely on indexed file data” in the Windows Explorer administrative template (shown under Windows Components).

The NoWindowsMarketplace policy has user-interface support through the Group Policy Object Editor, as

Hide “Windows Marketplace”

in the Programs administrative template (shown under Control Panel).

The NOBANDCUSTOMIZE policy has no known user-interface support.

The DisableKnownFolders policy has user-interface support through the Group Policy Object Editor, as “Disable Known Folders” in the Windows Explorer administrative template (shown under Windows Components).

The NoAutorun policy has user-interface support through the Group Policy Object Editor, as “Default behavior for AutoRun” in the AutoPlay Policies administrative template (shown under Windows Components).

The TaskbarNoRedock policy has user-interface support through the Group Policy Object Editor, as “Prevent users from moving taskbar to another screen dock location” in the “Start Menu and Taskbar” administrative template.

The NoSearchInternetInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Do not search Internet” in the “Start Menu and Taskbar” administrative template. Its availability is there limited to “Windows Vista and Windows Server 2008”.

The ForceClassicControlPanel policy has user-interface support through the Group Policy Object Editor, as “Always open All Control Panel Items when opening Control Panel” in the Control Panel administrative template. Its description in the templates from Windows Vista is simply “Force classic Control Panel view”. Though the ForceClassicControlPanel registry value is not supported as a policy until Windows Vista, it has an earlier history as a registry value interpreted by builds of SHELL32 version 6.0 from before Windows Vista.

The ScanWithAntiVirus policy has user-interface support through the Group Policy Object Editor, as “Notify antivirus programs when opening attachments” in the Attachment Manager administrative template (shown under Windows Components). The minimum and maximum are interpreted as disabled and enabled, respectively.

The SaveZoneInformation policy has user-interface support through the Group Policy Object Editor, as “Do not preserve zone information in file attachments” in the Attachment Manager administrative template (shown under Windows Components). The values 1 and 2 are interpreted as enabled and disabled, respectively.

The UseTrustedHandlers policy has user-interface support through the Group Policy Object Editor, as “Trust logic for file attachments” in the Attachment Manager administrative template (shown under Windows Components). The values 1, 2 and 3 are interpreted respectively as:

• Preferring the file type
• Preferring the file handler
• Looking at the file handler and type

The HideZoneInfoOnProperties policy has user-interface support through the Group Policy Object Editor, as “Hide mechanisms to remove zone information” in the Attachment Manager administrative template (shown under Windows Components).

The DefaultFileTypeRisk policy has user-interface support through the Group Policy Object Editor, as “Default risk level for file attachments” in the Attachment Manager administrative template (shown under Windows Components). Values from the minimum to the maximum are defined respectively as Low Risk, Moderate Risk and High Risk.

Data for the DefaultFileTypeRisk registry value specifies the risk level for file associations that have no risk level set explicitly through any of the HighRiskFileTypes, ModRiskFileTypes and LowRiskFileTypes policies.

The DefaultFileTypeRisk policy’s only known users in Windows Vista are IEFRAME and SHLWAPI. For both, the purpose is to support the undocumented AssocGetUrlAction function. SHLWAPI exports this function. IEFRAME has its own copy, presumably only to avoid importing it from SHLWAPI (which would have the unhappy side-effect of requiring Microsoft to document it for settlement compliance).

The HighRiskFileTypes policy has user-interface support through the Group Policy Object Editor, as “Inclusion list for high risk file types” in the Attachment Manager administrative template (shown under Windows Components).

Data for the HighRiskFileTypes registry value is a semicolon-delimited list of file assocations (given by extension or ProgID) to regard as high-risk. The SHLWAPI function AssocIsDangerous answers TRUE for all assocations in this list.

The ModRiskFileTypes policy has user-interface support through the Group Policy Object Editor, as “Inclusion list for moderate risk file types” in the Attachment Manager administrative template (shown under Windows Components).

Data for the ModRiskFileTypes registry value is a semicolon-delimited list of file assocations (given by extension or ProgID) to regard as moderate-risk.

The LowRiskFileTypes policy has user-interface support through the Group Policy Object Editor, as “Inclusion list for low risk file types” in the Attachment Manager administrative template (shown under Windows Components).

Data for the LowRiskFileTypes registry value is a semicolon-delimited list of file assocations (given by extension or ProgID) to regard as low-risk.

The AlwaysShowClassicMenu policy has user-interface support through the Group Policy Object Editor, as “Display the menu bar in Windows Explorer” in the Windows Explorer administrative template (shown under Windows Components).

The StartMenuLogoff policy has user-interface support through the Group Policy Object Editor, as “Remove Logoff on the Start Menu” in the “Start Menu and Taskbar” administrative template. Though the StartMenuLogoff registry value is not supported as a policy until Windows Vista, it is accessible as the REST_STARTMENULOGOFF restriction in SHELL32 version 5.0 and higher.

The NoStartMenuHomegroup policy has user-interface support through the Group Policy Object Editor, as “Remove Homegroup link from Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoProgramsAndFeatures policy has user-interface support through the Group Policy Object Editor, as

Hide “Programs and Features” page

in the Programs administrative template (shown under Control Panel).

The NoSearchProgramsInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Do not search programs and Control Panel items” in the “Start Menu and Taskbar” administrative template. The description in the template from Windows Vista is just “Do not search programs”.

The EnableSecureCredentialPrompting policy has user-interface support through the Group Policy Object Editor, as “Require trusted path for credential entry.” in the Credential User Interface administrative template (shown under Windows Components).

The EnumerateAdministrators policy has user-interface support through the Group Policy Object Editor, as “Enumerate administrator accounts on elevation” in the Credential User Interface administrative template (shown under Windows Components).

The NoTheaterMode policy has user-interface support through the Group Policy Object Editor, as “View menu: Disable Full Screen menu option” in the “Browser menus” category of the Internet Explorer administrative template (shown under Windows Components). Though the NoTheaterMode registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x6000000A in SHDOCVW version 5.0 and higher (and even earlier, in some builds of SHDOCVW version 4.72, as restriction number 0x50000025).

The NoSearchEverywhereLinkInStartMenu policy has user-interface support through the Group Policy Object Editor, as “Remove See More Results / Search Everywhere link” in the “Start Menu and Taskbar” administrative template.

The SkipNetworkShieldCheck policy has no known user-interface support.

The ForceRunOnStartMenu policy has user-interface support through the Group Policy Object Editor, as “Add the Run command to the Start Menu” in the “Start Menu and Taskbar” administrative template.

The NoBrowserClose policy has user-interface support through the Group Policy Object Editor, as “File menu: Disable closing the browser and Explorer windows” in the “Browser menus” category of the Internet Explorer administrative template (shown under Windows Components). Though the NoBrowserClose registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x60000008 in SHDOCVW version 5.0 and higher (and even earlier, in some builds of SHDOCVW version 4.72, as restriction number 0x50000021).

The NoFindFiles policy has user-interface support through the Group Policy Object Editor, as Search: Disable Find Files via F3 within the browser” in the Internet Explorer administrative template (shown under Windows Components). Its availability is there limited to “Only Internet Explorer 5.0 and Internet Explorer 6.0”. Though the NoFindFiles registry value is not supported as a policy until Windows 7, it is accessible as restriction number 0x6000000B in SHDOCVW version 5.0 and higher (and even earlier, in some builds of SHDOCVW version 4.72, as restriction number 0x50000026).

The NoSMConfigurePrograms policy has user-interface support through the Group Policy Object Editor, as “Remove Default Programs link from the Start menu” in the “Start Menu and Taskbar” administrative template. Though the NoSMConfigurePrograms registry value is not supported as a policy until Windows Vista, it is accessible as the REST_NOSMCONFIGUREPROGRAMS restriction in SHELL32 version 5.0 from Windows Server 2003 SP3 and higher, and version 6.0 from Windows XP SP1, and higher.