Driver fichier inf

To illustrate, consider the following scenario that includes a hypothetical device for which there are three extension INFs:. Next, the system processes the available extension INFs. From the first two, let's say that driver date is the same. The next tiebreaker is driver version, so the system selects the extension INF with v2. Specify these values for Class and ClassGuid in the Version section. Provide an ExtensionId entry in the [Version] section. Note that an organization may only use an ExtensionID that it owns.

Typically, an extension INF lists a more specific hardware ID than the base INF, with the goal of further specializing a specific driver configuration.

In some cases, the extension INF might provide a less specific device ID, like a compatible ID, in order to customize a setting across a broader set of devices. However, an extension INF can define other services, such as a filter driver for the device.

In most cases, you'll submit an extension INF driver package to the Hardware Dev Center separately from the base driver package. To remove an extension driver package from the system and uninstall it from any devices using it, use PnPUtil's delete-driver command with the uninstall flag. This allows the extension driver package to be uninstalled from devices without removing the base driver package.

In one common scenario, a device manufacturer IHV provides a base driver package, and then a system builder OEM provides an extension INF that supplements and in some cases overrides the configuration and settings of the base driver package. The following snippet is a complete extension INF that shows how to set the device friendly name. The following snippet is a complete extension INF that is included in the Driver package installation toolkit for universal drivers.

This example uses INF AddComponent directive to create components that install a service and an executable. For info on how to use an Extension INF to install a filter driver, see Device filter driver ordering. Any change to the base INF must be thoroughly tested to ensure that it does not break backward compatibility for existing extension INFs.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. SourceDisksNames required. SourceDisksFiles required. DefaultInstall required. Services required. ServiceInstall required. DefaultUninstall optional. Services optional. The Version section specifies the driver version information, as shown in the following code example. The following table shows the values that file system filter drivers should specify in the Version section.

The DestinationDirs section specifies the directories where the file system driver files will be copied. In this section and in the ServiceInstall section, you can specify well-known system directories by using system-defined numeric values. The SourceDisksNames section specifies the distribution media to be used. In the following code example, the SourceDisksNames section lists a single distribution media for the file system driver.

The unique identifier for the media is 1. The SourceDisksFiles section specifies the location and names of the files to be copied. In the following code example, the SourceDisksFiles section lists the file to be copied for the file system driver and specifies that the files can be found on the media whose unique identifier is 1 This identifier is defined in the SourceDisksNames section of the INF file.

In the DefaultInstall section, a CopyFiles directive copies the file system driver's driver files to the destination that is specified in the DestinationDirs section. Services , DefaultUninstall , and DefaultUninstall.

Services sections for each operating system version. Each section is labeled with a decoration for example,. In the following code example, the CopyFiles directive copies the files that are listed in the ExampleFileSystem. DriverFiles section of the INF file. The DefaultInstall. Services section contains an AddService directive that controls how and when the services of a particular driver are loaded.

In the following code example, the AddService directive adds the file system service to the operating system. Service is the name of the file system driver's ServiceInstall section. The ServiceInstall section adds subkeys or value names to the registry and sets values.

Services section. The following code example shows the ServiceInstall section for the file system driver. The DisplayName entry specifies the name for the service. The Description entry specifies a string that describes the service.

The ServiceBinary entry specifies the path to the executable file for the service. The ServiceType entry specifies the type of service. The following table lists the possible values for ServiceType and their corresponding service types. The StartType entry specifies when to start the service. The following table lists the possible values for StartType and their corresponding start types.

For detailed descriptions of these start types to determine which one is appropriate for your file system driver, see What Determines When a Driver Is Loaded. This requirement ensures optimal system boot performance. The ErrorControl entry specifies the action to be taken if the service fails to start during system startup.

The following table lists the possible values for ErrorControl and their corresponding error control values. This is different from what is specified for a file system filter driver or file system minifilter driver where the LoadOrderGroup entry is set to one of the file system filter load order groups.

For more information about the load order groups that are used for file system filter drivers and file system minifilter drivers, see Load Order Groups for File System Filter Drivers and Load Order Groups and Altitudes for Minifilter Drivers.

The AddReg directive refers to one or more INF writer-defined AddRegistry sections that contain any information to be stored in the registry for the newly installed service. For example:.