Windows command guide
Restart the Windows Print Spooler Service
Windows printing depends on the Print Spooler service to queue documents, hand jobs to the printer, and manage communication between apps and print devices. If the spooler hangs or gets jammed by a bad job, printing can stop for every application until the service is restarted.
This guide is written around the specific symptom-command match for restart print spooler, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
net stop spooler && net start spooler
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: Documents remain stuck in the print queue
- Run the service or app repair line exactly as shown: net stop spooler && net start spooler.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Re-open the affected app, service, or feature and check whether the same component still fails.
- If the issue persists, check service state, dependencies, package integrity, or event logs before doing a broader repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
net stop spooler && net start spooler
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
sc query spooler
What problem this command is trying to solve
This command targets stuck print queues, non-responsive printer jobs, and printing failures caused by the spooler service itself rather than by paper or hardware issues.
- Documents remain stuck in the print queue.
- A printer appears online but nothing actually prints.
- New print jobs fail because one broken job blocks the queue.
How the command works
The command stops the Print Spooler service and starts it again. That clears the active service state and often breaks the loop caused by stuck queue handling.
When it makes sense to run it
Use it when Windows sees the printer but print jobs are frozen or the queue behaves abnormally. It is a common first repair step before removing printer drivers or rebuilding the whole printer setup.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running net stop spooler && net start spooler.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: documents remain stuck in the print queue.
- Identify the exact Windows component that is failing before you use net stop spooler && net start spooler, so you do not reset unrelated parts of the system.
What result to expect
After running net stop spooler && net start spooler, compare the result against the symptom that brought you here. The most useful checkpoint is whether documents remain stuck in the print queue becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after net stop spooler && net start spooler is to repeat the action that previously triggered the problem. If a printer appears online but nothing actually prints still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes a Windows service, package, or built-in app component. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Restarting the spooler can cancel jobs that are currently waiting. If the problem returns immediately, a broken driver, print processor, or queue file may still be involved.
When this is probably the wrong fix
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.
What to do if it does not help
If net stop spooler && net start spooler does not improve documents remain stuck in the print queue, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about a Windows service, package, or built-in app component.
Frequently asked questions
Should I use net stop spooler && net start spooler for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets stuck print queues, non-responsive printer jobs, and printing failures caused by the spooler service itself rather than by paper or hardware issues.
What should I check right after net stop spooler && net start spooler?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether documents remain stuck in the print queue becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on net stop spooler && net start spooler alone?
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.