How to install a printer driver command line

Written by joshua laud
  • Share
  • Tweet
  • Share
  • Email

If you're installing a printer on a lot of computers on your home or local network, it's generally too time-consuming to install each printer individually. If you install the printer from the command line, however, you can automate the installation process and remove the need for a print installation wizard. If you learn to program your command-line printer driver installation, this could also be used in a batch script. If you install the printer driver this way, additional software will not be installed, just the basic printer driver.

Skill level:


  1. 1

    Click "Start," type "cmd" and press "Enter" to launch the command prompt.

  2. 2

    Type the following string replacing the variables as you type it:

    PRINTUI.EXE /ia /c\computername /m "Printer driver model" /h "Intel" /v "Windows 2000" /f C:\printerdriver.inf

    "/ia" specifies to install the printer from a .inf file. You need to know where this is located.

  3. 3

    Replace "computername" with the name of the computer on your server that you want to install the printer to.

  4. 4

    Replace "Printer driver model" with the name and model of your printer. "/m" specifies the model name command, "/h" specifies the driver architecture. This is typically "Intel," but can also be "Alpha," "Mips," or "PowerPC."

  5. 5

    Replace "Windows 2000" with the operating system version on the target computer. "/v" refers to the driver version to be installed.

  6. 6

    Replace "C:\printerdrive.inf" with the path and file name of the printer driver. "/f" refers to the path for the inf file.

  7. 7

    Press "Enter" to install the printer to the target from the command line.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.