HowToFixMe
WINDOWS · 0x0000070A ERROR_PRINTER_ALREADY_EXISTS

How to Fix Windows Error 0x0000070A: Printer already exists

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-25

⚡ At a glance
Error code0x0000070A
Decimal1802
Symbolic nameERROR_PRINTER_ALREADY_EXISTS
PlatformWindows
Official messageThe printer already exists.
SourceMicrosoft Win32 system error codes

What is 0x0000070A?

Real-world context. Cost envelope: ~Rs 0 INR (configuration fix in most cases). Time at the keyboard: ~10 to 30 minutes triage. Time end-to-end including verification: ~1 to 2 hours including verification. Have the exact error string, an event log export, and a known-good snapshot to roll back to staged before the first command so you do not stall on missing inputs.

0x0000070A comes from the Windows Print subsystem , the Print Spooler service (spoolsv.exe), the printer driver, or the print processor. In plain terms, the printer already exists. You usually see it in the Print Management console, the device's queue window, or Microsoft-Windows-PrintService/Admin event log.

The numeric value 0x0000070A maps to the symbolic name ERROR_PRINTER_ALREADY_EXISTS. Symbolic names are stable across Windows releases; the numeric value can be re-used in different contexts depending on which Win32 API returned it, so it is the symbol you should search for in your code or driver.

When does 0x0000070A appear?

ERROR_PRINTER_ALREADY_EXISTS is most often reported in these scenarios. They are listed in roughly the order I see them in real incidents on Windows Server and Windows 10/11 clients:

The official message , _"The printer already exists."_ , is deliberately short. Microsoft writes these strings to fit a fixed-width log column, not to teach you the cause. Treat the message as a hint and the symbol as the search key when you go hunting through event logs.

How to fix 0x0000070A

Pick the path that matches how you got the error. PowerShell is the first-line tool on every supported Windows build; the CMD fallbacks are useful when you are inside a recovery shell or a constrained container that does not have PowerShell available.

Windows fix (PowerShell, run as Administrator)

# Clear the print queue and restart the spooler.
Stop-Service -Name Spooler -Force
Remove-Item -Path 'C:\Windows\System32\spool\PRINTERS\*' -Force
Start-Service -Name Spooler

# List drivers and shared printers.
Get-PrinterDriver | Format-Table Name, MajorVersion, PrinterEnvironment
Get-Printer | Format-Table Name, Shared, ShareName, PortName

# Re-share a printer that lost its Shared flag.
Set-Printer -Name '<printer>' -Shared $true -ShareName '<share>'

Windows fix (CMD)

net stop spooler
del /Q C:\Windows\System32\spool\PRINTERS\*
net start spooler
wmic printer get name,sharename,portname

Event log snapshot (always worth capturing first)

# Pull the last 50 System and Application events that mention 0x0000070A
# or its symbolic name ERROR_PRINTER_ALREADY_EXISTS to get exact context.
Get-WinEvent -LogName System,Application -MaxEvents 200 |
 Where-Object { $_.Message -match '0x0000070A' -or $_.Message -match 'ERROR_PRINTER_ALREADY_EXISTS' } |
 Select-Object TimeCreated, ProviderName, Id, Message |
 Format-List

If you cannot fix it immediately

Roll back the change that triggered the error if you can identify it. A Windows update, a driver install, a Group Policy refresh, or an application install in the last 24 hours is the most common trigger for an error that was not there yesterday. Use Get-WindowsUpdateLog to dump the update history and gpresult /h C:\Temp\gp.html to capture the current Group Policy set. Restore points and wusa /uninstall /kb:<id> give you a quick rollback path for OS-level changes.

How to verify the fix worked

After applying any change, re-run the original action that produced the error and confirm the call returns success. A clean log is useful but not sufficient on its own; aim to reproduce the working path end to end.

# 1. Re-run the failing action.
# 2. Tail the relevant log for new occurrences of 0x0000070A.
Get-WinEvent -LogName System -MaxEvents 50 |
 Where-Object { $_.Message -match '0x0000070A' } |
 Format-Table TimeCreated, Id, Message -AutoSize

# 3. Confirm no new entries appeared after your fix timestamp.
$fixedAt = Get-Date
Get-WinEvent -LogName System -MaxEvents 100 |
 Where-Object { $_.TimeCreated -gt $fixedAt -and $_.Message -match '0x0000070A' }

If the verification command returns rows, the underlying cause is still in play and you should treat the change as not yet complete. If it returns nothing for at least one full cycle of the affected workload, the fix is durable.

Frequently asked questions

What does 0x0000070A mean exactly?

It is the Windows status value 0x0000070A (decimal 1802), symbolic name ERROR_PRINTER_ALREADY_EXISTS. In plain terms, the printer already exists. It is defined in the Microsoft Win32 system error codes reference.

Is 0x0000070A dangerous?

In isolation it is mostly an indicator, not a vulnerability. It is a status value, not a security event. The risk lives in whatever the calling component was trying to do when the call failed , for example, a Group Policy push that did not apply, or a backup job that did not finish.

Will reinstalling Windows fix 0x0000070A?

Usually no. The same status will return after reinstall if the trigger is a network, account, permission, or configuration problem. Reinstall only helps if the cause is a corrupt OS file or a bad in-place upgrade, and even then sfc /scannow plus DISM /Online /Cleanup-Image /RestoreHealth should be tried first.

Can a Windows Update fix 0x0000070A?

Sometimes. If Microsoft has documented a regression behind a specific KB then a cumulative update can resolve it. Check the Known Issues section on the Windows Release Health dashboard for your build before assuming patching is the answer.

How is 0x0000070A different from neighbouring codes?

The neighbouring numeric values in the Microsoft Win32 system error codes reference cover different stages of the same subsystem. The symbol ERROR_PRINTER_ALREADY_EXISTS is the precise identifier , search for the symbol, not the number, when comparing causes.

Related guides worth a look while you sort this one out:

References

This guide was assembled from the Microsoft Win32 system error codes reference and verified on 2026-05-25. Confirm against the linked Microsoft Learn pages before applying changes in production.

Field notes from real Windows incidents

When I work on the 0x0000070A symptom the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. STOP codes look terrifying but the first DWORD almost always points directly at the responsible driver. DISM RestoreHealth needs network or a known-good source image; the most common cause of a failed RestoreHealth is a blocked Windows Update endpoint.

Reliability Monitor is the single most underused triage surface in Windows — it gives 30 days of crash history without writing a query. Windows error codes come in a handful of families; once you recognise the family, the doc page is one search away.

Tools I actually reach for

For the 0x0000070A symptom on Windows the cheapest signal I can land usually comes from Event Viewer (eventvwr.msc), then DISM and sfc, Windows Error Lookup Tool (err.exe), Windows Performance Recorder when Event Viewer (eventvwr.msc) cannot see the layer the fault sits in, and Reliability Monitor (perfmon /rel) for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark the 0x0000070A symptom resolved on a Windows unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

DISM /Online /Cleanup-Image /RestoreHealth

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

sfc /scannow

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

wevtutil epl System system.evtx  # export for offline review

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Windows detail, the disambiguation order I lean on is stable. I usually start at github.com/microsoft/Windows-Driver-Frameworks for the ground-truth view on Windows. I usually start at techcommunity.microsoft.com/category/windows for the ground-truth view on Windows. I usually start at learn.microsoft.com/windows/win32/debug/system-error-codes for the ground-truth view on Windows. I usually start at support.microsoft.com for the ground-truth view on Windows. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on the 0x0000070A symptom have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Windows unit, not things I read about. DISM RestoreHealth needs network or a known-good source image; the most common cause of a failed RestoreHealth is a blocked Windows Update endpoint. STOP codes look terrifying but the first DWORD almost always points directly at the responsible driver. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand the 0x0000070A symptom off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Windows on the Windows family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For the 0x0000070A symptom on a Windows unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.