Start with Windows Update, then use the printer maker
In Windows 11, open Settings > Windows Update, select Check for updates, then review Advanced options > Optional updates for an applicable printer driver. If Windows Update does not offer one, use the printer manufacturer’s official support page, find the exact model, and choose a Windows 11 package for your PC’s system type (x64 or ARM64).
Before changing anything, open Settings > Bluetooth & devices > Printers & scanners, select the queue you actually use, print a test page, and note its driver and port. Update for a documented compatibility problem, security notice, or required feature—not as a blind fix for every printing problem. An installer can create a duplicate queue while applications continue using the old one.
Windows Protected Print Mode is a different path: when it is enabled, Windows uses the modern driverless IPP print stack with compatible Mopria-certified printers and removes third-party printer drivers. Do not try to force a manufacturer driver into that mode; confirm printer compatibility and your organization’s policy first.
Preserve the working queue and its settings
Use only the package Windows Update offers for the printer or a package from the exact manufacturer support page. Match the complete model name, Windows 11 release, and x64 or ARM64 architecture. In a managed workplace, let the print administrator handle a server-supplied queue or driver.
Important caution
A printer driver update is not a fix-all. It cannot correct an empty paper tray, a bad USB cable, an unreachable network address, a damaged document, or a hardware fault.
- Record the active queue name, port or network address, current driver, defaults, and test-page result.
- Apply the applicable Windows Update driver or follow the exact model’s official installation instructions.
- Confirm the original queue still uses the intended driver and port; remove a duplicate only after the original queue has been tested.
- Print a Windows test page and a representative color, duplex, scan, or finishing job for the features you use.
If output or connection worsens
Switch back to the prior queue or driver if it was retained, or reinstall the known-good official package for the exact model. Restore paper size, duplex, color profile, and finishing defaults because package replacement can reset them.
If jobs remain stuck, diagnose the queue and spooler rather than repeatedly adding printers or installing unrelated packages. Preserve a failing document for rendering tests, and use the printer maker’s support route or your print administrator when rollback is unavailable.
Inventory queues, ports, and packages before updating
Two queues can point to one printer, and one driver package can serve several queues. Record each similarly named queue, whether it is default, its port or server path, current driver name, and a test-page result. Check applications with their own remembered printer choice. This inventory prevents an installer-created queue from silently taking over while the original remains unchanged.
Also capture device settings such as Letter or A4, duplex unit, installed trays, color mode, finishing accessories, secure-print method, and accounting codes without exposing credentials. An updated package can rediscover options or return them to defaults. In managed environments, the client may receive its driver from the server; local installation can be ignored or conflict with policy, so the print administrator must own the server-side change.
Validate both routing and rendered output
After the supported installer or Windows Update completes, reopen the intended queue and confirm its driver and port. Do not delete the prior queue until the new or updated path is proven. Print a Windows test page, then a representative document with duplex, color, tray, and finishing requirements. Confirm the job appears in the expected queue and exits at the expected physical printer.
If the package fixes printing but scanning disappears, check whether scan software is a separate component rather than replacing the print driver again. If jobs become garbled, identify the printer language and restore the known-good package or queue. If the installer repeatedly adds queues, stop rerunning it and reconcile them deliberately. Keep the prior official installer and exported settings where supported until several normal work cycles succeed.
Compare old and new paths before cleanup. An IPP queue may use a Microsoft class path while the existing TCP/IP queue uses a vendor PCL or PostScript package; the two version labels are not a useful direct comparison. Print the same representative document through each and score only required features, output, and reliability. If Windows Protected Print Mode is planned, test the supported modern queue separately and confirm organizational policy before removing vendor-driver queues that cannot simply be restored by Driver Roll Back.
Important caution
Removing a shared driver package can affect other local queues. Do not use broad print-driver cleanup tools on a production or managed computer without administrator planning.
- Map every queue to its port, server, driver, and physical destination.
- Preserve required defaults and use the applicable official update method.
- Confirm the intended existing queue changed before removing any duplicate.
- Test routing, basic output, and every required advanced feature.
Example: the installer added a second queue
Do not immediately remove either queue. Print a labeled test page from each and record its port, driver, defaults, and physical destination. Check which queue applications remember and which one exposes required duplex or finishing options. If the new queue is the supported replacement, migrate defaults and application choices before retiring the old one. If the original queue received the new driver and the duplicate adds no value, remove only the confirmed duplicate. On a managed server, ask the administrator to reconcile it because local deletion may be reversed by policy.
Check scanning separately after any full-feature package update. The scan component may use a different network discovery mechanism and may require reselecting the device in the scan application. Do not roll back a proven print fix until you determine whether the maker provides a separate scan-software repair. Keep one dated test page from before and after the change when output quality matters; it provides a concrete comparison for color, margins, fonts, and finishing settings.