WSD Printer Ghost Entries — Switch to TCP/IP Fix Guide
Joe B.
Reviewed for technical accuracy
Specialities: Windows 11/10, Printers, Networking, Group Policy, Print Servers
Fix WSD printer ghost entries — remove WSD ports and force Standard TCP/IP on Windows 10/11
Quick answer: the accepted fix
Accepted fix when you see WSD printer ghost entries or duplicate printers in Windows 10/11: remove any queues that use WSD-xxxx ports, delete unused WSD ports in Print Management, and keep or create a single Standard TCP/IP port using the printer’s static IP. Always add printers via “TCP/IP address or hostname” instead of WSD, and disable WSD/WS-Discovery on the device where possible so Windows can’t auto-create new WSD printers.
Why WSD creates ghost printer entries and why TCP/IP is more stable
Web Services for Devices (WSD) uses automatic discovery (WS-Discovery) to find printers on the local network. That’s handy for home users, but in real networks it often leads to several WSD printers for the same device, strange “offline” states, and ports that don’t show an IP address. Every time Windows rediscovers the device, it may build a new WSD queue, so you end up with ghost printers users accidentally select.
By contrast, a Standard TCP/IP port points directly at the printer’s IP address (often on raw port 9100 or IPP). When you assign the printer a static IP and always create a TCP/IP printer port, Windows treats it like a traditional network printer: predictable, easy to script, and much less likely to spawn duplicate entries after reboots, updates, or network changes.
How to verify you’ve removed WSD and forced Standard TCP/IP
After cleanup, open Print Management → Printers and confirm there is only one queue per physical printer. In that queue’s Printer properties → Ports tab, the selected port should be a Standard TCP/IP Port showing your printer’s IP address — not a WSD-xxxx name. Print a test page and a multi-page PDF; the queue should stay online with no random “offline” or “not responding” errors.
If you run Get-PrinterPort | Where-Object Name -like "WSD*" in PowerShell and it returns nothing, you’ve successfully removed the WSD printer ports from that machine and are fully on TCP/IP.
WSD printer ghost entries — quick troubleshooting tips
Most WSD issues are solved by deleting WSD ports and standardizing on TCP/IP printer ports.
Quick path: print the printer’s config page → identify its IP → keep or create a Standard TCP/IP port with that IP → remove all WSD printers and WSD-xxxx ports → add future printers using “TCP/IP address or hostname” only → optionally disable WSD/WS-Discovery on the printer. This sequence removes confusing WSD ghost printers and gives you one reliable queue per device.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.
Expert will respond in minutes
We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive consults. Membership can save you significant time and money each month.
FAQ
What are WSD printer ghost entries?
WSD printer ghost entries are extra printer queues Windows creates via Web Services for Devices (WSD) discovery. They typically use WSD-xxxx ports, don’t show the printer’s IP address, and often appear duplicate to an existing TCP/IP queue for the same device. Users frequently pick the wrong queue and see offline or not-responding errors.
How do I remove WSD and force a Standard TCP/IP printer port?
First, get the printer’s IP from its configuration page. Then remove all printers that use WSD-xxxx ports, delete unused WSD ports in Print Management, and create or keep a Standard TCP/IP port pointing at the printer’s IP address. Add printers via “Add a printer using a TCP/IP address or hostname” instead of using the default WSD-based discovery.
Is WSD worse than TCP/IP for printers?
WSD is fine for simple home setups, but in business or mixed networks it often leads to duplicate printers, offline queues, and hidden IPs. A Standard TCP/IP port tied to a static IP is easier to manage, script, and support. That’s why many admins remove WSD printer ports entirely and standardize on TCP/IP.
Can I disable WSD so new ghost printers don’t appear?
On many printers you can log into the web interface and disable WSD / Web Services / WS-Discovery. Combined with adding printers only via TCP/IP and restricting user ability to install local printers, this prevents new WSD printer ghost entries from appearing on Windows 10/11 PCs.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Multiple duplicate printers for one device | Windows created extra WSD printers via auto-discovery | Remove WSD queues and ports; keep one Standard TCP/IP printer |
| Printer shows offline even though it responds on the network | Queue bound to flaky WSD port or wrong protocol | Switch from WSD to a Standard TCP/IP port with the correct IP |
| Users select wrong printer from list | Mix of local WSD printers and server/TCP-IP printers | Remove local WSD printers, deploy TCP/IP queues centrally |
| Hard to find printer IP from Windows | Port is WSD so IP isn’t shown | Print config page, create TCP/IP port using that IP, delete WSD port |
Step-by-step (Windows 10/11 — WSD to TCP/IP)
- Print the printer’s network configuration page and note the IPv4 address.
- In Printers & scanners or Devices and Printers, identify which queue uses a Standard TCP/IP Port and which use WSD-xxxx ports.
- Remove the WSD queues, then open Print Management → Ports and delete unused WSD ports.
- Create or keep a single Standard TCP/IP port with the printer’s IP, set that queue as Default, and add future printers using “TCP/IP address or hostname” only.
Note for mixed environments (macOS + Windows)
- On macOS, add the printer using its IP (IPP or HP Jetdirect/Socket) rather than discovery where possible.
- On Windows, standardize on Standard TCP/IP ports for the same device. That keeps behavior consistent across both platforms and avoids WSD-only quirks on the Windows side.
Sources
- Microsoft — Install printer using TCP/IP instead of Secure WSD
- Xerox — Check printer port and create a Standard TCP/IP port
- HP driver guide — Switch WSD ports to TCP/IP for stable printing
Filed under: Printer won’t print
Related articles
- Why does my printer need Wi-Fi setup again? It was working yesterday.
- Why does my printer go offline randomly (even when it’s on)?
- Printer says “Offline” and won’t print — what should I check first?
- My printer “forgot” my Wi-Fi — the saved network is gone
- Printer Wi-Fi settings reset by itself — why did it forget my network?
- My printer keeps popping up “Set up Wi-Fi” again — why won’t it stay connected?
- My printer Wi-Fi setup keeps failing — what am I doing wrong?
- Printer Wi-Fi setup is confusing — why won’t it connect to my network?