Network Shell Namespace Extensions in Registry

This guide identifies the specific Windows Registry paths where shell namespace extensions for Network Neighborhood and remote network endpoints are cataloged. It outlines both the machine-wide and user-specific registry keys responsible for managing these extensions, as well as the related component identifier (CLSID) paths used by Windows Explorer to populate network locations.

Primary Network Neighborhood NameSpace Keys

Windows catalogs the shell namespace extensions that appear inside the Network (formerly Network Neighborhood) folder under the following registry paths:

Each subkey under NameSpace is named after the Class Identifier (CLSID) GUID of the registered extension (for example, {208D2C60-3AEA-1069-A2D7-08002B30309D} for the core Network folder implementation).

Remote Computer Endpoint Extensions

When connecting to or browsing specific remote computers across the local network, Windows uses an additional dedicated namespace key to catalog shell extensions (such as remote printers, administrative shares, or scheduled tasks):

Subkeys within this location determine the items and services displayed when opening a remote computer endpoint in Explorer.

Corresponding CLSID Definitions

The GUID keys found within the NameSpace paths reference full COM class registrations. Detailed properties, handler DLLs, and presentation details for each network extension are cataloged in:

Inside these CLSID keys, the InProcServer32 subkey specifies the dynamic link library (DLL) executing the namespace extension, while ShellFolder defines attributes such as folder behaviors and visibility flags.