Fix it now
0x000006ba is Win32 1722, RPC_S_SERVER_UNAVAILABLE, “The RPC server is unavailable”. While printing from Office that server is nearly always the local print spooler, which has stopped or is crashing as fast as Windows restarts it. Office reports no printers because it asked the spooler for the list and got nothing back.
sc query spooler
net stop spooler
del /q /f %SystemRoot%\System32\spool\PRINTERS\*
net start spooler
- Read the
sc query spooleroutput first. STOPPED with no crash history means somebody or something stopped it, and starting it is the whole fix. - If it starts and dies again, that is a driver taking the service down with it. Open Event Viewer, Applications and Services Logs, Microsoft, Windows, PrintService, and note the driver named around the failures.
- List what the machine can see:
Get-Printerin PowerShell. An empty result with the service running means the queues themselves are gone. - Remove the suspect driver from Print server properties on the Drivers tab, with the spooler running, rather than only deleting the printer.
- Install the current driver from the manufacturer’s own download and add the printer again.
- Set the spooler’s Startup type to Automatic in
services.mscand reboot to confirm it comes up by itself.
On a print server, tell people before you empty the spool folder. Everything queued is lost, including other users’ jobs, and there is no way to get them back.
If the spooler stays up and printing works, you are done. If it keeps falling over, the next section explains what is taking it down.
Why it happens
The print spooler is one service that every application on the machine depends on. Office asks it for the printer list at startup and again when a document is printed. If the spooler is not running there is no list, so Office reports that no printers are installed even though the queues are configured and the hardware is fine. That is 0x00000bc4, Win32 3012, ERROR_PRINTER_NOT_FOUND, “No printers were found” – a symptom of the service being down rather than a fault of its own.
The spooler loads printer driver code inside itself. A driver that misbehaves can take the whole service down, and because Windows restarts the service automatically the result is a crash loop rather than a clean stop. From an application’s point of view that produces a scatter of unrelated-looking failures: an invalid handle when the connection it was using disappears, a file not found when a component the queue needs is no longer where it was, invalid data or an invalid parameter when a call lands mid-restart. Chasing those codes one at a time leads nowhere. Stabilising the service resolves all of them at once.
On a remote queue the same 0x000006ba means something different. There the RPC server that did not answer is the spooler on the print server, or the path to it. Test by opening the server by name in Explorer before you touch anything on the client.
The spooler is stopped or disabled
You have this one if sc query spooler reports it is not running, and starting it restores printing immediately.
- Start the service and set its Startup type to Automatic.
- Find out what stopped it. Hardening baselines disable the spooler deliberately on servers that do not print, which is a reasonable policy applied to the wrong machine here.
- Reboot and confirm it comes up by itself rather than assuming the change held.
Jobs in the spool folder wedge the service
You have this one if The service starts, runs for a moment and stops, and the spool folder holds files that never clear.
- Stop the spooler with
net stop spoolerbefore you touch anything, so the service is not writing while you work. - Delete the contents of
%SystemRoot%\System32\spool\PRINTERS, leaving the folder itself in place. - Start the spooler and resubmit one job to test.
Everything queued is lost, including jobs other users submitted. On a shared print server this is an announcement, not a quiet fix.
A faulty driver is crashing the service
You have this one if The System log shows the spooler terminating and restarting, and the print service log names the same driver each time.
- Remove the driver from Print server properties, on the Drivers tab, rather than only deleting the printer.
- Install the current driver from the manufacturer’s own download, not from a generic package or old installation media.
- Where the machine hosts several printers, set driver isolation for the suspect driver so a repeat failure cannot take every queue down with it.
- Prefer a class or universal driver from the manufacturer for a device with a history of unstable drivers.
Windows publishes two codes for drivers it already distrusts: 3013, the printer driver is known to be unreliable, and 3014, the printer driver is known to harm the system. If you meet either, believe them.
Orphaned queues and leftover entries
You have this one if Printers appear that cannot be removed, or the list is full of duplicates of queues that no longer exist.
- Stop the spooler before removing stubborn entries, then start it again so the changes are picked up cleanly.
- Remove the driver as well as the queue. A queue removed while its driver stays behind is a common source of repeat failures.
- Rebuild any shared queue connection from scratch rather than repairing it.
The print server is unreachable
You have this one if Local printers work and only queues from one server fail, and opening that server by name in Explorer also fails.
- Confirm the server name resolves and the machine is reachable.
- Check the spooler on the server itself, with the same checks you would run locally.
- If the server is fine and one client is not, remove and re-add the connection on that client.
Full reference
The six codes, and what each is really telling you
| Code | Published meaning | Why you are seeing it |
|---|---|---|
0x000006ba |
Win32 1722, RPC_S_SERVER_UNAVAILABLE: the RPC server is unavailable | Locally, the spooler is not answering. Remotely, the server’s spooler is not |
0x00000bc4 |
Win32 3012, ERROR_PRINTER_NOT_FOUND: no printers were found | The spooler returned an empty list, usually because it is down |
0x00000006 |
Win32 6, ERROR_INVALID_HANDLE: the handle is invalid | A connection that vanished when the service restarted underneath it |
0x00000002 |
Win32 2, ERROR_FILE_NOT_FOUND: the system cannot find the file specified | A component the print path expected is not where it was |
0x0000000d |
Win32 13, ERROR_INVALID_DATA: the data is invalid | Commonly a call landing while the service is mid-restart |
0x00000057 |
Win32 87, ERROR_INVALID_PARAMETER: the parameter is incorrect | A print call made with a value the spooler would not accept |
Four of those six are generic Windows errors that mean nothing specific about printing. That is the point: they are what a healthy application gets back when the service under it is unstable. Do not troubleshoot them individually.
Reading the pattern before you change anything
| What you see | What it means |
|---|---|
| No printers listed anywhere, including in Settings | The spooler is not running |
| The service restarts repeatedly in the System log | A driver is crashing it |
| Failures started after a driver install | That driver, straightforwardly |
| Only queues from one server fail | The remote spooler or the path to it |
| Jobs pile up and nothing prints | The spool folder or the queue, not the driver |
| It works after a restart and fails again by lunchtime | A driver, and a restart is a diagnostic rather than a fix |
Driver isolation
Driver isolation runs a print driver in its own process rather than inside the spooler. A driver that faults then takes down its own process and the queue that uses it, instead of taking down every queue on the machine. It is set per driver in Print Management, and it costs a small amount of memory per isolated driver.
- On a machine with one printer it rarely matters, because the driver and the spooler fail together anyway.
- On a print server it is worth setting for any driver you do not fully trust, and for every third-party driver on a busy server.
- It does not fix a bad driver. It contains one, which buys you the time to replace it during a change window rather than at nine in the morning.
When the spooler is stable and printing still fails
- Confirm the queue exists and points at a live port with
Get-Printer. - Print a Windows test page from the printer’s properties. That bypasses the application entirely.
- Check the device itself is reachable at the address the port names.
- On a shared queue, check the server’s spooler and its own event log rather than the client’s.
- Watch the System log for a few hours after the fix and confirm the service is not restarting quietly, which is what a partly-fixed driver problem looks like.
Deleting spool files discards every queued job, and editing the printer keys in the registry by hand can leave the spooler unable to enumerate any printer at all. Export the branch before changing it, and stop the spooler before deleting anything under the spool folder.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x000006ba |
Win32 1722, RPC_S_SERVER_UNAVAILABLE: the RPC server is unavailable. Locally, that is the print spooler | Microsoft Learn |
0x00000006 |
Win32 6, ERROR_INVALID_HANDLE: the handle is invalid, typically a connection that vanished when the service restarted | Microsoft Learn |
0x00000002 |
Win32 2, ERROR_FILE_NOT_FOUND: the system cannot find the file specified | Microsoft Learn |
0x00000bc4 |
Win32 3012, ERROR_PRINTER_NOT_FOUND: no printers were found, because the spooler returned nothing | Microsoft Learn |
0x0000000d |
Win32 13, ERROR_INVALID_DATA: the data is invalid, commonly a call landing while the service is mid-restart | Microsoft Learn |
0x00000057 |
Win32 87, ERROR_INVALID_PARAMETER: the parameter is incorrect | Microsoft Learn |
Confirm the fix worked
sc query spoolerreports RUNNING, and reports it again after a reboot.Get-Printerlists the queues you expect, with the drivers you expect.- A Windows test page prints, and then a document from an Office application prints.
- The System log shows no spooler restarts over the following few hours of normal use.
- If you removed a driver, confirm it is gone from the Drivers tab of Print server properties and has not been reinstalled by a policy.
Questions people ask about this
Does any of this cost money to fix?
No. Every step uses tools already in Windows, and the drivers involved are free downloads from the printer manufacturer. There is no licence that makes a spooler crash go away.
Why does restarting the spooler fix it for a while?
Because a restart clears the crashed state and any handle wedged behind it. If a bad driver is the cause, the next job that uses it crashes the service again, so a restart is a diagnostic rather than a fix.
Should I disable the spooler where nothing prints?
On servers that genuinely have no printing role, disabling it is a recognised hardening step and reduces exposure. Just make sure the policy is not reaching machines that do print, which is a common way to arrive at this error.
Is driver isolation worth setting up?
On a machine with several printers, or on a print server, yes. It runs the driver outside the spooler process so a crash takes the driver down instead of every queue on the machine.
Windows says the driver is unreliable. Should I install it anyway?
Windows publishes two separate codes here: 3013 for a driver known to be unreliable and 3014 for one known to harm the system. Both are the result of somebody having already had the failure you are about to have. Find a current driver from the manufacturer instead.
