5/7/2023 0 Comments Inf file driver![]() Minifilter drivers should specify a value of 1 (SERVICE_ERROR_NORMAL). The ErrorControl entry specifies the action to be taken if the service fails to start during system startup. This location is determined by the altitude that is specified for the minifilter instance. These values ensure that the filter manager is always loaded before any minifilter drivers are loaded.įor more information about how the StartType and LoadOrderGroup entries determine when the driver is loaded, see What Determines When a Driver Is Loaded.įor minifilter drivers, unlike legacy file system filter drivers, the StartType and LoadOrderGroup values do not determine where the minifilter driver attaches in the minifilter instance stack. The filter manager's StartType value is SERVICE_BOOT_START, and its LoadOrderGroup value is FSFilter Infrastructure. In this way, minifilter drivers are different from legacy file system filter drivers. Note that you must specify a LoadOrderGroup value, even if your minifilter driver's start type is not SERVICE_BOOT_START. To choose a load order group, see Load Order Groups and Altitudes for Minifilter Drivers. You should specify a LoadOrderGroup value that is appropriate for the type of minifilter driver that you are developing. The LoadOrderGroup entry provides the filter manager with information that it needs to ensure interoperability between minifilter drivers and legacy file system filter drivers. Valueįor more information about these start types, see "Driver Start Types" in What Determines When a Driver Is Loaded. The following table lists the possible values for StartType and their corresponding start types. The StartType entry specifies when to start the service. For more information about the ServiceType entry, see INF AddService Directive. Minifilter drivers should specify a value of 2 (SERVICE_FILE_SYSTEM_DRIVER). The ServiceType entry specifies the type of service. LoadOrderGroup = "FSFilter Activity Monitor " ServiceType = 2 SERVICE_FILE_SYSTEM_DRIVER The following code example shows a typical DefaultInstall section. For more information about creating this type of INF file, see Creating INF Files for Multiple Platforms and Operating Systems. nt) that specifies the operating system version to which it applies. Each section is labeled with a decoration (for example. You can create this type of INF file by creating additional DefaultInstall and DefaultInstall.Services sections for each operating system version. You can create a single INF file to install your driver on multiple versions of the Windows operating systems. ![]() SetupAPI copies these files automatically. The CopyFiles directive should not refer to the catalog file or the INF file itself. In the DefaultInstall section, a CopyFiles directive copies the minifilter driver's driver files and user-application files to the destinations that are specified in the DestinationDirs section. Minispy.UserFiles = 10,FltMgr DefaultInstall Section (required) In the following code example, the value 12 refers to the Drivers directory (%windir%\system32\drivers), and the value 10 refers to the Windows directory (%windir%). For a list of these values, see INF DestinationDirs Section. In this section and in the ServiceInstall section, you can specify well-known system directories by system-defined numeric values. The DestinationDirs section specifies the directories where minifilter driver and application files will be copied. For more information, see the description of the CatalogFile entry in INF Version SectionĭestinationDirs Section (optional but recommended) All other minifilter drivers should leave this entry blank. ![]() In your own INF file, you should specify a provider other than Microsoft.įor antivirus minifilter drivers that are signed, this entry contains the name of a WHQL-supplied catalog file. See File System Filter Driver Classes and Class GUIDs. The following table shows the values that file system minifilter drivers should specify in the Version section. The Version section specifies a class and GUID that are determined by the type of minifilter driver, as shown in the following code example.ĬlassGuid = See Signing a driver for more information. These sections were optional in prior OS versions.Īll drivers running on 64-bit versions of Windows systems must be signed before Windows will load them. Starting with Windows 10 version 1903, the DefaultUninstall and DefaultUninstall.Services sections are prohibited, (with exception). You'll find sample INF files in the minifilter samples.Īn INF file for a file system filter driver generally contains the following sections: Section See Creating a new primitive driver for details.įilter drivers need an INF file to be installed on the Windows operating system. Starting in Windows 10 version 1903, INF requirements for primitive drivers (such as file system minifilter drivers) changed. Creating an INF file for a minifilter driver Introduction
0 Comments
Leave a Reply. |