Independent printer help. Not affiliated with any printer manufacturer.

What this error means

The Print Spooler is the Windows service that holds print jobs, talks to printer drivers and keeps track of every installed printer. When it isn't running, Windows can't add printers, open printer settings or print, and you may see "The local print spooler service is not running. Please restart the spooler or restart the machine." Starting the service usually clears the message straight away. If it keeps stopping, something such as a stuck job or a faulty driver is crashing it.

Common causes

  • The service was stopped, or crashed and wasn't restarted
  • Its startup type is set to Manual or Disabled
  • A corrupt job file in the spool folder crashes it as it starts
  • A faulty printer driver or print add-on
  • A service it depends on, such as Remote Procedure Call (RPC), isn't running

How to fix it

Start with the first fix. They’re ordered from safest and quickest to most involved.

Fixes for Windows

0 of 7 steps tried

  1. Restart your PC

    A restart starts the Print Spooler again if it's set to start automatically, and it clears any hung print components. If the message is gone after restarting and stays gone, you're done.

  2. Start the Print Spooler and set it to Automatic

    Press Win + R, type services.msc and press Enter. Double-click Print Spooler, set Startup type to Automatic and click Apply. Then click Start and check that Service status changes to Running before you click OK.

  3. Or do it from Command Prompt

    Open Command Prompt as administrator and run the command below. It sets the service to start automatically and starts it now. The space after start= is required. If the service refuses to start, or keeps switching back to Disabled, a policy or a system tweak tool is probably controlling it; on a work PC, ask your IT team rather than overriding it.

    sc config spooler start= auto && net start spooler
  4. Clear stuck spool files

    If the service starts and then stops again within seconds, a damaged job file is a likely cause. In an administrator Command Prompt, run net stop spooler, then the command below, then net start spooler. This deletes every waiting print job but not your documents, so you just print them again.

    del /Q /F "%systemroot%\System32\spool\PRINTERS\*.*"
  5. Check the services it depends on

    If starting the spooler fails with error 1068 ("The dependency service or group failed to start"), open its properties in Services and look at the Dependencies tab, or run the command below and look at the DEPENDENCIES line. Make sure each listed service, such as Remote Procedure Call (RPC), is running and not disabled, then start the spooler again.

    sc qc spooler
  6. Make it restart itself after a failure

    In the Print Spooler's properties, open the Recovery tab and set First failure and Second failure to Restart the Service, then click OK. This keeps printing available while you track down the cause, but it doesn't fix whatever is crashing the service.

  7. If it keeps stopping, find the cause

    Press Win + X, open Event Viewer and go to Windows Logs > Application. Look for errors that mention spoolsv.exe; the faulting module named there often belongs to a printer driver. Remove that driver with printui /s /t2 (choose Remove driver and driver package), reinstall a current one from the manufacturer's official site, and run sfc /scannow from an administrator Command Prompt if the crashes continue.

Common questions

Is it safe to set the Print Spooler to Automatic?

Yes, on a computer you print from it's the normal Windows setting. Some organizations disable the spooler on PCs that never print as a security measure, so on a work computer check with your IT team before changing it.

Will clearing the spool folder delete my documents?

No. The folder only holds temporary copies of jobs waiting to print. Your original files are untouched, and you can send them to the printer again.

The spooler starts but the message comes back minutes later. Why?

The service is starting and then crashing, usually because of a damaged job or a faulty driver. Clear the spool folder, then check Event Viewer for the file that caused the crash.

Press Enter to see all results. Use ↑ ↓ to move.