Fix printer error 0X00000869 — destination already exists

You're trying to add a network printer or a shared printer from another machine, and Windows throws up 0X00000869 with the message "The printer destination already exists." This usually pops up when you're adding a printer that was previously installed on the system, but the old entry is still hanging around in the print spooler. I've seen it most often in small offices where someone's Windows 10 or 11 machine had a network printer that got disconnected, and then they try to re-add it with the same name. The spooler remembers the old destination, and it refuses to create a duplicate.

The root cause is simple: the print spooler has a cached entry for that printer name. When you try to add a new printer with the exact same name—whether it's a TCP/IP port or a shared printer path like \\server\printer—the spooler says "already got that one." It's not smart enough to check if the old entry is dead or just stale. So it blocks the new one.

Fix: Clear the stale printer entry from the spooler

You don't need to reinstall drivers or reboot the server. Just nuke the old entry. Here's how.

Stop the print spooler service. Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or PowerShell (Admin)). Run:
```
net stop spooler
```
This kills the spooler service. Don't worry, it'll restart in a second.
Clear the printers folder. The spooler keeps printer data in C:\Windows\System32\spool\PRINTERS. Delete everything inside that folder. Don't delete the folder itself, just the files in it.
```
del /Q /F C:\Windows\System32\spool\PRINTERS\*.*
```
I've had clients who skipped this step and the error came back. Those leftover .SHD and .SPL files are the old printer references.
Remove the printer port manually (if needed). Sometimes the port name is the culprit. Open Devices and Printers, right-click any printer, choose Printer Properties, then go to the Ports tab. If you see a port with the same name as the one you're trying to add (e.g., 192.168.1.100 or \\server\printer), uncheck it and delete it if the option is available. If not, we'll clean it via the registry.
Registry cleanup (only if step 3 didn't work). Open Regedit and navigate to:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports
```
Look for the stuck printer name. Right-click and delete it. I know editing the registry sounds scary, but this is the fastest way to kill a stubborn port. Back it up first if you're nervous—File > Export.
Restart the spooler. Back in the Command Prompt:
```
net start spooler
```
Add the printer again. Go to Settings > Bluetooth & devices > Printers & scanners > Add device. Windows should now let you add it without the error.

Still failing? Check these

Printer driver leftovers. If the printer was installed before, old driver packages might block a new one. Run printmanagement.msc (type it in Run), go to Custom Filters > All Drivers, and remove any driver that matches the old printer model. Reboot after.
Group Policy restrictions. In a domain environment, a policy might be pushing the old printer. Run gpresult /h gp.html and look for "PushPrinterConnections" or "Deployed Printers". If it's there, talk to your admin.
DNS or hostname mismatch. If you're using a hostname instead of IP, make sure the DNS record points to the right machine. I had a client last month whose print server IP changed, but the old one was still in DNS cache—same error appeared.

That's it. This fix works for Windows 10, Windows 11, and Server 2016/2019/2022. The whole thing takes about two minutes once you know where to look. If you're still stuck after this, the spooler might be corrupted—then you're looking at a sc stop spooler + sc config spooler start= disabled and rebuilding it from scratch, but that's a rare case.