Printer Is in an Error State Is Not a Windows Error

The phrase sounds like something Windows has done to you. It reads like a system fault, so that is where everybody starts looking. The good news is that the real answer is usually much quicker than the afternoon people spend on it.

Microsoft's own page points the other way in one sentence, and almost nobody quotes it.

I went to the vendor wording first, then to owners who had it, and the useful part turned out to be a single test that decides which half of the problem you have.

What Microsoft actually says about that phrase

One sentence, and it changes where you look. Microsoft states it on its printer problems page.

If the status shows "Printer in error state," there may be a problem with the printer itself. Windows is repeating, not diagnosing. The printer reported a condition and Windows printed the label it was handed.

So a spooler reset does nothing when the machine in the corner is the one complaining. Start at the printer, then come back to Windows if the printer is fine.

The test that decides which half you have

Two minutes, and it saves you from fixing the wrong computer. Print anything from a second device, a phone, another laptop, anything at all.

It fails everywhere? The printer is the problem. Go and look at it. It works from the other device? Windows on this PC is the problem, and the printer is fine. You can stop poking it.

Reported by an owner on Microsoft Q&A, exactly the second case. Their HP printed from two machines downstairs and refused from the laptop upstairs. The printer's own web page read "ready to use" from the failing PC.

If it fails everywhere: the four things Microsoft names

Boring, physical, and the actual cause most of the time. Microsoft lists them together: check the printer "for low paper or ink, and be sure the cover isn't open and the paper isn't jammed."

A cover that is nearly shut counts as open. Press it until it clicks, and do not judge it by eye.

Low ink stops some printers outright. Whether Windows can even read the level depends on the model.

And a jam can be a scrap you cannot see. The paper path has places a torn corner hides.

The power cycle, with Microsoft's own timing

Not the same as switching it off and on quickly. Microsoft's instruction: "Turn off your printer and unplug it, wait 30 seconds, plug your printer back in, and then turn the printer back on."

The unplug is the part people skip. A printer holding an error condition often keeps holding it through a normal power button press.

Thirty seconds is not superstition here. It is the figure in the vendor instruction. Use it rather than a guess. Do this before any Windows step. It costs you a minute and it clears a good share of these.

If it only fails from this PC

Now it is worth touching Windows, and there is an order. Microsoft sends Windows 11 and Windows 10 users to the same place first.

"start by running the automated printer troubleshooter in the Get Help app. It will automatically run diagnostics and attempt to fix most printer problems." Then the spooler, which is the queue your jobs sit in.

Microsoft's steps: "Press Windows key + R, type services.msc, and press Enter," find Print Spooler, then "Right-click on Print Spooler and select Restart." A stuck queue survives that restart.

Microsoft names the folder to empty: %WINDIR%\system32\spool\PRINTERS, with the spooler stopped. Driver last, not first. Reinstalling a printer driver is a bigger job than it looks.

The case that does not resolve, reported honestly

Ours to say plainly, because no competing page does. An owner with a Brother HL-L2395dw checked everything physical first, the way you would. Their words: ink, paper and jams "all fine", printer online, troubleshooter run.

Windows took a long time to connect, showed printing, then showed the error state. A slow connect before the error is a network symptom, not a paper one.

It printed once after two hours and went straight back to the error on the next job. Nothing in the thread fixed it and the question closed unanswered.

That pattern points at the connection rather than the printer or the queue. A wireless printer that answers slowly is worth checking as an offline problem instead.

What this machine reports

Ours, read before writing any of the above. Four printers installed, all reporting status Normal. Three are virtual, which is what your list probably looks like too.

The Print Spooler service reads Running, on an Automatic start type. That is what healthy looks like. Zero jobs queued anywhere, and an empty queue cannot be blocking you. Yours is worth checking for the same reason.

None of that proves your printer is fine. I am showing you what the Windows side looks like when nothing is wrong with it.

**Status: the printer side of this was read on 18 September 2026 from a Windows 11 Home laptop running 25H2, covering the installed printers, their status, the spooler service and every queue.

Microsoft's printer page supplied the error state sentence, the four physical checks and the 30 second power cycle, and its spooler page gave the restart steps. Nothing was printed and no setting was changed.**

What does "printer is in an error state" mean in Windows?

It means the printer reported a problem back to Windows, and Windows displayed that. Microsoft's own wording is that there may be a problem with the printer itself.

It is not a Windows fault code, so the spooler and the driver are rarely where the answer is.

How do I fix a printer in an error state?

Print from a second device first. If that also fails, check your paper, ink, the cover and for a jam, then unplug the printer for 30 seconds.

If the other device prints fine, the problem is on this PC, so run the troubleshooter in Get Help and restart the Print Spooler service.

Why does my printer work from my phone but say error state on my PC?

Because the printer is healthy and this PC's connection to it is not.

One owner reported exactly that, with the printer's own web page reading ready to use from the machine that would not print. Treat it as a Windows and network problem, not a printer problem.

Does restarting the print spooler fix an error state?

Only when the fault is on the PC. Microsoft's route is Windows key and R, services.msc, then right-click Print Spooler and choose Restart.

If the printer is reporting a real condition, the spooler restarts cleanly and the error comes straight back.

The Short Version

• Microsoft says the phrase means there may be a problem with the printer itself.
• Print from a second device. That one test splits the printer from the PC.
• Fails everywhere: check paper, ink, the cover and a jam, in that order.
• Unplug the printer for a full 30 seconds, which is Microsoft's own figure.
• Fails only here: the Get Help troubleshooter first, then the spooler.
• Restart Print Spooler through services.msc, and empty %WINDIR%\system32\spool\PRINTERS if a job is stuck.
• A slow connect before the error points at the network, not the paper path.
• Four printers here all read Normal with the spooler running and no jobs queued.

Where to Next

Go and look at the printer before you touch anything on the computer, because the message is telling you to. Print from a phone to find out which half of this you are dealing with, then stop working on the other half.

Give it the full thirty seconds unplugged rather than a quick off and on. And if it only misbehaves from one machine, treat it as a connection problem and leave the printer alone entirely.

If yours showed the error with a symptom that is not on this list, say what the printer was doing at the time in the comments. Those details are what make the next version of this better.