9 reasons why Wireless scanning doesn’t work in Windows 10 (and how to fix it)

Start here if your scanner won’t show up or complete scans over Wi‑Fi — the most common cause is that the PC and scanner can’t see each other on the network. If Wireless scanning doesn’t work in Windows 10, it’s usually because of network settings, disabled Windows services, driver/firmware problems, firewall rules, or router features that block device-to-device communication. In this article you’ll learn the nine most frequent causes and step‑by‑step fixes so you can restore wireless scanning reliably.

---

Key Takeaway

Most wireless scanning problems are network visibility issues — set the network profile to Private, enable Network Discovery and the related Windows services, ensure the scanner and PC are on the same SSID, and update drivers/firmware; if a firewall or router feature is blocking traffic, create the required exceptions or disable client isolation.

---

Quick Fix Guide

Reason for the Problem	Quick Solution
Scanner is powered off or not connected to Wi‑Fi	Power on the scanner and connect it to the correct Wi‑Fi network (SSID).
PC and scanner on different networks or bands	Put both devices on the same SSID and, if possible, on the same 2.4/5GHz band.
Network profile set to Public / Network Discovery off	Change network to Private and enable Network Discovery and File and Printer Sharing.
Required Windows services stopped (WSD, WIA, Function Discovery)	Start and set Function Discovery and WIA services to Automatic.
Firewall or antivirus blocking scanner ports	Allow scanner app/ports through Windows Defender Firewall or disable third‑party firewall temporarily.
Missing or incorrect scanner drivers	Install the manufacturer’s scanner driver or use Device Manager > Update driver.
Outdated scanner firmware	Update firmware from the manufacturer’s website or the scanner’s web UI.
Router AP/client isolation or Guest network blocking	Disable client/AP isolation or move device off guest network in router settings.
IP address conflict or DHCP issues	Assign a DHCP reservation or set a correct static IP on the scanner and verify by pinging it.

---

Detailed Fixes for “Wireless scanning doesn’t work in Windows 10”

1) Scanner is powered off or not connected to Wi‑Fi

Why this causes the problem

• If the scanner isn’t powered on or not joined to the wireless network, Windows cannot discover or communicate with it.

Step‑by‑step solution

1. On the scanner control panel, verify the display shows a Wi‑Fi/Network symbol. If not, turn the scanner on.
2. Use the scanner’s Wi‑Fi setup wizard (often under Network or Wireless Setup) to join the correct SSID and enter the Wi‑Fi password.
3. Print a network configuration page from the scanner (menu option often labeled Print Network Configuration or Network Status) and confirm it shows an IP address.
4. From your PC, open Command Prompt and run: ping to confirm connectivity.

Notes

• If the scanner has a USB-only mode, ensure it’s set to network mode for wireless scanning.

2) PC and scanner are on different networks or bands

Why this causes the problem

• Many routers create multiple SSIDs (guest, private, 2.4GHz vs 5GHz). Devices on different SSIDs or isolated guest networks can’t communicate.

Step‑by‑step solution

1. On Windows 10, check the connected SSID: Settings > Network & Internet > Wi‑Fi and note the network name.
2. On the scanner, confirm the SSID it’s connected to (from its network menu or printed network page).
3. If they differ, reconnect either the PC or the scanner to the same SSID.
4. If the router splits bands into distinct SSIDs (e.g., MyWiFi and MyWiFi_5G), try connecting both devices to the same band (preferably 2.4GHz for many older scanners).

Tips

• Some enterprise networks isolate Wi‑Fi clients; use a home network or contact IT.

3) Network profile set to Public and Network Discovery disabled

Why this causes the problem

• Windows treats Public networks as untrusted and disables discovery and sharing features, blocking scanner discovery.

Step‑by‑step solution

1. Open Settings > Network & Internet > Status.
2. Click Change connection properties and set Network profile to Private.
3. Open Control Panel > Network and Sharing Center > Change advanced sharing settings.
4. Under Private, turn on Turn on network discovery and Turn on file and printer sharing. Save changes.
5. Optionally restart Windows or run services.msc and restart Function Discovery Provider Host and Function Discovery Resource Publication.

Notes

• If you must remain on a Public network, create explicit firewall rules (see firewall section below).

4) Required Windows services are stopped (Function Discovery, WIA, WSD)

Why this causes the problem

• Windows uses services like Function Discovery and WIA (Windows Image Acquisition) to find and communicate with network scanners.

Step‑by‑step solution

1. Press Win + R, type services.msc, and press Enter.
2. Locate these services and ensure their Startup type is set as indicated:
   • Function Discovery Provider Host — Automatic (Delayed Start); click Start if stopped.
   • Function Discovery Resource Publication — Automatic; start it.
   • SSDP Discovery — Manual or Automatic (start if needed).
   • UPnP Device Host — Manual (start if needed).
   • Windows Image Acquisition (WIA) — Automatic; start it.
3. After starting, wait 30 seconds and try scanning again.

Tip

• If any service fails to start, check the Event Viewer for errors and reinstall related Windows components or updates.

5) Windows Firewall or third‑party antivirus blocking scanner

Why this causes the problem

• Firewalls can block the discovery protocols and ports scanners use, preventing communication.

Step‑by‑step solution (Windows Defender Firewall)

1. Open Windows Security > Firewall & network protection > Allow an app through firewall.
2. Click Change settings, then Allow another app… if necessary. Ensure the scanner manufacturer’s scanning app and Network Discovery are allowed on Private networks.
3. To open necessary ports for SMB/File sharing, create new inbound rules:
   • Open Windows Defender Firewall with Advanced Security.
   • Create inbound rule for TCP ports 139, 445, and UDP ports 137, 138 (File and Printer Sharing). Also allow TCP 5357 and UDP 3702 if WSD is used.
4. If using a third‑party firewall or antivirus, temporarily disable it and test scanning; if that fixes it, add exceptions in the third‑party app for the scanner software and ports.

Advanced command

• Reset firewall rules to defaults using admin Command Prompt: netsh advfirewall reset

Notes

• Disabling the firewall is only for testing; do not leave it off.

6) Missing or incorrect scanner drivers in Windows

Why this causes the problem

• Windows needs either a native driver or the vendor’s driver to expose scanning functions to apps.

Step‑by‑step solution

1. Open Device Manager (Press Win + X > Device Manager).
2. Look under Imaging devices, Other devices, or the vendor name for your scanner.
3. Right‑click the scanner and choose Update driver > Search automatically for updated driver software.
4. If Windows cannot find a driver, download the latest scanner driver or full software package from the manufacturer’s website and install it.
5. After installation, restart Windows and try the scanner utility.

Tip

• If you have a multifunction printer/scanner, install the full driver package (not just the basic driver) to get network scanning features.

7) Outdated scanner firmware or vendor app

Why this causes the problem

• Firmware bugs or outdated scanning apps can break network discovery or compatibility with modern Windows updates.

Step‑by‑step solution

1. Visit the scanner manufacturer’s support page and find firmware downloads for your model.
2. Follow their update instructions carefully — often you upload firmware via the scanner’s web UI or run a vendor‑provided update tool.
3. While on the vendor site, download the latest scanning utility (e.g., HP Scan and Capture, Epson Scan, Canon IJ Scan Utility) and install it.
4. Test using both the Windows built‑in Scan app and the vendor app.

Warning

• Do not power off the scanner during a firmware update.

8) Router features: AP/client isolation, guest network restrictions

Why this causes the problem

• Many routers have a “client isolation” or “guest network” mode that prevents devices from communicating with each other even if on the same SSID.

Step‑by‑step solution

1. Log into your router’s admin page—usually at http://192.168.0.1 or http://192.168.1.1; check the router label for the exact address.
2. Look for options named AP Isolation, Client Isolation, Wireless Isolation, or Guest Network.
3. If enabled, disable isolation for the network that both the PC and the scanner use. Move devices off the Guest SSID if necessary.
4. Save settings and reboot the router if prompted.

Notes

• On managed/enterprise networks you may need an administrator to change these settings.

9) IP address conflict or DHCP problems

Why this causes the problem

• If the scanner’s IP changes or conflicts with another device, Windows won’t reliably reach it.

Step‑by‑step solution

1. Print the scanner’s network configuration to obtain its IP address.
2. From the PC, run Command Prompt and use ping . If ping fails, try arp -a to view known devices.
3. If the scanner does not respond, assign a DHCP reservation in your router (find the scanner by MAC address) so it always gets the same IP.
   • Router method: Advanced > DHCP Reservation or LAN > DHCP > Add Reservation.
4. Alternatively, set a correct static IP on the scanner within the router’s subnet (e.g., if router is 192.168.1.1, use 192.168.1.50). Ensure subnet mask and gateway are correct.
5. After assigning, ping the IP again and try scanning.

Tip

• Use a static or reserved IP outside the DHCP auto‑assign pool to avoid conflicts.

---

Additional: Preventive tips and a quick troubleshooting checklist

• Always connect scanner and PC to the same SSID and avoid guest networks for scanning.
• Keep scanner firmware and Windows drivers updated.
• Make sure network profile is Private on your PC and that Network Discovery remains enabled.
• Have a backup: connect the scanner via USB to test whether the issue is strictly network related.
• If intermittent, try using wired Ethernet for the scanner (many MFPs support it) — wired connections are generally more stable for large scans.

Quick troubleshooting checklist (fast sequence to test):

1. Power‑cycle scanner and router.
2. Confirm both devices on same SSID and check IP with ping.
3. Set PC network to Private and enable Network Discovery.
4. Restart WIA and Function Discovery services.
5. Temporarily disable firewall/antivirus and test.
6. Update drivers/firmware if needed.

---

FAQ

Q: Can I scan over Bluetooth instead of Wi‑Fi?

Yes — some scanners support Bluetooth scanning. Pair the scanner in Settings > Devices > Bluetooth & other devices, install the vendor app, and follow the app’s scanning workflow. Bluetooth scanning often has smaller file size limits and lower speed.

Q: Why does my phone find the scanner but my Windows PC doesn’t?

Phones often use vendor apps and mDNS/airscan methods different from Windows; the phone may be on a different protocol or bypass firewall restrictions. Check that the PC is on the same SSID and that Windows services, firewall rules, and scanner drivers are configured as described above.

Q: Does scanning use SMB or WSD, and does it matter?

Both are common. SMB (file share) sends files to a shared folder and uses ports 139/445. WSD (Web Services for Devices) uses discovery on TCP 5357/UDP 3702 and works with Windows discovery. If one method fails, try the other (many manufacturers support both).

Q: How do I forcibly reinstall the Windows built‑in Scan app?

Open Settings > Apps > Apps & features, find Windows Scan, uninstall it if present, then reinstall from the Microsoft Store. For legacy Windows Fax and Scan, enable it via Control Panel > Programs and Features > Turn Windows features on or off.

Q: When should I contact manufacturer support or IT?

Contact support if firmware updates fail, the scanner’s web UI is unreachable despite identical network settings, or if the device shows hardware errors. For corporate networks with VLANs and managed Wi‑Fi, contact IT to ensure device‑to‑device communication is allowed.

---

Conclusion

Wireless scanning commonly fails when devices can’t see each other on the network or when Windows services, drivers, or firewall settings block discovery. Follow the steps above — verify connectivity, set your network to Private, start the necessary services, allow firewall exceptions, and update drivers/firmware — to restore wireless scanning. If you still have problems after trying these fixes for Wireless scanning doesn’t work in Windows 10, contact the scanner manufacturer or your network administrator for help.