Some Group Policy areas are missing from the Group Policy Editor
This article provides a solution to an issue where some Group Policy areas are missing from the Group Policy Editor.
Applies to: Windows 10 - all editions, Windows Server 2012 R2
Original KB number: 555218
When you open the Group Policy Editor MMC snap-in tool, and focus on a local GPO or Active Directory-based one, some Group Policy areas that are expected to appear may not be found. These missing policy areas are different than the ones that are normally missing when you're focused on a local GPO.
Each area of policy functionality is implemented by an MMC snap-in DLL that is registered by default on a standard Windows 2000, 2003 or XP installation. Occasionally those DLLs can be un-registered or removed and when that happens, the underlying group policy editing functionality they implement will not appear in the Group Policy editor UI.
To resolve this issue, re-register the appropriate MMC snap-in DLL that implements the missing functionality by issuing the following command at a Windows command prompt
regsvr32 <snap-in DLL name>
By default, all of the Group Policy related MMC snap-in DLLs can be found in %systemroot%\system32.
The following lists the default Group Policy snap-in DLLs that you can re-register:
- Administrative Templates and Scripts: gptext.dll
- Folder Redirection: fde.dll
- Internet Explorer Maintenance: ieaksie.dll
- IP Security: ipsecsnp.dll
- Public Key and Software Restriction: certmgr.dll
- Remote Installation Services: rigpsnap.dll
- Security: wsecedit.dll
- Software Installation: appmgr.dll
When you focus on the local GPO with the MMC Group Policy Editor snap-in, it is normal that some policy areas that you would normally see when editing an Active Directory-based GPO are not present. This is expected behavior because the local GPO only supports a subset of the features in an Active Directory-based GPO. However, sometimes even when focused on Active Directory-based GPOs, some policy areas that should be present are missing. In that case, the most likely cause is missing registrations for the MMC snap-in DLLs that implement that functionality, and by re-registering the missing DLL and restarting the Group Policy Editor, the problem can be resolved.
If you need assistance from Microsoft support, we recommend you collect the information by following the steps mentioned in Gather information by using TSS for Group Policy issues.
Community Solutions Content Disclaimer
Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.