Reading Time: 2 minutes
Whether it is Home or Office, Printer has increasingly become a necessary accessory in everyday life. Printers are essential to take print documents, create projects, take picture printouts etc. Most printer issues are simple connectivity or software issues, but it can get complicated at times.
One of the problems in Printer is when multiple documents are sent to the printer to take printouts. These printouts might come from a device directly connected to the printer using a wired or wireless connection, or it might come from any of the devices in a network.
When multiple printouts are sent to a printer, the printer saves these documents to a spooler where the information is stored in a queue. The printer takes this information one by one on FIFO basis (First In First Out) and takes printout thereby releasing the queue.
Sometimes the print spooler may stop working completely. If this happens, you won’t be able to send any more printouts to the printer queue. The printer stops working completely or it might become painfully slow.
Solutions to fix Print spooler problems in Printer
- Double click on the Printer icon on system tray. From the pop-up window, select Cancel All Documents. In simple issues, this should fix the problem. If the entries inside print spooler refuse to go, try the next step.
- Press Windows Key + R to open the Run window. Type services.msc to open services window. Scroll down to Print Spooler service and double-click to open Properties. Click on Restart to restart print spooler service. If the service is not started for some reason, you need to click Start to start the service. If the step didn’t work, try the next step. This is the same as what we did in Step 2 but sometimes command prompt works better.
- Open Command prompt with admin rights. Try the following command in following order.net stop spooler
del / q / f / s “% systemroot% \ System32 \ Spool \ Printers \ *. *”
net start spooler
Check if the problem is fixed.
- Restart printer and check if the problem is fixed.
Hopefully, this should fix the problem. You may use the comment section for feedback or any further queries.