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

Writing INF Files

Last Updated: 1/24/2017

When you write an INF file for your driver package, you should follow these guidelines:

  • An INF file must use valid structure and syntax to pass driver package validation checks at the beginning of the installation process.

    Use the ChkINF tool to validate the structure and syntax of INF files.

  • An INF file must contain valid INF SourceDisksFiles and SourceDisksNames sections. Starting with Windows Vista, the operating system does not copy the driver package into the driver store unless these sections are present and filled in correctly.

  • It is sometimes necessary to copy INF files during device installation so that Windows can find them without repetitively displaying user prompts. For example, the base INF file for a multifunction device might copy the INF files for the device's individual functions so that Windows can find these INF files without prompting the user every time that it installs one of the device's functions.

    Starting with Windows XP, if you want to stage other INF files during an installation that is driven by an INF file, use the INF CopyINF directive.

    Note Do not use the INF CopyFiles directive to copy INF files.

  • The components of a driver package must never directly copy or delete INF files directly into a system's %SystemRoot%/Inf directory. This results in the driver's digital signature to be invalidated, and this causes the driver not to load successfully.

© 2017 Microsoft