Fix 0x00000703 Printer Driver Already Installed Error

When Windows claims a printer driver is already installed but you can't see or use it, the driver store is stuck. Here's how to clear it out and force a clean install.

Quick answer

For advanced users: stop the spooler, delete the driver package from the driver store with pnputil /delete-driver oemXX.inf /uninstall /force, then reinstall from scratch. That clears the stuck flag that produces 0x00000703.

What's actually happening here

This error is Windows being stubborn about its driver store. When you install a printer driver, Windows doesn't just load it into memory—it copies the whole package into C:\Windows\System32\DriverStore\FileRepository and registers a reference in the spooler's database. The problem is that this registration can get out of sync. Maybe a previous uninstall didn't finish, or you ran a manufacturer's installer that half-installed and then crashed. Either way, the spooler thinks the driver exists, but the actual files or the registry entries are missing or corrupt. So when you try to add the printer again, you get 0x00000703—ERROR_PRINTER_DRIVER_ALREADY_INSTALLED—instead of a clean install.

The reason this is so annoying is that simply uninstalling from Devices and Printers won't touch the driver store. You're clearing the visible part, but the underlying package is still there, still registered, still causing the conflict. You have to go deeper.

Before you start

You'll need administrator rights. If you're on a company laptop with locked-down admin, this won't work—you'll need IT to run these commands. Also, grab the driver installer from the manufacturer's site beforehand. You're going to remove everything, so you need a clean source to reinstall from.

Fix steps

Identify the stuck driver. Open an elevated command prompt (right-click Command Prompt, Run as administrator). Run:
```
pnputil /enum-drivers
```
Look for the printer driver you're having trouble with. The Published Name will be something like oem42.inf. Note it down.
Stop the print spooler. Run:
```
net stop spooler
```
The spooler has to be off because it holds locks on driver files. Trying to delete while it's running will either fail or leave you with a half-deleted mess.
Delete the driver package using pnputil. Replace oem42.inf with the name you found:
```
pnputil /delete-driver oem42.inf /uninstall /force
```
The /uninstall flag removes the driver package from the store, and /force ignores any pending installations. If you get an error here, skip to the alternative fixes below.
Clean up leftover registry entries. Open regedit and navigate to:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3
```
Find the key matching your printer model and delete it. Be careful—only delete the one for the printer causing the issue. If you're not sure, this step can wait; sometimes pnputil clears it all.
Restart the spooler.
```
net start spooler
```
Reinstall the driver fresh. Run the manufacturer's installer, or use Add Printer in Windows Settings. This time it should install cleanly because the old driver's ghost is gone.

Alternative fixes if the main one fails

Sometimes pnputil refuses because the driver is marked as “in use” or the package is protected. Here's the next level:

Force a spooler reset via PowerShell

Open PowerShell as admin and run:

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

This goes through the WMI printer driver provider, which often catches stragglers that pnputil misses.

Manually delete driver files

If the registry key is gone but the error persists, the driver files might still be sitting in C:\Windows\System32\spool\drivers\x64\3. Delete the files matching your printer. This is a last resort—if you delete the wrong ones, you can break other printers, so only do it if you know exactly what you're removing.

Why the registry cleanup matters

What's actually happening here is that the spooler keeps a list of installed drivers in the registry. When you run the installer again, it checks this list and says “already there.” Even if the files are gone, that registry entry alone is enough to trigger 0x00000703. So if you skip step 4, you might reinstall the driver and watch it fail again. The registry entry is the root cause in most stubborn cases.

Prevention tip

Always uninstall printer drivers using the manufacturer's uninstaller, not just Remove Device. The official uninstaller knows to clean the driver store. Also, avoid installing both the Windows Update version and the manufacturer's version of the same driver—that's a common trigger for this exact error on Windows 10 and 11.