| Previous | Next |
| ERROR_UNKNOWN_PORT | ERROR_UNKNOWN_PRINTPROCESSOR |
ERROR_UNKNOWN_PRINTER_DRIVER
Printer queues refer to a registered printer driver by name. AddPrinter, for example, requires a non-NULL driver name in PRINTER_INFO_2, and the server must already know the driver that the queue is meant to use.
This status is more specific than a missing DLL. A driver package may exist in the Driver Store while the expected printer-driver registration is absent, or a deployment may be asking a remote server for a driver name that exists only on the client. Architecture and driver-name mismatches are especially important when a print server serves multiple client environments.
Resolve the identity first
- Enumerate printer drivers on the same server named in the failing API call.
- Compare the exact driver name and target environment; do not normalize vendor suffixes or architecture-specific names in application code.
- For a queue creation failure, also record pPrinterName, pPortName, pDriverName, and pPrintProcessor from PRINTER_INFO_2.
- If a remote client expects automatic driver delivery, verify that the server actually publishes a compatible registered driver.
Microsoft AddPrinter requirements · Printer driver installation APIs · Samba automatic printer driver downloads
Looking for a different code? Search another status or error code.