Why Network Discovery Keeps Turning Off in Windows 11 and How to Lock It On

Quick fix: Open Services (services.msc). Set these services to Automatic and Start: Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host. Network Discovery depends on all four; if any stops, the feature reverts to Off.

You enable Network Discovery in Advanced Sharing Settings. Reboot the PC. Network Discovery is Off again. Or it stays on for a few hours and then disables itself. The cause is one of four required services not running — Windows reverts the toggle to Off when dependencies aren’t ready.

What causes this

Network Discovery is implemented via SSDP (Simple Service Discovery Protocol), DNS-SD, and WSD (Web Services Discovery). Four Windows services must all be running for it to work: Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host. If any are set to Manual and not started, or fail to start, the Settings UI reverts to “Off” even when you toggle it On.

The fix: set all four to Automatic and start them.

Method 1: Enable all four discovery services

The standard fix.

1. Press Win + R, type services.msc, press Enter.
2. For each of these services, double-click to open Properties:
   • Function Discovery Provider Host
   • Function Discovery Resource Publication
   • SSDP Discovery
   • UPnP Device Host
3. For each: set Startup type to Automatic. Click Start if not running. Click Apply → OK.
4. Verify in PowerShell:

   Get-Service fdPHost, FDResPub, SSDPSRV, upnphost | Format-Table Name, Status, StartType

   All four should show Running, Automatic.

5. Open Control Panel → Network and Sharing Center → Change advanced sharing settings. Verify Network Discovery is now toggleable and stays on.
6. For Windows 11 Settings path: Settings → Network & internet → Advanced network settings → Advanced sharing settings → Network discovery. Toggle On.

This handles the most common cause.

Method 2: Verify network profile is Private (not Public)

Network Discovery is blocked on Public networks by design.

1. Open Settings → Network & internet → Wi-Fi (or Ethernet).
2. Click the connected network name.
3. Under Network profile type, pick Private network.
4. This allows Network Discovery and File/Printer Sharing.
5. For domain-joined PCs: the profile may be Domain, not Private or Public. Domain has its own discovery rules controlled by Group Policy.
6. For home networks accidentally classified as Public: changing to Private also enables File and Printer Sharing, which you may want or not. Adjust those toggles separately in Advanced sharing settings.

This handles network profile mis-classification.

Method 3: Reset network stack and re-enable discovery

For when services and profile are correct but Discovery still doesn’t stay on.

1. Open Terminal (Admin).
2. Reset network stack:

   netsh int ip reset
   netsh winsock reset
   ipconfig /flushdns

   Reboot.

3. After reboot, re-enable Network Discovery via Advanced sharing settings.
4. For PCs where Discovery still toggles off: open Windows Defender Firewall → Allow an app through firewall. Verify Network Discovery is allowed on Private and Domain networks. If unchecked, tick.
5. For Group Policy-managed PCs: gpresult /h C:\gpresult.html — look for network policies that might enforce Discovery off.
6. For PCs where home network shows as Public despite repeated change to Private: Settings → Network & internet → Advanced network settings → Hardware and connection properties. Note the network. Open Registry Editor → HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles. Find the profile, set Category = 1 (Private).

This handles stubborn cases.

How to verify the fix worked

• Open File Explorer → Network. Other PCs and shared devices on your network appear.
• From Network & internet → Advanced sharing settings: Network discovery shows On and stays on across reboots.
• Run net view in Terminal. Lists discovered shared resources.

If none of these work

If Network Discovery toggles off despite all services running and profile being Private, deeper causes apply. Antivirus blocking SSDP/WSD: third-party antivirus (Norton, Kaspersky, Avast) may block multicast traffic. Add exception for Network Discovery’s ports (UDP 1900, 5355) or disable AV firewall temporarily to test. Router blocking multicast: some routers (especially in commercial settings) block IGMP/multicast at the router level. Network Discovery uses multicast to find devices. If your router does, you can’t discover other devices regardless of Windows settings. Check router admin panel for IGMP snooping or multicast forwarding. For corporate PCs joined to Azure AD: Intune policies often disable Network Discovery for security. IT controls this. For VPN connections: when VPN is up, the VPN profile may suppress Network Discovery to local LAN devices. Allow LAN access in VPN client settings.

Bottom line: Four services must run for Network Discovery: Function Discovery Provider Host, FD Resource Publication, SSDP Discovery, UPnP Device Host. Set all to Automatic. Profile must be Private.