KB5088762 Network Discovery Fails After Switching to Private Network

Symptoms

• Network devices do not appear in File Explorer under Network after switching to Private network
• Network discovery status shows as off despite being enabled in Settings
• Unable to browse or connect to other devices on the local network
• Windows Network Diagnostics reports network discovery errors or related issues

Likely causes

• Windows Firewall rules reset or misconfigured by KB5088762 affecting network discovery
• The Function Discovery Provider Host (fdPHost) or Function Discovery Resource Publication (FDResPub) services are stopped or disabled
• Corrupted or missing network-related system components or registry keys after update installation
• Group Policy settings or third-party security software blocking network discovery on private networks

What FixWin checks

• Verify that Windows Firewall Private profile is enabled and has rules allowing Network Discovery
• Check that 'Function Discovery Provider Host' (fdPHost) and 'Function Discovery Resource Publication' (FDResPub) services are running and set to Automatic
• Inspect the 'Network List Service' and 'SSDP Discovery' services for proper startup type and status
• Review Windows Event Viewer logs under 'Microsoft-Windows-NetworkProfile/Operational' for network profile or discovery errors
• Confirm no Group Policy or third-party firewall is blocking network discovery on private networks

AI diagnostic workflow

• Open Services.msc and verify the status of fdPHost and FDResPub services; start them if stopped
• Use Windows Defender Firewall with Advanced Security to check inbound rules for network discovery under Private profile
• Run 'Get-NetFirewallRule -DisplayGroup 'Network Discovery' | where {$_.Enabled -eq 'True'}' in PowerShell to confirm active firewall rules
• Check Event Viewer logs at Applications and Services Logs > Microsoft > Windows > NetworkProfile > Operational for errors related to network profile change
• Use 'gpedit.msc' to review Local Group Policy under Computer Configuration > Administrative Templates > Network > Network Connections > Prohibit use of Internet Connection Firewall on your DNS domain network

Related Windows entities

• Function Discovery Provider Host (fdPHost) service
  Provides network device discovery functionality essential for network browsing and device visibility.
• Function Discovery Resource Publication (FDResPub) service
  Publishes this computer and its resources so they can be discovered on the network.
• Windows Defender Firewall component
  Controls network traffic filtering; misconfigured firewall rules can block network discovery.
• NetworkProfile Operational Log log
  Records events related to network profile changes and network discovery issues.
• KB5088762 package
  Windows cumulative update that introduced changes affecting network discovery behavior on private networks.

Repair logic

Network discovery failures after KB5088762 commonly result from disabled or stopped discovery-related services and restrictive firewall rules on the Private network profile. Ensuring that fdPHost and FDResPub services are running and that Windows Defender Firewall allows inbound network discovery traffic resolves most cases. Reviewing Event Viewer logs can identify underlying permission or policy conflicts. Group Policy or third-party security software may override settings and require manual adjustment.

FAQ

Why does network discovery stop working after switching to a private network?

Network discovery depends on specific services and firewall rules active on the Private profile. KB5088762 may reset or disable these settings, causing discovery to fail.

How can I check if the necessary services for network discovery are running?

Open Services.msc and verify that 'Function Discovery Provider Host' and 'Function Discovery Resource Publication' are running and set to Automatic startup.

Can third-party firewall software cause this problem?

Yes, third-party firewalls or security suites can block network discovery traffic on private networks. Temporarily disabling them or configuring exceptions can help diagnose the issue.

Related Windows problems

• Function Discovery Resource Publication Not Starting on Windows 11 25H2