Table of contents
Collapse the table of content
Expand the table of content

Add-registry-sections in a Network INF File

Last Updated: 9/2/2016

An INF file contains one or more add-registry-sections for each component that it installs. An add-registry-section adds keys and values to the registry. The DDInstall section of an INF file contains an AddReg directive that references one or more add-registry-sections. For more information about the add-registry-section and the AddReg directive, see INF AddReg Directive.

Adding Keys and Values to Instance Keys

One or more add-registry-sections can add keys and values to the instance key for a component to accomplish any of the following:

Adding Keys and Values to a NetClient Component

An add-registry-section in an INF file for a NetClient component must add a NetworkProvider key to the service key for that component. The NetworkProvider key has two values: a Name that specifies the name of the network provider, and a ProviderPath that specifies the full path to the network provider DLL. For more information, see Specifying the Name and Provider Path for a NetClient Component.

NoteNetClient components are deprecated in Windows 8.1, Windows Server 2012 R2, and later.

Creating the Ndi Key

Each network INF file must contain at least one add-registry-section that adds an Ndi key for the component installed by the file. The Ndi key is a network-specific key that is added to the instance key for the component. The keys and values that are added to the Ndi key vary according to the type of network component being installed and its capabilities. The Ndi key specifies the following:

For a list of Ndi registry keys and values that are available in Windows 95/98/Me but not used in Windows 2000 and later versions, see Ndi Values and Keys Not Used in Windows 2000 and Later Versions.

© 2017 Microsoft