Quick fix: Right-click the INF file → Install. If that’s greyed out (driver INFs don’t always have an Install verb), use Settings → Bluetooth & devices → Printers & scanners → Add device → Add manually → The printer that I want isn’t listed → Add a local printer or network printer with manual settings, then point at the INF via Have Disk.

Your printer manufacturer ships drivers as a giant EXE installer that bundles unwanted software (web toolbars, “helper” tray apps, auto-update services). Or you have only the INF + supporting files extracted from a CAB archive. Either way, you want to install the driver from the INF directly without running the full installer. Windows 11 supports this — the path is just hidden under “Add manually.”

Symptom: Want to install a printer driver from a standalone INF file without using the manufacturer’s bloated installer.
Affects: Windows 11 (and Windows 10) with INF-based printer drivers.
Fix time: ~10 minutes.

What causes this

A printer driver is technically just a collection of files (DLLs, PPDs, INFs) registered with Windows. Manufacturer EXE installers wrap that registration in a wizard plus add-on software. The Windows-native install path uses only the INF file: the INF describes which files belong to the driver, which printer models it supports, and how to register them. Windows reads the INF and copies the listed files to the driver store, no EXE needed.

Two scenarios where INF-based install is the right call: (1) you want to avoid bloatware, (2) the EXE installer fails or isn’t available (older drivers from defunct manufacturers, custom-built corporate drivers).

Method 1: Install via “Add manually” in Settings (Have Disk path)

The recommended GUI path. Works for both local and network printers.

Open Settings → Bluetooth & devices → Printers & scanners.
Click Add device. Wait a few seconds.
Click Add manually at the bottom of the discovery list.
Pick Add a local printer or network printer with manual settings. Click Next.
Choose the port. For USB printers: pick the existing USB port (USB001, USB002). For network printers via IP: pick Create a new port → Standard TCP/IP Port and enter the printer’s IP. Click Next.
In the driver list: click Have Disk (lower right).
Click Browse. Navigate to the folder containing your INF file. Select the INF. Click Open → OK.
Windows reads the INF and shows the printer models the driver supports. Pick your model. Click Next.
Choose printer name (defaults to the model). Click Next.
Choose sharing (typically “Do not share” for personal use). Click Next.
Optionally Print a test page. Click Finish.

This is the cleanest GUI path. It uses no third-party software but achieves the same result as the manufacturer’s installer.

Method 2: PnPUtil from command line

For scripted installs or when you want to add the driver to the driver store without immediately registering a printer.

Open Terminal (Admin).
Add the driver to the Windows driver store:
```
pnputil /add-driver C:\path\to\driver.inf /install
```
The /install flag installs the driver on any currently-attached device matching it.
To add the driver but defer installation until a device is connected:
```
pnputil /add-driver C:\path\to\driver.inf
```
To list all printer drivers currently in the driver store: pnputil /enum-drivers.
For multiple INFs in a folder:
```
pnputil /add-driver C:\driver_folder\*.inf /install
```
Adds every INF in the folder. Useful for vendor packages that ship with several variant INFs.
After driver is in the store, add the printer through Settings (Method 1) and the driver will appear in the dropdown without needing Have Disk.
To remove a driver: pnputil /delete-driver oemXX.inf /uninstall (replace oemXX.inf with the published name from pnputil /enum-drivers).

PnPUtil is the right approach for fleet deployment scripts and for situations where you want the driver pre-staged.

Method 3: Print Management for advanced scenarios

For installing drivers for multiple printers, including shared printers and v3/v4 driver model details.

Search Start menu for Print Management or run printmanagement.msc.
Expand Print Servers → [your computer].
Right-click Drivers → Add Driver. The Add Printer Driver Wizard opens.
Click Next. Pick architecture (x64 for 64-bit Windows; tick both x64 and x86 if you need to share to 32-bit clients).
Click Have Disk. Browse to your INF. Click OK.
Pick the driver name (from the INF’s declared models). Click Next → Finish.
The driver is now in the driver store and visible to Add Printer wizards in both Settings and Print Management.
To create the actual printer with this driver: right-click Printers → Add Printer in Print Management. Pick “Add a new printer using an existing port” or “Use an existing printer driver,” and select your installed driver.

Print Management is the right path for users managing more than a handful of printers, or for setting up shared printers with explicit driver architecture support.

How to verify the fix worked

Open Settings → Bluetooth & devices → Printers & scanners. Your printer should appear with status Ready.
Right-click → Printer properties → Print Test Page. A test page should reach the printer and print.
Run pnputil /enum-drivers /class Printer in Terminal. Your INF-installed driver should be listed with class Printer.

If none of these work

If the INF install fails with errors like “The third-party INF does not contain digital signature information” (error 0x800F0244 or 0x800F0247), the INF lacks a code-signing signature. On Windows 11 Home/Pro, this means Windows refuses to install the driver. Two workarounds: (1) sign the driver yourself if you have a code-signing certificate (advanced), or (2) disable driver signature enforcement temporarily — boot into Advanced Startup, choose Troubleshoot → Advanced options → Startup Settings → Restart → press 7 (Disable driver signature enforcement). This lasts only for one boot. For permanent unsigned-driver install, use Test Mode (bcdedit /set testsigning on) — caveat: a watermark appears in the bottom-right of the desktop, and Test Mode reduces security. For drivers in v3 model only (older PPD-based PostScript drivers): consider switching to a v4 model driver if the manufacturer provides one — v4 drivers are sandboxed and don’t require kernel-mode installation.

Bottom line: Settings → Add device → Add manually → Have Disk is the GUI path; pnputil /add-driver is the CLI path. Either installs an INF-based driver without manufacturer bloatware.