Adding a Printer and Windows Cannot Find It? Use the IP

You clicked Add device. Windows spun for a while. Your printer is not in the list. It is switched on, it is on the Wi-Fi, and it worked from your phone ten minutes ago.

Windows finds printers by broadcasting a question across your network and waiting for an answer. When that conversation fails, the printer is fine and the discovery is what broke.

There is a route that skips discovery entirely. It is the one to reach for. I have taken this by how your printer connects, because that is what changes the answer.

Start here, whatever kind of printer it is

Documented by Microsoft on its install a printer page, for Windows 11: "Select Start > Settings > Bluetooth & devices > Printers & scanners", then "select Add device".

On Windows 10 the route is "Select Start > Settings > Devices > Printers & scanners", then "select Add a printer or scanner".

Give it thirty seconds. If your printer appears, click it. Done.

If it does not, do not click Add device again. Repeating a search that already failed is the most common wasted minute in this whole job.

If it is plugged in with a USB cable

The easy case. It almost never needs this page.

Plug the cable straight into the PC rather than through a hub. Windows should install it without you doing anything.

Try a different USB port before anything else. A printer that appears on one port and not another is a port problem, not a printer one.

⚠️ If nothing happens at all when you plug it in, that is a USB fault rather than a printing one. The exact wording of any message matters.

If it is a wireless printer on your own network

Now the common case, and the one where discovery lets you down.

Microsoft states the requirement plainly: "For wireless printers, make sure the printer is on the same wireless network as the Windows device."

That catches more people than anything else. A router with a 2.4 GHz and a 5 GHz band, or a guest network, gives you two networks with similar names. The printer on one and the PC on the other will never see each other.

Check the printer's own screen for the network name it joined, and compare it with the one your PC is on.

Ours, and marked as ours: write down the printer's IP address while you are at its screen. It is usually under Network or Wireless settings, and you are about to need it.

When it is still not listed, skip discovery

This is the route worth learning, and it works when everything else has failed.

In the Add device flow, Microsoft's own wording is to look next to "The printer that I want isn't listed" and "select Add a new device manually".

Then choose Add a printer using a TCP/IP address or hostname, type the address you wrote down, and let the wizard finish.

This bypasses discovery completely. You are telling Windows exactly where the printer is instead of asking the network to find it.

Reported by an adviser on Microsoft's board in October 2025, and it matches what the flow does. Adding by IP is the reliable route. Discovery being flaky does not stop it. It works whenever the printer is reachable at all.

Test reachability first if you want certainty. Open Command Prompt and run `ping` followed by the printer's address. Replies mean the PC can reach it and the fault is discovery. Timeouts mean they are not talking at all.

If ping fails, it is the network and not Windows

Different problem, and no setting on your PC fixes it.

Client isolation on the router is the usual cause. Many routers can stop devices talking to each other, under names like AP Isolation, Client Isolation or Layer 2 Isolation.

Guest networks often have it on by default, so check which one you joined.

An adviser on that same thread pointed at exactly this. Log in to the router and disable any of those options.

Ours: phone can print to it, PC cannot, both on the same network? Isolation is the first thing to look at.

Power cycle the printer for thirty seconds and reboot the router before concluding anything. That pair fixes a surprising share of these and costs two minutes.

If it is shared from another PC

Another route hides behind the same link. It needs the other machine to be on.

Use The printer that I want isn't listed again. Then Select a shared printer by name, and type the path as `\\ComputerName\PrinterShareName`.

⚠️ The computer sharing it has to be awake. A printer shared from a laptop that sleeps vanishes and reappears all day. That is not a fault you can fix from your end.

The discovery services, when nothing is ever found

Worth knowing about, though it is further down the list than most pages put it.

An adviser on Microsoft's board named five services that network discovery depends on. Function Discovery Provider Host, Function Discovery Resource Publication, DNS Client, SSDP Discovery and UPnP Device Host.

Open services.msc and find each one. Check it is running, with a startup type of Automatic.

⚠️ That reply reads like a support template and I am labeling it as adviser guidance rather than as vendor documentation. Nobody on the thread confirmed it fixed them.

Ours: try adding by IP before you go into services. If the IP route works, discovery was the problem and you now have a working printer either way.

The case where an update was the cause

Printed because it is real and dated, and it may be yours. It ended in a rollback rather than a repair.

An owner reported in October 2025 that Windows 11 25H2 broke it. Printers installed on that network before could no longer be found. In their words: "Install program cannot find them."

They had already rebooted the router and the PC. They had worked through a set of commands too.

A day later they came back with the outcome: "Rolled back to 24H2. Everything nominal."

⚠️ A reader on the same thread blamed a specific protocol change in that release. That is a reader's claim, not a Microsoft statement. I am not going to repeat it as fact.

The end of it was mixed rather than clean. After reinstalling the older version, they reported getting the Canon connected while the Epson still showed as "Status Unavailable".

So there is no clean confirmed fix for that case. And rolling a whole feature update back is a heavy answer to a printer problem.

Ours: did this start the week your PC took a feature update? Add by IP first. It sidesteps the broken half without giving up the update.

When the printer is added and still will not print

Different article from here, and worth separating.

A printer that is installed but refuses to print starts from the test page. One step, and it names which end is at fault.

And one that reports itself offline has its own seven fixes. They start with a proper power cycle.

Status: worked through 23 August 2026, covering both versions. Microsoft documents each of the Settings routes, the Add device and Add a printer or scanner buttons, the printer that I want isn't listed link, Add a new device manually, and the requirement that a wireless printer be on the same network. The TCP/IP route, the discovery services and the router isolation advice are adviser answers from a dated Microsoft Q&A thread, and the update case ended in a rollback rather than a fix.

How do I add a printer that Windows cannot find?

Use The printer that I want isn't listed, then Add a printer using a TCP/IP address or hostname. Type the address shown on the printer's own screen. That skips discovery entirely and works whenever the PC can reach the printer.

Why can my phone see the printer but my PC cannot?

Usually because they are on different networks, or because the router is separating devices. Check the network name on the printer's screen against the one the PC is on. Then look for AP Isolation or Client Isolation in the router settings.

How do I find my printer's IP address?

On the printer's own screen, under Network or Wireless settings. Most will also print a network configuration page from their menu. Write the address down before you start the Add device flow.

Can a Windows update stop printers being found?

Owners report it. One in October 2025 lost printer discovery after moving to Windows 11 25H2. They ended up rolling back, with mixed results afterwards. Adding by IP address is the lighter answer if that is your situation.

The Short Version

  • Settings, Bluetooth and devices, Printers and scanners, Add device on Windows 11.
  • If it is not found, do not search again. Use The printer that I want isn't listed.
  • Add a printer using a TCP/IP address or hostname skips discovery altogether.
  • Get the IP off the printer's own screen before you start.
  • Microsoft requires a wireless printer to be on the same network as the PC. Two bands count as two networks.
  • Ping the printer to prove the PC can reach it. Replies mean discovery is the fault.
  • Client isolation on a router stops devices seeing each other and is often on for guest networks.
  • One owner lost discovery to a feature update. They rolled back rather than fixing it.

Where to Next

Go and read the IP address off the printer's screen. Then add it by TCP/IP. Three minutes, and it is the route that works when the easy one has failed.

If ping gets no reply, stop working on the PC. Look at the router instead. Isolation settings are the usual answer, and no printer setting reaches them.

If the printer installs and then refuses to print, the test page separates the two halves in one step.

And if adding by IP failed for you on a printer that pings fine, drop the make below. I have not seen that pairing explained anywhere.

Leave a Comment