How to Install inf Drivers (Windows 10/7/8/XP/Vista) - Driver Easy.
Looking for:
Creating an INF file for a file system driver - Windows drivers | Microsoft Docs.Using a Universal INF File - Windows drivers | Microsoft Docs |
INF Driver Pack for Windows® 10 bit for NUC10i7FN, NUC10i5FN, NUC10i3FN.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. The installation process is controlled by INF files. The INF file is a text file that specifies the files that must be present for your driver to run and the source and destination directories for the driver files. An INF file also contains driver configuration information that SetupAPI stores in the registry, such as the driver's start type and load order group.
For general information about signing drivers, see Driver Signing. You can create a single INF file to install your driver on multiple versions of the Windows operating system. Starting with bit versions of Windows Vista, all kernel-mode components, including non-PnP Plug and Play drivers such as file system drivers file system, legacy filter, and minifilter drivers , must be signed in order to load and execute. For these versions of the Windows operating system, the following list contains information that is relevant to file system drivers.
INF files for non-PnP drivers, including file system drivers, are not required to contain [Manufacturer] or [Models] sections. For performance reasons, boot-start drivers must contain an embedded signature.
With Administrator privileges, an unsigned driver can still be installed on xbased systems starting with Windows Vista. However, the driver will fail to load and thus execute because it is unsigned.
For detailed information about the driving signing process, including the driving signing process for bit versions of Windows Vista, see Kernel-Mode Code Signing Walkthrough. All kernel-mode components, including custom kernel-mode development tools, must be signed. INF files cannot be used to read information from the registry or to launch a user-mode application. To construct your own file system driver INF file, use the following information as a guide.
DestinationDirs optional but recommended. 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:. The DefaultUninstall section is optional but recommended if your driver can be uninstalled. It contains DelFiles and DelReg directives to remove files and registry entries.
In the following code example, the DelFiles directive removes the files that are listed in the ExampleFileSystem. The DelReg directive refers to one or more INF writer-defined DelRegistry sections that contain any information to be removed from the registry for the service that is being uninstalled. The DefaultUninstall. Services section is optional but recommended if your driver can be uninstalled. It contains DelService directives to remove the file system driver's services.
In the following code example, the DelService directive removes the file system driver's service from the operating system. There are certain classes of file system products that cannot be completely uninstalled. In this situation, it is acceptable to just uninstall the components of the product that can be uninstalled and leave installed the components of the product that cannot be uninstalled. You can create a single international INF file by creating additional locale-specific Strings.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode. Table of contents. Note There are certain classes of file system products that cannot be completely uninstalled.
Submit and view feedback for This product This page. View all page feedback. In this article. Leave this entry blank. In the future, it will contain the name of a WHQL-supplied catalog file for signed drivers. If startup still fails, run a bug-check routine. Only the drivers that are needed for the system to startup should specify this value in their INF files.
Comments
Post a Comment