Printer Offline After Update

Question

Hi,

I have problem after windows update, my printer going offline.
Solution I had do:

1. reinstall the driver
2. Clear install printer

But still offline, then I try to restart service "Printer Spooler" at services, It's worked the printer come to Online again.
But, after 10 minutes the printer going offline again.

Do you have solution for this case?

My printer is DocuCenter FX-3373

Answer 1

Hi @Rauf

Your printer is offline apparently due to no communication with the attached computer. The reason behind this error may be related to the software or hardware. To further narrow down the issue, Please follow steps to get your printer back online.

1. From Search “Printers and Scanners” in the search menu bar as shown in the image, and click on open.
2. A new window for Printers & Scanners will open.
3. Select your printer in the provided list and click on “Open queue”.
4. A new window will open for your selected printer.
5. Click on “Printer” located at the top right corner in the box.
6. Uncheck “Use Printer Offline”.

On your Printer

1. Check if your printer is in sleep mode, a short press to the power button usually wakes the printer.
2. Check if there are any error lights prompting on the printer. Check the paper tray and cartridge.
3. Restart the printer after following the above two steps and send a print job again.

Additionally , Please have a look on below guide from Microsoft to resolve printer related issues.

https://support.microsoft.com/en-us/windows/troubleshooting-offline-printer-problems-9f5e98ed-0ac8-50ff-a13b-d79bf7710061

Hope this answers your question :)
Thank you.

--
--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

I mostly solved a problem where the Print Job get Stuck in the Printer Queue. My affected Computers uses Intel Network Drivers.

I used MSCONFIG to Disabled All the Non-Microsoft Services. After wards, I clicked Apply, and Ok: and selected the Exit and restart option. Periodically, A restart is needed, but I guess that's because something started the Offending Service. I suspect it's an Intel Bloatware service.