Windows 10: function discovery resource publication could not start error. i have already receive many...

• 

https://support.microsoft.com/help/4026529/windows-10-using-system-file-checker


this is a link with the closest to my problem that I was given but it did not work. the second to last post in this link said that there was nothing to change when I ran the command in cmd safe mode.

:)

 

Function Discovery Resource .Publication

Hi Joshua,
I became aware of the problem several weeks ago when I could not find another computer on the local network. It had been working okay before. There have been no significant changes that I know of.
I found an article that said I should check if the following services are enabled and running: DNS Client, Function Discovery Resource Publication, SSDP Discovery and UPnP Device Host. All were running except for Function Discovery Resource Publication.
It was enabled (Automatic (Delayed Start)) but each time I tried to start it, I got the error message:

Windows could not start the Function Discovery Resource Publication service on Local Computer.
Error 0x80004005: Unspecified error

I suspected this was the cause of not finding the computer on the network, but didn't know how to fix it. Yesterday I tried another tactic by going to Settings / Network and Internet / Status / Network Troubleshooter. It seemed to find a problem and correct
it, and then I was able to find the computer on the network by refreshing Windows Explorer. However Function Discovery Resource Publication was still not working. Today when I checked I found I could not find the computer again.
Regards,
Larry

 

Function Discovery Resource .Publication

Hi Joshua,
I became aware of the problem several weeks ago when I could not find another computer on the local network. It had been working okay before. There have been no significant changes that I know of.
I found an article that said I should check if the following services are enabled and running: DNS Client, Function Discovery Resource Publication, SSDP Discovery and UPnP Device Host. All were running except for Function Discovery Resource Publication.
It was enabled (Automatic (Delayed Start)) but each time I tried to start it, I got the error message:

Windows could not start the Function Discovery Resource Publication service on Local Computer.
Error 0x80004005: Unspecified error

I suspected this was the cause of not finding the computer on the network, but didn't know how to fix it. Yesterday I tried another tactic by going to Settings / Network and Internet / Status / Network Troubleshooter. It seemed to find a problem and correct
it, and then I was able to find the computer on the network by refreshing Windows Explorer. However Function Discovery Resource Publication was still not working. Today when I checked I found I could not find the computer again.
Regards,
Larry

 

Function Discovery Resource .Publication

Hi Joshua,
I became aware of the problem several weeks ago when I could not find another computer on the local network. It had been working okay before. There have been no significant changes that I know of.
I found an article that said I should check if the following services are enabled and running: DNS Client, Function Discovery Resource Publication, SSDP Discovery and UPnP Device Host. All were running except for Function Discovery Resource Publication.
It was enabled (Automatic (Delayed Start)) but each time I tried to start it, I got the error message:

Windows could not start the Function Discovery Resource Publication service on Local Computer.
Error 0x80004005: Unspecified error

I suspected this was the cause of not finding the computer on the network, but didn't know how to fix it. Yesterday I tried another tactic by going to Settings / Network and Internet / Status / Network Troubleshooter. It seemed to find a problem and correct
it, and then I was able to find the computer on the network by refreshing Windows Explorer. However Function Discovery Resource Publication was still not working. Today when I checked I found I could not find the computer again.
Regards,
Larry