A print job remains stuck on Deleting
What to do first
A print job remains stuck on Deleting. An application or driver may hold a spool file, preventing Print Spooler from processing the queue. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows Print Spooler
- Versions and conditions
- Windows 11 (confirm the edition and hardware requirements for the feature)
- Error codes and identifiers
- Spooler
Symptoms
- A print job remains stuck on Deleting.
- The same condition can persist after a retry or restart.
Causes and conditions
An application or driver may hold a spool file, preventing Print Spooler from processing the queue.
Before you start
- Save open documents and allow time for a Windows restart if required.
- Run administrative actions only on a personally managed PC or with administrator approval.
- Save the diagnostic command output so the before and after states can be compared.
Precautions
- Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
- Do not run unofficial scripts or unknown drivers with administrator rights.
Step-by-step instructions
Open Settings > Bluetooth & devices > Printers & scanners, select the printer and choose Open print queue. Check document names and owners and cancel only your own unwanted jobs. Do not remove other users’ jobs from a shared printer.
Close the printing application, confirm that interrupting printing is acceptable for other users, and record the affected queue and jobs.
Close the source application and reopen the queue. If a cancelled document remains, proceed to restart Print Spooler; do not resubmit it first because that can print duplicates.
If cancellation does not take effect, press Windows key + R and open services.msc. Right-click Print Spooler, choose Restart, and confirm its status returns to Running. Leaving it stopped prevents printing; if it cannot start, record the error and contact your administrator.
Confirm that Print Spooler is Running in Services. Open the affected printer’s Printer properties, print one test page and check that its job leaves the queue.
Check the result
- The feature starts, connects, or completes without the original error.
- The verification command reports the expected enabled, healthy, or connected state.
- The result remains correct after a Windows restart and no new matching critical event appears.
If the problem continues
- If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
- If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.
Scope of this guide
Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.
Frequently asked questions
Can printing continue while Spooler is stopped?
No. Other users' jobs also stop, so coordinate downtime on a shared print server.
Should I delete the entire spool folder?
Confirm the affected jobs after stopping Spooler and avoid bulk deletion on a shared server.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
- WSL 2 error 0x80370102 prevents a distribution from starting
- Restore the WSL optional component when error 0x8007019e appears
- WSL alone cannot resolve names while a VPN is connected
- Hyper-V is missing from Windows Features or cannot be enabled
- WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine
- Windows Sandbox is missing or cannot start