ToolTip AI

Windows printing,
queue by queue.

The printer screens fail in a way almost nobody reads: the error is in a component you cannot open, describing a state you did not set. Twelve entries, ordered from the machine's own service outward to the device.

spooler · type 3 · type 4 · ipp · wsd · point and print

How to find which of the four layers refused the job.

A print failure belongs to one of four layers, and only two of them are visible in the queue.

Application, driver, spooler, device. The dialog reports the fault as though it were one event, and it names the printer even when the printer is the only part that worked. The reason a printer page feels unreadable is that it shows a status assembled from three of those layers at once.

The useful separation costs one test: print to a file. A file that comes out right means the application and the driver agreed, so the fault is downstream in the port or the device. A file that comes out wrong means nothing was ever sent correctly, and every network setting you change from that point is wasted.

  • Print to PDF first. It uses the same rendering path and skips the network, so it splits the problem in half in thirty seconds.
  • Read the status as flags, not as a sentence. Offline, Paused, Error and Not Sharing come from different places and two of them were set by a person.
  • One service owns every queue. The spooler is shared, so a stuck job and a crashed driver are machine-wide events, not printer events.
  • Driver type is not a preference. Whether a device needs a vendor package is decided by the driver model, and the model changed in 2021 for security reasons nobody asked you about.

The twelve places a print job can be refused.

Ordered from inside Windows outward to the device at the other end of the cable.

The queue you can see is a service you cannot
What it is
Every print job on the machine goes through the print spooler, a single Windows service (Spooler, running as spoolsv.exe) that owns the queue, hands documents to a port monitor and waits for the device. The window titled with your printer's name is a view of that service's store, not a property of the printer.
What changes
Because it is one process for all printers, one job that never completes can hold the queue of an unrelated device. The files that hold those jobs live in the spool directory under System32\\spool\\PRINTERS as .SPL and .SHD pairs; stopping the service, removing those files and starting it again clears the stuck job and the document that was waiting behind it. Jobs already sent to a network printer's own memory are not cleared by that, which is why a page sometimes still arrives after you deleted it.
Risk
Careful Restarting the spooler is safe for the machine and destructive for other people's jobs: on a shared print server the restart clears the queue everyone else is watching.
Type 3 and Type 4 drivers, and why the difference decides who can install one
What it is
A Type 3 driver is the older vendor package: a user-mode component plus a kernel-mode data file for the device, often a .inf that Microsoft never signed as a class driver. A Type 4 driver is the modern one: XPS-based, no kernel component, and the class driver ships with Windows so the vendor only supplies a description file.
What changes
Type 3 needs to run inside the print system, so installing one changes what runs with the spooler's privileges; Type 4 needs no kernel code at all, which is why a generic print-to-IP or a modern network printer can work with no vendor package. It also explains a page that prints with the wrong margins or no graphics: the class driver you got is a text-and-simple-graphics driver, and the vendor's Type 3 was the one that understood the device's fonts and duplex unit.
Risk
Reversible Nothing about the type is an error. Reading which one you have tells you whether a printing defect is a driver gap or a device setting.
Point and Print, and the two security changes that broke shared printers in 2021 and 2022
What it is
Adding a printer that is shared from another computer copies the driver from that server to your machine, through a remote procedure call. That mechanism, named Point and Print, was the route of the PrintNightmare vulnerabilities, so its rules changed twice in one summer.
What changes
The changes restrict who may install a driver this way: an authenticated user gets a driver already present on the server, and installing a new one becomes an administrator action. The second change closed anonymous connections to a print share over the file-sharing protocol, which is why a printer that had been shared from a home or small-office PC for years stopped being reachable from other machines, and why the failure looks like a network problem rather than a policy one.
Risk
Expensive The usual response is to loosen the policy back, which reopens the hole that produced the change. The two honest fixes are an IPP or TCP/IP connection to the device itself, or hosting the share on a server whose driver the client can validate.
Ports: WSD, TCP/IP, USB and the one that quietly stops working
What it is
A port is the address the spooler writes to, and it is a property of your machine's configuration, not of the printer. WSD ports come from discovery: Windows found the device with the Web Services protocol and recorded a handle. Standard TCP/IP ports record an address. USB ports bind to the physical connection, and a Local Port writes to a file path.
What changes
A WSD port is the one that betrays you: it follows the device, so when the printer's address changes after a lease renewal the port may still resolve and printing may still work, or it may stop with a queue that says Error with no other clue. Converting that printer to a static TCP/IP port, addressed to a reservation on the router, is the change that makes the problem stop recurring. A Local Port aimed at a file is not a defect but a feature, and it is how a printer ends up producing nothing visible while the queue reports successful jobs.
Risk
Careful Switching port type re-routes the device without asking you to reinstall it. The reverse direction, deleting the port an installed printer still points at, leaves a printer that cannot be removed until its port exists again.
Offline, Paused, Not Sharing, Error: four words that name four different causes
What it is
The status line in the queue is composed from independent flags. Offline means the spooler could not reach the port. Paused means somebody told the queue to stop accepting or releasing work. Error means a job failed in the driver or the device refused it. Not Sharing is a property of a shared printer being unpublished.
What changes
Two of the four are reversible by a person rather than by the machine: there is a Use Printer Offline switch in the queue's own menu and a Pause Printing switch, both of which get set by accident and stay set after the printer is healthy, and both of which are greyed in the tray when you are looking at the wrong printer. The manual state persists across restarts, which is why a printer can be offline for weeks while the device answers a ping.
Risk
Reversible Before any deeper repair, look for a tick next to a manual flag. Half of the weekend diagnosis in this family is unchecking one of two menu items.
The driver is a 64-bit package and the application is 32-bit
What it is
Printing is one of the few places where the bitness of a program is visible to the user. The 32-bit and 64-bit print components cannot load each other's driver, so an older 32-bit application on a 64-bit system prints through a separate path, and a printer that works everywhere else can fail only inside that one program.
What changes
The mismatch produces a short list of printers inside the affected application, an access-violation dialog when you open the print setup, or a job that disappears into the queue and never arrives. Adding the matching driver for the other architecture on a print server is the intended answer for shared devices; on a workstation the answer is usually the specific application's own print path, and knowing which one you are looking at prevents reinstalling a driver that was never the problem.
Risk
Careful Reinstalling the good 64-bit driver to fix a 32-bit application changes nothing and can remove the only working configuration of the other programs on the machine.
Microsoft Print to PDF and Fax: the two printers that are not printers
What it is
Both are installed by Windows as features rather than by a vendor, and both are diagnostic instruments. Print to PDF renders the job through the graphics pipeline and writes a file instead of sending anything anywhere, which is the closest thing to a proof of what the application actually produced.
What changes
Because the output is a file, you can separate the two possible faults that look identical: if the PDF is right and the paper is wrong, the problem is in the real printer's driver or its device settings; if the PDF is wrong, the driver is innocent and you have an application, a document or a font issue. Turning the feature off removes the printer from every application's list, and some very old installers assume the feature exists.
Risk
Reversible This is the cheapest useful test available on the machine, and it prints nothing, wastes nothing and touches no configuration.
Windows manages your default printer, and it is not being malicious
What it is
A setting called Let Windows manage my default printer picks the last printer you used, per location and per network, and it changes the value that applications show when they open the print dialog for the first time.
What changes
Turning it on produces the effect people describe as the printer changing by itself: printing at a different site, or connecting to a different network, promotes whatever you last used there. Turning it off restores a fixed choice, which is what a kiosk, a label printer or an office queue needs. The default is a per-user setting, so a second account on the same PC can have a different one, and an application that caches its own last-used device can disagree with the system value.
Risk
Reversible Nothing breaks. The cost is surprise, and the fix is one switch and a deliberate choice.
The modern print dialog and the classic one are different screens with different omissions
What it is
Applications built on the modern Windows controls show a compact dialog with a Printer properties link that opens the classic page; applications using the old common dialog show the full page immediately. Which one you see is a property of the program, not of the printer.
What changes
The compact form hides the device settings that actually decide duplex, paper source and quality, and it hides them behind one link whose label differs between versions of Windows. The classic page can show fewer printers than the system has, because it enumerates them at open time. When a setting you need does not exist in the dialog, the answer is usually that you are in the other dialog, and opening the printer's own properties page from Settings gives the same controls with more room.
Risk
Reversible No risk. Knowing which dialog you are in saves the search for a duplex option that is one link away.
Scan-to-printer, Mopria, AirPrint and IPP: four names for one modern protocol
What it is
Internet Printing Protocol is the transport that lets a device be added over the network without a vendor driver, and it is the reason AirPrint devices, Mopria devices and a modern Windows machine agree. The class driver Windows installs for these is a generic one, and it is deliberately minimal.
What changes
Adding a network printer through the modern settings page usually takes the IPP route even when the old TCP/IP port path is available, which explains a printer that appears with a plain name and no vendor features. The generic driver prints documents correctly and omits device-specific options such as finisher trays, custom paper sizes and staples, because those live in the vendor package. Where a shared queue over the file-sharing protocol stopped working, IPP over the web port often works and is the direction the platform is moving.
Risk
Reversible Choosing the generic IPP path is the safe default for a personal device; the feature loss is the trade, and it is visible in the dialog rather than hidden.
Jobs that print blank pages, wrong colours or a page of garbage
What it is
Three distinct failures that people describe with the same sentence. A blank page says the driver and the document disagree about colour space or transparency. Wrong colour says a colour management path is being applied twice, or the device is set to a greyscale or economy mode. A page of meaningless characters says the data reached the device in a language it does not speak, typically a PostScript job sent to a non-PostScript printer.
What changes
The garbage page is the useful one: it proves the network path and the queue are working, and that only the data format is wrong, so the fix is the driver or the protocol, never the cable. Blank pages respond to a driver change more often than to any setting, which is why changing the port to raw or adjusting a tray produces nothing; the raw-bytes test is what converts this from guesswork into a decision.
Risk
Careful Switching between vendor and class drivers to see what changes also changes which device features are available, so note the driver name before you experiment.
Removing a printer does not remove the driver, and the leftovers cause the next problem
What it is
Uninstalling a printer deletes the queue and its port mapping. The driver package stays in the driver store so another printer, or the same one re-added, can use it without a download. In Print Management the two actions are separate, and only one of them is offered in Settings.
What changes
Old drivers are the classic cause of a queue that now prints somewhere else, of a device that keeps being re-added by discovery, and of a spooler that crashes at start because a loaded package faults. The console has a driver-installation setting that can be tuned to allow only signed or only present packages, and it is also where a package can be removed when it is no longer in use. Removing the driver while a printer still references it leaves a device that cannot print and cannot be repaired except by reinstalling both.
Risk
Expensive The cleanup that feels tidy is the one that takes away the working configuration of a device you use every day and cannot re-add without the vendor's package.

A printer is the one device that fails without an error code.

Windows has no dialog that says which layer refused the job, and a queue that reports success is not a page that was printed. That gap is where the guessing starts, and it is also why the two tests worth remembering are the cheapest things on the machine: print to a file, and look for the tick next to a manual flag.

Get ToolTip AI on Microsoft Store
Windows 10 build 19041 or newerWindows 1164-bit onlyNo administrator rights
Part of the guides library.