Printer in error state, what it means and what to do
This message is Windows passing along a shrug: the printer told the PC something is wrong, or stopped answering in the expected way, and Windows does not know more than that. The actual diagnosis is nearly always on the printer itself, a flashing light pattern, a display message, or a code. Treating this as a Windows problem first is the common mistake; read the printer, then clear the PC's state.
The fix, in order
- Read the printer's own display or lights. Note the exact message or code (for example a brand code like B200 or 49) and any flashing pattern. That detail is the real error; look it up by the code rather than by this generic Windows wording.
- Clear the physical basics. Paper loaded and seated, no jam anywhere along the path (check the rear access panel too), ink or toner present, all covers and trays fully closed. Cover and tray switches are a frequent hidden trigger of the error state.
- Power cycle the printer properly. Turn it off, unplug the power for 60 seconds, and plug it directly into a wall outlet rather than a strip if possible. This clears latched error states that a quick off-and-on does not.
- Clear the Windows queue and restart the spooler. Cancel every job in the print queue, then restart the Print Spooler service. A corrupt job at the head of the queue can hold the printer in an error state from the PC's side.
- Reconnect the printer. For USB, reseat the cable at both ends or try another port. For network printers, confirm the printer's IP still matches its Windows port, since an address change reads as an unresponsive, error-state printer.
- Remove and re-add the printer if the state is stale. If the printer's own display is happy but Windows insists on error state, delete and re-add the printer, reinstalling the vendor driver from the manufacturer's site. The stored device state Windows is quoting is corrupt in that scenario.
If it still happens
If the printer's display shows a specific code, that code's meaning governs, and some of them (printhead and fuser faults especially) are hardware failures no PC-side step can clear. A printer that enters error state mid-print on large jobs but handles small ones may be overheating or running out of memory on complex pages; splitting the job or printing as image in the reader's options tests that.
Common questions
Why does Windows just say error state instead of the real problem? Windows receives a limited status report from the printer. Many models report only a general fault flag over the connection, keeping the detail on their own panel, so Windows honestly has nothing more specific to show.
Can a document cause the error state? Yes. A malformed print job can fault the printer's interpreter, which then reports an error state until the job is cleared from the queue and the printer is power cycled. If the state returns only for one document, that document is the fault.
Related errors