Print Spooler Won't Restart: What to Do
The Print Spooler hangs, restarting it fails or the service keeps stopping? How to kill it, clear the print queue and find the driver that crashes it.


Restarting the Print Spooler sounds like one click. Until it refuses to start again.
“Restart the Print Spooler.” A clear instruction from a support chat, and the classic when the printer doesn't print. The service was running, set to automatic start, the restart was triggered, and it failed. A look at the queue showed the reason: on the default printer, an inkjet multifunction device in the office, several print jobs were stuck and blocking the service. Before they were deleted, a question came up: should all jobs be removed? They have to be sent again afterward.
When the normal restart of the Print Spooler doesn't work, you need a few more steps. The basics about the print queue are in Printer won't print: fixing the print queue; this article is about the stubborn cases.
Why does the restart fail?
- Stuck print job – Service stays at “Stopping”, jobs in the queue
- Faulty driver – Service starts and stops again immediately, event 7031/7034
- Missing administrator rights – Message “Access is denied”
- Service disabled by policy – Startup type “Disabled”, can't be changed
- Dependent service not running – Error 1068 (the dependency service or group failed to start)

Step 1: Check the status and the error message
PowerShell as administrator:
Get-Service Spooler | Select-Object Status, StartType
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Service Control Manager'} -MaxEvents 20 |
Where-Object Message -match "Druckwarteschlange|Print Spooler" | Select-Object TimeCreated, Id, Message- If the service is set to Disabled and can't be changed, a Group Policy is usually behind it. That is a deliberate setting by IT.
- If 7031 or 7034 show up several times, the service is crashing. Continue with step 4.
Step 2: Kill the hung service
If the service hangs while stopping, the only thing that helps is to end the process directly:
taskkill /F /IM spoolsv.exeAfter that the service is stopped, even if Services still shows “Stopping” for a moment.
Step 3: Clear the queue and restart
Now remove the stuck jobs. But first: let people know that jobs that haven't been printed will have to be sent again, as in the real case, where someone asked before deleting.
del /Q /F "%systemroot%\System32\spool\PRINTERS\*.*"
net start spoolerThen print a test page: Settings › Bluetooth & devices › Printers & scanners › printer › Print test page.
Delete only the jobs of a single printer (the service has to be running):
Get-PrintJob -PrinterName "Büro Drucker" | Remove-PrintJobStep 4: If the service keeps crashing
Then a printer driver is almost always to blame. At startup, the spooler loads all installed drivers; if one is faulty, it takes the service down with it.
- Open Print Management: Windows+R ›
printmanagement.msc(not available in Home editions; there, useprintui /s› Drivers tab). - Under Drivers, look for old, duplicate or unknown drivers, often a recently installed one.
- Remove the suspect driver (delete the associated printer first).
- Start the spooler and check whether it runs stably.
- Set the printer up again with the current driver from the manufacturer.

14 days free
IT support that fixes itself.
SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.
Start free trialThe Microsoft-Windows-PrintService/Admin log in Event Viewer (under Applications and Services Logs) often names the driver that is causing problems.
Which drivers exist and which printer uses which:
Get-PrinterDriver | Select-Object Name, Manufacturer, DriverVersion
Get-Printer | Select-Object Name, DriverName, PortNameMore about drivers: HP Universal Print Driver: traditional or dynamic?.

Step 5: Configure recovery
So that the spooler restarts itself after a crash: services.msc › Print Spooler › Properties › Recovery › for the first and second failure, Restart the Service. Details: Restart a Windows service automatically. This doesn't fix the cause, but it makes sure not every crash turns into a phone call.
Print server instead of workstation?
If the printers run through a print server, a hung spooler there affects all users. The same steps apply, but on the server and ideally outside working hours. If the print server can't be reached at all, the cause is elsewhere: see Windows Server shuts down every hour.


How does SuperSupport help with spooler problems?
In the case described, the SuperSupport agent checked the status of the Print Spooler, tried the restart, read the default printer's queue after it failed and found the stuck jobs. Before deleting, it asked the user, because jobs are lost in the process. What this looks like for internal IT teams and IT service providers is described on the respective pages.
Frequently asked questions
Why won't the Print Spooler restart?
Usually the service is stuck on a faulty print job or driver and no longer responds to being stopped. Other causes are missing administrator rights, a service configuration locked by Group Policy, or a driver that makes the service crash again right at startup.
How do I kill the Print Spooler when it hangs?
In a Command Prompt as administrator, with taskkill /F /IM spoolsv.exe. Then delete the files in the folder C:\Windows\System32\spool\PRINTERS and restart the service with net start spooler.
Are print jobs lost when I clear the queue?
Yes, all jobs that have not been printed yet are deleted and have to be sent again. So give people a heads-up first, especially with shared printers.
The Print Spooler keeps stopping on its own. Why?
Almost always because of a faulty printer driver. The System log then shows event 7031 or 7034 for the Print Spooler service. Remove the suspect driver in Print Management and replace it with a current version from the manufacturer.
Do I need administrator rights to restart the Print Spooler?
Yes. Without administrator rights you get “Access is denied”. In companies, IT takes care of this, or a tool that carries out the action after approval.

14 days free
IT support that fixes itself.
SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.
Start free trial
Nico Haslberger is Co-Founder & CEO of SuperSupport.ai. With years of experience as an IT technician, he knows the problems in IT support first-hand: from overloaded help desks to recurring tickets that slow teams down. That knowledge is built into every feature of the platform today. He makes sure SuperSupport.ai solves exactly the problems he experienced himself for years.
This article was created with AI assistance and editorially reviewed.
Related Articles

Restart a Windows Service Automatically If It Stops
A program feature suddenly stops working because a background service stopped? Find the service and have Windows restart it automatically from now on.

Microsoft 365 Quarantine: How to Release an Email
An important email is stuck in Microsoft 365 quarantine? Here is how to check it, release it, and keep it from happening again.

Remove Local Admin Rights: How to Do It Without Chaos
Admin rights are a security risk, but removing them floods the helpdesk. How SMBs remove local admin rights: preparation, LAPS, Intune, GPO, exceptions.