| Setup Information file | |
| Extension: | .inf |
| Mime: | text/plain |
| Type: | Configuration file |
| Precompiled Setup Information file | |
| Extension: | .pnf |
| Mime: | application/octet-stream |
| Type: | Configuration file |
INF file (setup Information file) is INI plain-text file used by Microsoft Windows-based operating systems for the installation of software and drivers.[1] INF files are most commonly used for installing device drivers for hardware components.[2] Windows includes the IExpress tool for the creation of INF-based installations. INF files form part of the Windows Setup API and of its successor, Windows Installer.
The directory contains several such .inf files.[3]
Precompiled setup Information file is a binary representation of an INF file compiled by the operating system.
The structure of an INF file is very similar to that of an INI file; it contains various sections that specify the files to be copied, changes to the registry, etc. All INF files contain a [Version] section with a Signature key–value pair specifying the version of Windows that the INF file is meant for. The signature is commonly $CHICAGO$ (for Windows 9x) or $WINDOWS NT$ (for Windows NT/2K/XP). Most of the remaining sections are user-defined and contain information specific to the component being installed.An example of an INF file might have something like this:example.exe file automatically whenever the media containing the file (in its root directory) is connected to the computer. This can be dangerous, as there is no way to tell whether such a file exists before inserting the media. Since Windows XP, however, this feature has been replaced with a menu forcing the user to choose which action to take.
INF Files can sometimes be dangerous on Windows 2000 as they may allow viruses to autorun without prompting.They are blocked on Windows 7, but can be worked around. [4] icon=*.ico command replaces any old or default drive icon with the specified one.[autorun] can be replaced by [AutoRun] or [Autorun].
The INF file may specify values for Windows Registry entries. Drivers providers and users may for instance use this feature to override display Extended Display Identification Data (EDID) metadata for displays that have corrupted ROM memory.[5]