Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x0000070A

Error 0x0000070A: printer already exists or the driver is still in use

10 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

Microsoft publishes 0x0000070A as ERROR_PRINTER_ALREADY_EXISTS, the printer already exists. That is usually true even when nothing appears in your printer list, because a queue has more parts than the icon: a configuration record, a port, a driver package staged in the driver store, and possibly jobs still in the spool folder. The companion codes tell you which part is still holding on.

Run these in an elevated session, in order, stopping when the name comes free

Remove-Printer -Name "QueueName"
net stop spooler
net start spooler
rundll32 printui.dll,PrintUIEntry /s /t2
pnputil /enum-drivers
  1. If jobs are holding the queue open, stop the spooler, delete everything inside C:\Windows\System32\spool\PRINTERS – the contents, not the folder – then start it again.
  2. The rundll32 line opens Print Server Properties on the Drivers tab. Select the driver, choose Remove, and pick the option that removes the driver package as well as the driver.
  3. If that is refused, find the package in the driver store from the pnputil /enum-drivers output, note the oem number against the manufacturer’s INF, then run pnputil /delete-driver oem12.inf /uninstall with your own number.
  4. Reinstall from a freshly downloaded package, or add the printer again and let Windows use the in-box driver.

If the removal reports 0x00000BC5 or 0x00000BC6, stop and read those. They are Windows telling you the driver is on its warned or blocked list, and reinstalling the same package will not end well.

If the queue is gone and the new one installs, you are done. If the name is still refused, the next section covers what else is holding it.

Why it happens

A print queue is a record in the spooler’s configuration, not a file you can delete. Adding a printer writes the queue, binds it to a port, and loads a driver from the driver store into the spooler process or into an isolation host process. Removing the icon removes the record. It does not unload the driver, remove the package from the store, or empty the spool folder.

That is why a reinstall so often fails immediately after an uninstall that appeared to work. The spooler still has the driver loaded, so it reports the driver as in use. Or a job that never printed is still queued against the old configuration. Or the package is still staged and the installer finds an identical one already present.

Two of the companions are simple and one is not. 0x00000BB9 is ERROR_PRINTER_DRIVER_IN_USE, the specified printer driver is currently in use. 0x00000BC1 is ERROR_PRINTER_HAS_JOBS_QUEUED, the requested operation is not allowed when there are jobs queued to the printer. Both are mechanical and both clear once you deal with what they name.

0x00000BC5 is the one to read carefully, because it is not a warning about your operation. It is ERROR_PRINTER_DRIVER_WARNED: the printer driver is known to be unreliable. Windows is telling you what it thinks of the package, not that the request went through with a condition attached. Its neighbour 0x00000BC6 is the same list one step further – known to harm the system – and that one is refused outright. If either appears while you are clearing up, the driver you are about to reinstall is the driver you should be replacing.

Jobs are still queued against the old printer

You have this one if 0x00000BC1, or documents in the queue that will not cancel and sit at Deleting.

  1. Try the clean route first: Get-PrintJob -PrinterName "QueueName", then Remove-PrintJob for each job.
  2. If jobs will not clear, stop the spooler with net stop spooler.
  3. Delete the contents of C:\Windows\System32\spool\PRINTERS, leaving the folder in place, then start the spooler and remove the queue.

The driver is still loaded in the spooler

You have this one if 0x00000BB9 when you try to remove the driver, even though no queue uses it any more.

  1. Restart the spooler so it releases loaded drivers: Restart-Service Spooler -Force.
  2. Retry the removal from Print Server Properties, Drivers tab.
  3. If the driver runs isolated, look for a leftover PrintIsolationHost process in Task Manager and restart the spooler again.
  4. As a last resort, remove the driver in Safe Mode, where third-party print drivers are not loaded.

The package is still staged in the driver store

You have this one if The Drivers tab is empty and the manufacturer’s installer still reports an existing installation, or the same driver reappears the moment the device is plugged in.

  1. List the staged packages with pnputil /enum-drivers and find the entry whose original name and provider match your printer.
  2. Delete it with pnputil /delete-driver oem12.inf /uninstall, substituting the number you found.
  3. Reboot, then install the driver you actually want.

Windows Update can restage a package for a device that is still connected. Unplug a USB printer before the clean reinstall.

Windows has warned or blocked the driver you keep reinstalling

You have this one if 0x00000BC5 or 0x00000BC6 appears during the removal or the reinstall.

  1. Stop reinstalling the same package. 0x00000BC5 is published as the driver being known to be unreliable and 0x00000BC6 as known to harm the system.
  2. Download a current package for the model from the manufacturer, or use the in-box class driver.
  3. Remove the old package from the driver store before installing the replacement, so it cannot be selected again.

The name is taken by a per-user connection, not a local queue

You have this one if The name is free for one user and taken for another, or it is a connection to a server queue rather than a local printer.

  1. Check what the current user has: Get-Printer | Select-Object Name,Type, and look for connection entries pointing at a server.
  2. Remove the connection rather than a local queue: Remove-Printer -Name "\\printsrv\queuename".
  3. If Group Policy Preferences or a logon script recreates it, change that first or it will return at the next logon.

Full reference

What the four codes say, exactly

Code Published meaning
0x0000070A ERROR_PRINTER_ALREADY_EXISTS: the printer already exists
0x00000BB9 ERROR_PRINTER_DRIVER_IN_USE: the specified printer driver is currently in use
0x00000BC5 ERROR_PRINTER_DRIVER_WARNED: the printer driver is known to be unreliable
0x00000BC1 ERROR_PRINTER_HAS_JOBS_QUEUED: the requested operation is not allowed when there are jobs queued to the printer

0x00000BC5 changes what you should do next, which is why it is worth separating from the other three. The other three are obstacles to an operation you are performing. That one is an opinion about the package you are performing it on, and the correct response is to find a different driver rather than to force the same one back into place.

The four places a printer lives

Part How it is removed What is left if you skip it
The queue Remove-Printer, or Settings The name stays taken
Queued jobs Stop the spooler and clear the PRINTERS folder 0x00000BC1 on every attempt
The loaded driver Restart the spooler, then remove it from the Drivers tab 0x00000BB9 on every attempt
The staged package pnputil /delete-driver <inf> /uninstall The installer finds an identical driver already present

Work down that table in order. Most failed reinstalls are somebody who did the first row and assumed the rest followed, and each row has a code that names it, so you rarely have to guess which one you are on.

Clearing the spool folder safely

  1. Warn anyone with a job waiting on a shared print server. They will have to send it again.
  2. Stop the service: net stop spooler.
  3. Delete the files inside C:\Windows\System32\spool\PRINTERS. Keep the folder.
  4. Start the service: net start spooler.
  5. Retry the removal, and only then the reinstall.

Deleting spool files with the spooler running can corrupt the queue for every user on a shared print server. Stop the service first. On a busy server, do it in a quiet period rather than in the middle of the afternoon.

When the name is still refused

  • Check for a per-user connection with the same name, which is invisible from another account.
  • Check whether a Group Policy Preference or a logon script recreates the queue at the next refresh.
  • Check whether a management tool is redeploying the printer as soon as it disappears.
  • Confirm the driver package really left the store, with pnputil /enum-drivers after the reboot rather than before it.
  • Where the spooler’s own configuration is the last suspect, treat direct edits to it as a last resort, take a backup first, and do it with the service stopped – it is the one step here that can leave printing unusable if you remove the wrong thing.

Every code this article covers

Code What it points at Source
0x0000070A ERROR_PRINTER_ALREADY_EXISTS: the printer already exists Microsoft Learn
0x00000BB9 ERROR_PRINTER_DRIVER_IN_USE: the specified printer driver is currently in use Microsoft Learn
0x00000BC5 ERROR_PRINTER_DRIVER_WARNED: the printer driver is known to be unreliable. Not a warning about your operation, but about the package Microsoft Learn
0x00000BC1 ERROR_PRINTER_HAS_JOBS_QUEUED: the requested operation is not allowed when there are jobs queued to the printer Microsoft Learn

Confirm the fix worked

  1. Run Get-Printer and confirm the old queue is gone and the new one is present.
  2. Run Get-PrinterDriver and confirm only the driver you intended is installed.
  3. Run pnputil /enum-drivers and confirm the old package is no longer staged.
  4. Print a test page and confirm the job leaves the queue rather than sitting at zero bytes.
  5. Reboot and confirm the queue and driver survive the restart without the old entry reappearing.

Questions people ask about this

Do I need to buy anything to clear this?

No. Every step uses tools built into Windows: the printing cmdlets, printui, pnputil and the Services console. There is nothing here a licence changes.

Why does deleting the printer icon not remove the driver?

Because they are separate objects. The queue is a configuration record; the driver is a package staged in the driver store and loaded into the spooler process. Removing one leaves the other where it was.

Is it safe to delete everything in the PRINTERS folder?

Yes, with the spooler stopped. Those files are spooled jobs and their descriptors and nothing else. You lose queued documents that have not printed, so warn users first on a shared print server.

I got 0x00000BC5 while removing the driver. What is that?

ERROR_PRINTER_DRIVER_WARNED: Windows publishes it as the printer driver being known to be unreliable. It is not a note about your removal. Take it as a reason to install a different driver rather than the same one again.

The name is still refused after all this. What is left?

A per-user connection with the same name, a queue recreated by policy at each refresh, or a package still staged in the driver store. Check them in that order, and re-check the driver store after a reboot rather than before one.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Network adapter Code 10: this device cannot start in Device Manager License Error VPN error 806: GRE protocol 47 blocked, and why PPTP should be retired License Error Error 0x80072746: endpoint security resets SMB, print and RDP connections License Error Error 0x80092012: TLS inspection breaks certificate checks on the client
โ† Back to Knowledge Base