Error Fixes5 min read·Apr 11, 2026

Event ID 7036 — Function Discovery Resource Publication Service Stopped (Fix)

Event ID 7036 in Event Viewer with 'Function Discovery Resource Publication service entered the stopped state' is the exact reason network discovery keeps turning off. Here is the permanent fix.

What This Event Means

If you open Event Viewer and search for Event ID 7036, you may see:

The Function Discovery Resource Publication service entered the stopped state. Source: Service Control Manager Event ID: 7036

This event is logged every time the Function Discovery Resource Publication (FDResPub) service stops. And this service stopping is the direct cause of computers disappearing from the Network folder.

If you are seeing this entry repeatedly — sometimes multiple times per day, sometimes after a reboot — you have found the root cause of your network discovery problem.

Why This Service Keeps Stopping

Cause 1 — Startup Type Set to Manual (Most Common)

Windows Updates occasionally reset service startup types. FDResPub gets set back to Manual, and on next reboot it does not start automatically. The service starts when something requests it, runs briefly, then stops when idle.

Check: Open services.msc (Win+R → type services.msc) → find "Function Discovery Resource Publication" → check the Startup Type column.

If it shows Manual: that is your problem.

Fix:

Set-Service FDResPub -StartupType Automatic
Start-Service FDResPub

Cause 2 — Service Dependency Failure

FDResPub depends on other services. If any dependency stops or fails to start, FDResPub terminates shortly after starting.

FDResPub dependencies:

  • HTTP (HTTP Service) — check this is Running
  • RPC (Remote Procedure Call) — almost always running; if not, major system issues
  • SSDPSRV (SSDP Discovery) — needs to be running

Check all dependencies:

Get-Service FDResPub | Select-Object -ExpandProperty DependentServices
(Get-Service FDResPub).ServicesDependedOn | Select-Object Name, Status

Start any dependencies that are stopped.

Cause 3 — The Service Is Crashing (Check Event Viewer Further)

Look in Event Viewer for additional entries around the same timestamp as the 7036 event:

  1. Event Viewer → Windows Logs → Application → filter for errors within 1 minute of the 7036 time
  2. Event Viewer → Windows Logs → System → look for Event ID 7031 ("The [service] service terminated unexpectedly") or 7034

If FDResPub is crashing (7031) rather than stopping cleanly (7036): the service has an unhandled error and Windows is terminating it. This can occur with corrupted system files.

Fix for crashes:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Then restart the service.

Making the Fix Permanent

Setting the service to Automatic startup is not always sufficient if Windows Updates keep resetting it. The permanent approach uses a scheduled task.

Create a Task Scheduler task to ensure FDResPub runs on startup:

Open Task Scheduler → Create Basic Task:

  • Name: "Fix Network Discovery"
  • Trigger: At startup (delay by 30 seconds)
  • Action: Start a program
  • Program: powershell.exe
  • Arguments: -command "Start-Service FDResPub, SSDPSRV, upnphost"

This runs every time Windows starts and ensures the services are running even if their startup type was reset.

Or — create the task via PowerShell:

$action = New-ScheduledTaskAction -Execute 'powershell.exe' -Argument '-NonInteractive -Command "Start-Service FDResPub, SSDPSRV, upnphost"'
$trigger = New-ScheduledTaskTrigger -AtStartup
Register-ScheduledTask -TaskName "FixNetworkDiscovery" -Action $action -Trigger $trigger -RunLevel Highest -Force

Verifying the Fix

After applying the fix:

  1. Open Event Viewer → Windows Logs → System
  2. Filter for Event ID 7036 with source "Service Control Manager"
  3. Confirm subsequent 7036 entries show "entered the running state" for FDResPub rather than "stopped state"

The Network folder should now show other computers on the network reliably.

Why This Keeps Coming Back

The root cause is that Windows Updates can reset service startup types and FDResPub is not treated as a critical infrastructure service by Microsoft's update process. This is a known issue across Windows 10 and 11 with no Microsoft-provided fix.

The scheduled task approach above is the most reliable workaround until Microsoft permanently resolves the service startup type regression.

Done troubleshooting Windows?

Oxolan finds other PCs automatically — no Windows discovery services required.

Get Oxolan for Windows

Frequently Asked Questions

How often does this 7036 event appear? In unmanaged Windows 11 installations, it can appear multiple times per week. In particularly unstable configurations, it appears on every restart.

Does setting the service to Automatic (Delayed Start) help? Sometimes. Delayed Start gives other services time to initialise first, which can prevent dependency failures. Try: Set-Service FDResPub -StartupType AutomaticDelayedStart.

This service was running but computers still disappeared. What else could cause it? If FDResPub is running but PCs disappear: check the SSDP Discovery service as well. Both need to be running. Also check that the network profile on the missing machines is set to Private — machines on Public profile cannot be discovered even when the discovery service is healthy.

We are on a domain. Does Group Policy manage this service? Yes. In a domain environment, Group Policy Object settings can control service startup type centrally. Contact your IT administrator to configure the service startup type via GPO rather than per-machine.

Done troubleshooting Windows?

Oxolan handles file sharing so you never have to think about this again.

Get Oxolan for Windows
← All articles