How to Install an INF Driver Offline

Not every driver ships with a friendly setup program. Sometimes all you get is a folder with an INF file, a few SYS and CAT files, and no obvious way to run it. That's normal for many chipset, network, and specialty components. Windows can install these packages directly, no installer required and no internet needed. You'll learn the three reliable manual methods and how to confirm the driver actually took hold afterward, so the device works instead of sitting there flagged with a warning.

1. 1

   Unpack and inspect the driver folder

   Copy the driver package to a folder you can find easily, such as one on your Desktop. If it arrived as a ZIP, extract it first so the files sit loose in a folder rather than inside the archive. Look for a file ending in .inf, usually alongside .sys, .cat, and sometimes .dll files. The INF is the recipe Windows reads to install everything else, so keep all these files together in one place. Don't rename or move individual files out of the folder, since the INF points to them by name and will fail if they've wandered off.

2. 2

   Create a restore point first

   Before changing any driver, give yourself an undo button. In the Start menu search box, type "Create a restore point" and open the result. On the System Protection tab, make sure protection is turned on for your system drive, then click Create and give the point a clear name like "before manual driver install." This takes a minute and costs nothing. If the new driver misbehaves, you can roll the whole system back to this moment. It's a small habit that saves real headaches when a bare INF turns out to be the wrong version for your hardware.

3. 3

   Try the right-click Install method

   The quickest route works when the INF is meant for direct installation. In File Explorer, right-click the .inf file. On Windows 11, choose "Show more options" first to reveal the classic menu, then click Install. Windows reads the file and copies the driver into place quietly, often without any visible progress window. When it finishes, you may see a brief confirmation. Note that not every INF supports this shortcut; some are meant to be selected through Device Manager instead. If Install is grayed out or you get an error, move on to the next method rather than forcing it.

4. 4

   Use Device Manager 'Have Disk'

   For a specific device, point Windows straight at your folder. Right-click the Start button and choose Device Manager. Find the device, right-click it, and pick Update driver, then "Browse my computer for drivers." Choose "Let me pick from a list," then click Have Disk. Browse to your driver folder and select the .inf file. Windows shows the matching hardware entries it found inside; pick the one that fits your device and continue. This method is ideal when a device shows a warning icon or when you need to force a particular driver onto hardware Windows didn't match automatically.

5. 5

   Install with pnputil from the command line

   For a scriptable, no-clicking approach, use the built-in pnputil tool. Right-click the Start button and choose Terminal (Admin) or Windows PowerShell (Admin). Change to your driver folder, then run pnputil /add-driver yourfile.inf /install. Swap yourfile.inf for the real name. To add every INF in a folder at once, use pnputil /add-driver *.inf /install. The /install flag tells Windows to bind the driver to any matching device it finds, not just stage it. Watch the output: it reports each package added and whether installation succeeded, which makes troubleshooting far clearer than the silent right-click method.

6. 6

   Verify the install in Driver Details

   Confirm Windows is actually using the driver you installed. Back in Device Manager, double-click the device, open the Driver tab, and check the Driver Version and Driver Date. Click Driver Details to see the exact SYS files loaded and their paths. If those match the package you added, you're done. You can also run pnputil /enum-drivers in an admin Terminal to list every third-party driver now in the driver store, which confirms your INF was accepted. A matching version plus no warning triangle on the device means the manual install succeeded.

7. 7

   Handle a device that still won't match

   If the device keeps a yellow warning after installing, the INF may not cover your exact hardware. Open the device's Properties, go to the Details tab, and select Hardware Ids from the dropdown. Compare those IDs against the ones listed inside the INF file, which you can open in Notepad. If they don't line up, this package isn't built for your device, and forcing it can cause instability. In that case, go back to your hardware maker's official support page and look for a package that lists your exact model, rather than trying to make a mismatched INF fit.