Member Avatar for G.W.

I was trying to install a new printer on an existing print server that housed another printer and now my print spooler won't stay on.

I've gone in now several times and turned it on but it keeps going back off within about a min.

Can anybody help with this?

  • 4 Contributors
  • 3 Replies
  • 116 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by xcellpro6

Dani AI

Generated

Quick summary and where to start: this pattern (spooler starts, then dies shortly after a new printer is added) almost always points to a driver or driver-package problem on the server. describes the classic symptom; and were right to focus on drivers and logs, and ’s note about drivers on client machines is a good reminder. Below are immediate stabilizing steps, a focused way to identify the offending component, and safe next actions.

Immediate, safe restore (run an elevated command prompt before these): stop the spooler, clear any stuck jobs, then restart it.

net stop spooler
del /q "%windir%\System32\spool\PRINTERS\*.*"
net start spooler

If that keeps the service up, the spool folder had a bad job. If the service still dies, collect the failure detail next: open Event Viewer -> Windows Logs -> System (and Application) and note the print-spooler entries at the time it stopped. Look for the faulting module or a DLL name (that tells you which vendor/driver caused the crash) and the Event ID.

Targeted remediation: once you have the suspect driver name, remove or replace that specific driver package (don’t simply remove every driver). On newer servers use Print Management (printmanagement.msc) or Driver Store tools. To list driver packages:

pnputil -e

Then remove the related package with

pnputil -d oemXX.inf

(or use Print Server Properties -> Drivers if you prefer the GUI). Install the correct architecture (x86 vs x64) signed driver from the vendor or test with a Microsoft generic driver to confirm. On modern Windows, consider using Printer Driver Isolation for third‑party drivers so a bad driver won’t crash the spooler.

Additional cautions and follow-up: set the Print Spooler service Recovery (Services -> Print Spooler -> Recovery) to restart on failure while troubleshooting, run SFC if system files look suspect, apply relevant OS updates/hotfixes, and scan for malware if anything looks unusual in logs. Avoid removing drivers that are in use by other printers without planning a maintenance window.

Recommended Answers

All 3 Replies

Member Avatar for freshfitz

Seen this before and forget what I did, Try going into printers and faxes uninstall the print drivers you are not using. Right click the white space in printers and fax's goto server properties to uninstall. Also is there anything in the event log?

Member Avatar for sally864

We have the same problem. We had to move our printers to a new server (if you are lucky enough to have one) and then look for a hotfix from Microsoft. Did you check to make sure there wasn't some type of virus blocking it from starting?

Member Avatar for xcellpro6

Hi

Make sure that you install the printer drivers on your computer as well.... Install new printer .... select network printer .... find the printer and install drivers.... Make sure the printer is shared on the server so it can be seen on the network

hope this helps
Darren

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.