Network Discovery Windows 10 Not Working
Network discovery lets Windows 10 see other devices on the same local network and be seen by them. When network discovery Windows 10 not working, you cannot browse PCs, printers, or NAS devices from File Explorer. The most common causes are a mismatched network profile, a stopped service, or a firewall rule blocking it. The fixes below move from the quickest checks to deeper repairs, and they work whether you are on Wi-Fi or Ethernet.
- Network Discovery Windows 10 Not Working
- 1. Check Your Network Profile
- 2. Verify the Function Discovery Provider Host Service
- 3. Reset the Network Stack
- 4. Check Firewall and Antivirus
- 5. Enable SMB and File Sharing Features
- 6. Manually Add a Device or Access by IP
- 7. When to Check the Router
- 8. Create a New Network Profile
More from this site
Keep reading the latest coverage
1. Check Your Network Profile
Windows 10 disables discovery on public networks for safety. If your Wi-Fi or Ethernet connection is set to Public, discovery will stay off.
- Open Settings > Network & Internet > Status.
- Click Properties under your active connection.
- Set Network profile type to Private.
After switching, return to Network & Internet > Advanced sharing settings and confirm that Network discovery is turned on under the Private profile.
2. Verify the Function Discovery Provider Host Service
Discovery relies on the Function Discovery Provider Host service. If it is stopped or disabled, Windows 10 will not find other devices.
- Press Win+R, type services.msc, and press Enter.
- Find Function Discovery Provider Host.
- Double-click it, set Startup type to Automatic, and click Start if the service is stopped.
- Repeat for Function Discovery Resource Publication.
3. Reset the Network Stack
A corrupted TCP/IP or DNS cache can break local name resolution and discovery. Resetting the stack clears these without affecting personal files.
- Open Command Prompt as Administrator.
- Run the following commands in order, pressing Enter after each:
| Command | Purpose |
|---|---|
| netsh winsock reset | Resets the Winsock catalog |
| netsh int ip reset | Resets TCP/IP settings |
| ipconfig /release | Releases current IP address |
| ipconfig /renew | Renews IP address |
| ipconfig /flushdns | Clears DNS resolver cache |
Restart the PC after running all five commands.
4. Check Firewall and Antivirus
Windows Defender Firewall can block discovery if a rule was accidentally disabled or if third-party software is interfering.
- Open Control Panel > Windows Defender Firewall > Turn Windows Defender Firewall on or off.
- Ensure the Private network setting has the firewall turned on, not off.
- If the option is greyed out, run the Microsoft Fix It tool for Windows Firewall or check Group Policy.
For third-party antivirus, temporarily disable the firewall component and test discovery again. If it starts working, add an exception for Function Discovery or File and Printer Sharing.
5. Enable SMB and File Sharing Features
Discovery uses SMB (Server Message Block) to advertise shares. If the SMB component is disabled, other PCs will not appear.
- Open Control Panel > Programs > Turn Windows features on or off.
- Expand SMB 1.0/CIFS File Sharing Support.
- Ensure SMB 1.0/CIFS Client and SMB 1.0/CIFS Server are checked.
- Also check Function Discovery Resource Publication under Network Services.
Restart after making changes. Note that SMB 1.0 has known security weaknesses; if you do not need legacy compatibility, keep it disabled and rely on SMB 2.0/3.0, which is on by default.
6. Manually Add a Device or Access by IP
If discovery still does not list a PC or NAS, you can reach it directly. In File Explorer's address bar, type two backslashes followed by the other PC's local IP address (for example, \\192.168.1.25). This bypasses the discovery broadcast and works as long as file sharing is enabled on the remote machine.
7. When to Check the Router
If multiple Windows 10 PCs on the same network cannot see each other, the router may be isolating clients. Look for AP Isolation, Client Isolation, or Guest Network settings in the router admin page and disable them. Also confirm that all devices are on the same subnet — a PC on 192.168.1.x and another on 192.168.0.x will not discover each other.
8. Create a New Network Profile
A corrupted profile can persist even after switching to Private. Deleting the profile forces Windows to create a fresh one.
- Open Network and Sharing Center.
- Click the active connection, then click Delete this network profile.
- Reconnect to the Wi-Fi or Ethernet and set the new profile to Private.
This resets the network location and usually re-enables discovery.