Tag Archives: stopping

Print Spooler Service keeps stopping – KB1039981


Description:  Print Spooler Service keeps stopping.

Common customer description: Need a new printer installed.

Probing questions:

Have you ever printed to this printer before?
Is this a new printer to everyone?

Steps to isolate: If the Print Spooler Service keeps stopping or restarting there is a good chance an incompatible driver is installed.  Look at all their printers and verify that the model numbers are correct.  If one or more are not correct you will need to remove them.

Steps to resolve: Once you have cleared out the incompatible drivers you will need to install the correct drivers.  Find out the exact model of printer and then locate the printers on the Manufactures website for that exact model for their version of Windows.

Additional considerations: Keep in mind that not all 64bit OS’s need to use 64bit printer drivers but all 32bit OS’s will use 32bit printer drivers.

Task Killing a Service that is Stuck on Stopping/Starting with Command Prompt – KB1039927


Description:  Trying to stop or start a service but the service is stuck on “Starting” or “Stopping”

Common customer description: Why is one of my Windows services stuck on “Starting” or “Stopping”?

Probing questions: Was your computer and/or server rebooted recently?

Did you try stopping or restarting a service?

Steps to isolate: Check previous tickets

Check system info

Steps to resolve:

1. Connect to the server and go to Windows Services

2. Find the service that is stuck on “Starting” or “Stopping”

3. Right click on the service and go to properties

4. Find the service name and make a note of it

Service name

5. Start Command Prompt as Administrator

cmd admin

6. Type in this command: sc queryex [service name]

  • In this case the service name is spooler

sc queryex

7. Press enter now find the PID for the service

  • For the Print Spooler, the PID is 1552


8. Next type in this command, taskkill /f /pid [PID of the service]

  • For this example, it would be: taskkill /f /pid 1552

task kill

9. Press enter, if it worked you should see this



Additional considerations: If the command came back with an error, check to make sure that the spelling is correct for the commands. Check to make sure that the PID is also correct. Sometimes it will seem like it didn’t work and you will see the start button again to start the service.

If none of these work, the next step would be to reboot the server. Call the customer to schedule a reboot of the server.

If you need additional help, consult with a Tier 2 tech