Training
Module
Troubleshoot device driver failures - Training
This module focuses on the role of device drivers and troubleshooting problems that pertain to them.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This optional section contains one or more INF AddComponent directives that reference additional INF-writer-defined sections in a driver package INF file. This section is supported for Windows 10 Version 1703 and later.
[install-section-name.Components] |
[install-section-name.nt.Components] |
[install-section-name.ntx86.Components] |
[install-section-name.ntia64.Components] |
[install-section-name.ntamd64.Components] |
[install-section-name.ntarm.Components] |
[install-section-name.ntarm64.Components] |
AddComponent=ComponentName,[flags],component-install-section
[Include=filename.inf[,filename2.inf]...]
[Needs=inf-section-name[,inf-section-name]...]
You can provide a DDInstall.Components section with one or more AddComponent directives to create a symbolic relationship between a driver package and any number of software components.
AddComponent=ComponentName,[flags],component-install-section
This directive references an INF-writer-defined component-install-section elsewhere in the INF file for the drivers of the devices covered by this DDInstall section. For more information, see INF AddComponent Directive.
Include=filename.inf[,filename2.inf]...
Specifies one or more additional system-supplied INF files that contain sections needed to install this device. If this entry is specified, usually so is a Needs entry.
Needs=inf-section-name[,inf-section-name]...
Specifies the named sections that must be processed during the installation of this device. Typically, such a named section is a DDInstall.Components section within a system-supplied INF file that is listed in an Include entry. However, it can be any section that is referenced within such a DDInstall.Components section of the included INF.
DDInstall.Components sections should have the same platform and operating system decorations as their related DDInstall sections. For example, an install-section-name.ntx86 section would have a corresponding install-section-name.ntx86.Components section.
The specified DDInstall section must be referenced in a device/models-specific entry under the per-manufacturer Models section of the INF file. The case-insensitive extensions to the install-section-name shown in the formal syntax statement can be inserted into such a DDInstall.Components section name in cross-platform INF files.
For more information about how to use the system-defined .nt, .ntx86, .ntia64, .ntamd64, .ntarm, and .ntarm64 extensions, see Creating INF Files for Multiple Platforms and Operating Systems.
[ContosoGrfx.NT.Components]
AddComponent = ContosoControlPanel,,Component_Inst
[Component_Inst]
ComponentIDs = VID0001&PID0001&SID0001
DisplayName = %ContosoControlPanelDisplayName%
Training
Module
Troubleshoot device driver failures - Training
This module focuses on the role of device drivers and troubleshooting problems that pertain to them.
Documentation
Using a Component INF File - Windows drivers
Describes how to use software components to include user-mode software that is specific to a device.
INF DDInstall.Software Section - Windows drivers
The DDInstall.Software section contains one or more INF AddSoftware directives that reference additional INF-writer-defined sections in a software component INF file.
INF AddSoftware Directive - Windows drivers
An AddSoftware directive describes the installation of standalone software.