Printer troubleshooting technician providing live chat help

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

Technician avatar Technician
Hey! We’ll track down those WSD printer ghost entries and convert your printers to a clean Standard TCP/IP setup so they stop duplicating and going offline.
A couple of quick questions to aim the fix: In Settings → Bluetooth & devices → Printers & scanners (or Control Panel → Devices and Printers), do you see your printer listed more than once with similar names? When you open Printer Properties → Ports, does the active port show as WSD-xxxx instead of the printer’s IP address? And is this happening on Windows 10, Windows 11, or a mix of both?
Customer
Windows 11. In Devices and Printers I see the same HP printer 3–4 times. In the port list, the one that keeps going offline is on a WSD-xxxx port. Another entry uses a Standard TCP/IP port with the printer’s IP. The WSD printers keep showing up as new devices and confuse users — they pick the wrong one and it fails.
Technician avatar Technician
That’s exactly what we call WSD printer ghost entries.
Windows uses WS-Discovery (WSD) to automatically find printers on the network. When you install a printer via WSD, Windows creates a WSD port instead of a TCP/IP port. Sounds convenient, but in real life it often causes:
• Multiple ghost printers with similar names.
• Queues that randomly go offline or show “printer not responding”.
• Ports that don’t display the IP, making management a pain.

The stable approach is to remove the WSD printer ports, keep or create a single Standard TCP/IP port with the printer’s IP address, and force Windows to use that. We’ll:
1) Confirm which printer instance is the “real” TCP/IP one.
2) Capture the printer’s IP address if you don’t already have it.
3) Remove unused WSD queues and delete WSD ports.
4) Add or re-point to a Standard TCP/IP port and make that the only queue users see.
Customer
That makes sense. My problem is I don’t actually see the IP on the WSD entry, only on the TCP/IP one. How do I find the IP for the WSD printer and then switch everything from WSD to TCP/IP without breaking scanning or drivers?
Technician avatar Technician
Great question — WSD hides the IP, which is why WSD printers are so awkward to manage.
Step 1 — Confirm the printer’s IP and the “good” queue
1) On the printer itself, print a Network Configuration or Wireless Summary page from the front panel menu. Look for the IPv4 address (something like 192.168.1.50).
2) In Settings → Printers & scanners, select each printer entry → Manage → Printer properties → Ports tab.
  • Note which queue uses a Standard TCP/IP Port that matches the IP on the printer’s page.
  • Note which ones use WSD-xxxx port names and show no IP.
3) Print a test page from each queue:
  • If the TCP/IP queue always works and the WSD printer queue goes offline, we’ll keep the TCP/IP queue and remove the WSD printer ghost entries.

Scanning is usually handled separately (via the vendor software, SMB, or an IP-based scan profile), so changing from WSD to TCP/IP for printing normally doesn’t break scanning. We’ll still do it carefully.
Customer
The configuration page shows 192.168.0.42. One of the printers is on a Standard TCP/IP port with that IP and prints fine. The others are WSD and sometimes show “offline” even when the printer is on. I’d like to only use the TCP/IP one. What’s the clean way to get rid of the WSD ports and ghost entries?
Technician avatar Technician
Perfect — we already have the working IP queue, so this becomes a cleanup job.
Step 2 — Remove WSD printer ghost entries and delete WSD ports
1) In Settings → Printers & scanners (or Devices and Printers):
  • Right-click each WSD printer (the ones that use WSD ports) → Remove device.
2) For deeper cleanup, open Print Management (printmanagement.msc) → expand Print Servers → <your-computer> → Printers.
  • Delete any printer that uses a WSD port or keeps going offline.
3) Still in Print Management, go to Ports under your computer:
  • Look for port names starting with WSD-.
  • If a WSD port shows not in use, select it and click Delete port. This removes the underlying WSD printer ghost port so Windows can’t accidentally bind to it again.
4) Keep the single Standard TCP/IP Port that matches 192.168.0.42 and is working.

After this, you should have one real queue using TCP/IP. Next we make sure Windows doesn’t keep trying to auto-add a new WSD printer.
Customer
Okay, I’ve deleted the extra WSD printers and unused WSD ports. The remaining queue is the TCP/IP one and works. Is that enough, or do I need to change any settings so Windows doesn’t add WSD again automatically?
Technician avatar Technician
Good move. Now we’ll force TCP/IP so WSD isn’t used again by accident.
Step 3 — Double-check the Standard TCP/IP port and disable WSD-style auto-add
1) On the working queue, open Printer properties → Ports:
  • Confirm the checkbox is on Standard TCP/IP Port with the correct IP.
  • Click Configure Port and make sure the printer name/IP is set to 192.168.0.42 (or your value). If your printer is simple, consider turning off SNMP status if it causes false “offline” states.
2) Avoid using the automatic “Add device” WSD option going forward. When you add printers, always choose:
  • “The printer that I want isn’t listed” → Add a printer using a TCP/IP address or hostname in Windows.
3) On some printers, you can log into the web interface and disable WSD/WS-Discovery entirely. That stops WSD printer endpoints from being advertised, so Windows can’t create new WSD queues even if a user clicks the wrong thing.

From now on, any new queue you add should use Standard TCP/IP only. That’s the stable, admin-friendly way to avoid WSD ghost printers.
Customer
What about in a small domain environment? We have a bunch of Windows 10 and 11 PCs, and a few somehow added their own WSD printers instead of the print server queue. Can I force everything to use TCP/IP and get rid of WSD printer ports with a script?
Technician avatar Technician
Yes — in a domain it’s common to find random local WSD printers side by side with your official print server queues.
Step 4 — Find and remove WSD printers with PowerShell (admin task)
On a test PC, open an elevated PowerShell and run:
Get-Printer | Where-Object PortName -like "WSD*" | Format-Table Name,PortName
• This lists all printers using a WSD port.

To remove those ghost entries (after verifying you have working TCP/IP queues from the server), you can run:
Get-Printer | Where-Object PortName -like "WSD*" | Remove-Printer

Then clean the ports:
Get-PrinterPort | Where-Object Name -like "WSD*" | Remove-PrinterPort

Once you’re happy with the result on a test machine, you can deploy similar logic through a logon script, Intune, or remote PowerShell to remove WSD printer ghost entries across multiple PCs, leaving only the TCP/IP / print server queues users should be using.
Customer
After we remove the WSD printers and ports, some users still see the printer auto-appearing again as a new WSD device when they click “Add a printer”. Any way to stop that behavior so they’re forced to use the TCP/IP or server-deployed queue?
Technician avatar Technician
That’s where policy and printer settings come in.
Step 5 — Reduce or disable WSD auto-discovery and push TCP/IP queues centrally
1) Deploy printers via Group Policy Preferences, Intune, or Universal Print so users automatically get the correct TCP/IP or server queue and don’t need to click “Add device” at all.
2) Use Group Policy or local security policy to restrict users from installing new printer drivers or adding local printers. That nudges everyone toward the managed TCP/IP queues only.
3) Where possible, log into the printer’s web UI and disable WSD / Web Services / WS-Discovery. Without those advertisements, Windows won’t see the device as a “WSD printer” and can’t create new WSD entries.
4) On complex networks (VPN, multiple subnets), limiting multicast/WS-Discovery traffic also helps reduce WSD ghost printers appearing from other segments.

Combined, these steps make Standard TCP/IP the only path users see, and WSD quietly disappears from your environment.
Customer
After cleanup, each PC now shows just one printer queue and it’s on a Standard TCP/IP port with the correct IP. Test pages are good. Anything else I should check so the WSD ghost entries don’t come back after reboots or updates?
Technician avatar Technician
Nice work — you’re already in the “stable” camp now.
Final checks for long-term WSD → TCP/IP success:
• Give the printer a static IP or DHCP reservation so the Standard TCP/IP port always points at the right address.
• Make sure users only see and use the TCP/IP queue. Hide or remove any legacy queues that still reference WSD or old IPs.
• If the printer firmware allows, keep WSD disabled going forward so new WSD printer endpoints never appear.
• Periodically review Get-PrinterPort output on a sample of machines to confirm there are no “WSD-” ports creeping back in.

If you ever want help building a quick script or GPO to normalize all printers to Standard TCP/IP, just open the chat and we’ll tailor it to your exact environment.
Customer
Perfect. The WSD ghost entries are gone and we’re down to one TCP/IP queue per printer. Printing is way more reliable now. Thanks!
Technician avatar Technician
Summary: To fix WSD printer ghost entries, stop using WSD ports and force Standard TCP/IP instead. Remove extra WSD queues, delete unused WSD-xxxx ports, confirm the printer’s IP from its configuration page, and create or keep a single Standard TCP/IP port. In managed environments, disable WSD on the printer and deploy TCP/IP queues via GPO or Intune so users only see the stable printer. Want someone to walk you through this live? Open the chat.

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.

Common WSD printer problems and quick fixes
SymptomLikely causeQuick 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)

  1. Print the printer’s network configuration page and note the IPv4 address.
  2. In Printers & scanners or Devices and Printers, identify which queue uses a Standard TCP/IP Port and which use WSD-xxxx ports.
  3. Remove the WSD queues, then open Print Management → Ports and delete unused WSD ports.
  4. 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)

  1. On macOS, add the printer using its IP (IPP or HP Jetdirect/Socket) rather than discovery where possible.
  2. 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

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant