Updating Printer Drivers HP

HP publishes full-feature packages, Easy Start downloads, universal print drivers and operating-system-supplied queues. Consumer DeskJet and Envy models usually need the full-feature package only when scan, fax or colour controls are missing. Office LaserJet and PageWide devices often work well with a validated Universal Print Driver, but model-specific finishing, accounting and status features can disappear. DesignJet and production devices should follow the model’s own installer and controller documentation rather than a generic office package.

HP’s support portal is regional. A package listed for North America may not include the same language or accessory support as the European release. Match the region, operating system build and architecture, then check the release notes for the exact suffix. For managed fleets, standardise on one tested UPD version and document the exceptions that need a full-feature driver.

Windows Update may install an HP IPP or basic PCL queue automatically. If scan or finishing features are missing, remove that queue and install the full-feature package from the HP support page. For ARM64 Windows devices, verify the package architecture before running the installer.

1. 01

   Record the baseline and clear the old queue

   Note the exact model code, port, current driver version and any custom defaults. Remove the affected queue and, where relevant, its dedicated port. Restart before installing. This prevents Windows from silently reusing the stale driver.

2. 02

   Download the matching package from HP

   Select the exact model, Windows version and architecture. Verify the digital signature and release notes. If you need scan, fax, finishing or accounting features, confirm that the package includes those components rather than assuming they are bundled.

3. 03

   Install deliberately, not by automatic discovery

   Run the signed installer and add the printer on the intended port. For a network device, use a fixed address or DHCP reservation. If a generic queue already exists, remove it before adding the new one so the driver choice is unambiguous.

4. 04

   Reapply options and test real output

   Reselect installed trays, finishers, colour profiles and authentication settings. Print from two applications, test duplex and colour, then reboot and print again. If scanning is part of the workflow, test it separately.

macOS often discovers HP devices through AirPrint. That is fine for basic printing, but HP Easy Start or a current HP driver package is needed for scan shortcuts, specialty media and some colour options. Remove the old queue first if macOS keeps selecting a Generic PostScript driver.

1. 01

   Remove the existing queue before downloading

   Open System Settings → Printers & Scanners and remove the device. This clears stale driver references and prevents macOS from quietly reusing a generic PostScript queue. Note any presets or custom paper sizes first.

2. 02

   Choose AirPrint or the vendor package on purpose

   If basic printing is enough, readding the device as an AirPrint queue is the most maintainable path. If you need scanning, specialty media, colour profiles or finishing, install the current HP package and select the vendor driver explicitly.

3. 03

   Verify scan support outside the print dialog

   Open Image Capture or the manufacturer’s scan utility and confirm the scanner is visible. A print queue can be healthy while scanning is absent. If the scanner is missing, fix discovery or the scan component before changing the print driver again.

4. 04

   Test, then record the working configuration

   Print a real document, a colour page and a duplex job where supported. Note the queue protocol, driver version and macOS release. macOS updates occasionally replace a vendor queue with a generic one, so the record is your baseline.

HPLIP is the mature path for supported HP models. Install it from your distribution repository where possible, then use hp-setup for discovery. New consumer models can lag behind HPLIP releases, so check the supported-device list before assuming a failure is a CUPS problem.

Linux support is model-dependent. Where the manufacturer does not publish a current package, a driverless queue or a validated generic PCL/PostScript driver may be the only supported option. Treat unsupported features as unavailable rather than “almost working.”

The three patterns below account for a disproportionate share of HP driver support cases. They are worth checking before you download another package.

This guide applies to the HP families below. Model suffixes and regional variants matter, so use the label on the device or the configuration page before choosing a package.

The list is illustrative, not exhaustive. A driver page may cover additional models or exclude older regional variants. Always compare the exact model and release notes before installing.