Print Server Queue Service Unavailable Error – Fix It Fast

When the Print Queue Goes Dead

Last month, a client called me because their entire office couldn't print. The error on every workstation said "Print Server Queue Service Unavailable." The server was a Windows Server 2019 box running a shared HP LaserJet. The queue just stopped. No warning. No update. Just dead.

I've seen this dozens of times. It's almost never a hardware failure. It's almost always the Print Spooler service dying, a driver going bad, or permissions getting scrambled. Here's how I fix it, starting with the fastest thing you can try. You can stop at any step once it works.

Fix #1: The 30-Second Checkbox Restart

Before you do anything else, check if the Print Spooler is even running. It's the engine behind the queue. If it's stopped, nothing prints.

1. On the print server (or your machine if it's a local printer), hit Windows + R, type services.msc, and press Enter.
2. Scroll down to Print Spooler. Look at the Status column. If it says "Stopped" or it's blank, right-click it and select Start.
3. Right-click again, pick Restart. This clears any temporary glitch.
4. Check if the queue is alive now. Try printing a test page.

This works maybe 30% of the time. It's the first thing I do when I walk into a client's office. If the service starts but then stops again, or if the queue still shows unavailable, move to Fix #2.

Fix #2: The 5-Minute Spooler Reset

If the service is running but the queue is stuck, the spooler folder probably has junk in it. Corrupted print jobs can freeze the whole queue. I've seen a single stuck job bring down a server for 50 users.

Step 1: Stop the Spooler and Clear the Queue

1. Open services.msc again (or use an admin command prompt).
2. Right-click Print Spooler and select Stop. Leave the window open.
3. Open File Explorer and go to C:\Windows\System32\spool\PRINTERS. Delete everything inside that folder. Don't worry, these are just temp job files.
4. Go back to Services and start the Print Spooler again.

That's the basic cleanout. But sometimes the spooler folder itself is corrupt. If the above doesn't work, do this command instead (run as Admin):

net stop spooler
del /Q /F /S C:\Windows\System32\spool\PRINTERS\*
net start spooler

This forces a clean delete. I had a client last week whose queue had a 200MB PDF stuck from a year ago. That one line fixed it.

Step 2: Check if the Spooler Service Is Set to Auto-Start

In Services, double-click Print Spooler. Set Startup type to Automatic. Click Apply and OK. If it's set to Manual, it won't start after a reboot, and you'll get the error again.

If the spooler still crashes or won't start, move to Fix #3. That's the deep stuff.

Fix #3: The 15+ Minute Deep Dive – Permissions and Drivers

If the spooler starts but stops immediately, or if the queue shows unavailable after a restart, the problem is usually permissions or a bad printer driver. Don't waste time guessing – check these in order.

Step 1: Fix Spooler Permissions (Common on Server 2016/2019)

The Print Spooler service runs under the Local System account. If that account lost permissions to the spool folder, it can't write job files. I've seen this happen after a security update or a domain policy push.

1. Go to C:\Windows\System32\spool\PRINTERS.
2. Right-click the PRINTERS folder and select Properties.
3. Go to Security tab. Click Advanced.
4. Make sure SYSTEM has Full control. Also check Administrators and Print Operators have Modify.
5. If SYSTEM is missing, add it. Click Add, type SYSTEM, check Full control.
6. Apply and restart the spooler.

I had a client whose IT guy locked down folder permissions. The spooler couldn't write files, so the queue showed unavailable. Fixing permissions took 2 minutes after an hour of head-scratching.

Step 2: Remove Bad Printer Drivers

A corrupt driver can kill the spooler on start. Windows 10 and 11 are especially picky with third-party drivers. If you added a printer recently, that driver might be the culprit.

1. Open Devices and Printers on the server.
2. Right-click any printer using the suspect driver and select Printer properties (not the regular properties). Go to Advanced tab.
3. Note the driver name. Then close out.
4. Open an admin PowerShell and run:

Get-PrinterDriver -Name "*" | Where-Object {$_.Name -like "*HP*"} | Remove-PrinterDriver

Replace "HP" with the driver brand you want to remove. This nukes all drivers of that brand. After that, reinstall fresh drivers from the manufacturer's site – not Windows Update. I've seen Windows Update deliver broken drivers that cause exactly this error.

If you don't know which driver is bad, remove all third-party drivers and add them back one at a time:

Get-PrinterDriver | Where-Object {$_.Name -notlike "Microsoft*"} | Remove-PrinterDriver

Then restart the spooler and test with a basic Microsoft Print to PDF first. If that works, add back your real printer driver.

Step 3: Check for RPC Issues (If the Server Is Remote)

If the print server is on a different machine and the queue shows unavailable on clients, the RPC service might be blocked. This happens after Windows updates that tighten firewall rules.

On each client, open services.msc and check that Remote Procedure Call (RPC) is running. Also check RPC Endpoint Mapper. Both should be set to Automatic and running.

If they're running, test connectivity from the client to the server using:

Test-NetConnection -ComputerName [server-name] -Port 445

If that fails, your firewall or network is blocking print sharing. Open port 445 between client and server. That's the standard SMB port for printer sharing.

Real-World Tips

Final Thought

Print queue errors are annoying but rarely mean hardware failure. Start with the checkbox restart. If that doesn't stick, clear the spool folder. If it keeps coming back, fix permissions or kill a bad driver. Nine times out of ten, one of these three steps gets you printing again. And if it doesn't, you might have a deeper network issue – but that's a rare beast. I'll cover that another day.

Try these steps in order. You can stop once your queue shows Ready and a test page prints. No need to do all three if the first one works.