Windows 10, Version 1809. Network does not show computers

"I use the script from a prior post. which is essentially restarting Functional Discovery.as posted by fg2001 using the script (or if want batch file) 

cmd /c net stop FDResPub

cmd /c net start FDResPub

For now I did put it in Task Scheduler on one machine and may use it on others pay as you go as needed on others since traffic is usually only one way.

I don't expect a fix until April 2019 update."

 Hi CSAMD, 

With Win 10 1803 everything works fine by setting FDResPub service to start as Automatic (No need for Delay start at all), but with Win 10 1809 the service is already started Manually and setting it to Automatic or Automatic (Delay Start) does not help at all. 

I already put the restart in the task scheduler as suggested, with one machine it worked by doing it at Startup, but on another machine I had to do it at Login (Any User) because by doing it at Startup it was still failing intermittently.

As for a MS fix, I just hope they wake up and do some better testing. I have 2 other problems in different threads reported with 1809 feedback, but so far no answer or solution :(

I can't explain it all. SMB version 1 did work but I prefer not to use it. As an aside, many peripherals only use that version with network attached devices.  I keep an antique that I use a gateway when I need access to such devices. My problem started with 1809. Solutions that I have come across suggest that FDRP should be started as delayed automatic.  That did work on the prior version. Perhaps on 18 core machines and other faster machines that's not enough of a "delay" and I am not going to go wifi in lieu of gigabit hardwire. Clearly, none of us should have this problem. It's not so much that there is a "bug" but more so the process in finding out that it is a bug and that we are not doing something "wrong". Unless I am incorrect, msft silence on the issue is deafening. 

I use the script from a prior post. which is essentially restarting Functional Discovery.as posted by fg2001 using the script (or if want batch file) 

cmd /c net stop FDResPub

cmd /c net start FDResPub

For now I did put it in Task Scheduler on one machine and may use it on others pay as you go as needed on others since traffic is usually only one way.

I don't expect a fix until April 2019 update.

Thanks for sharing your experience.

Enabling does "fix" the problem. I have the problem on a few machines with Oct 2018 update. I decided to use the startup script suggested by others in this thread. I used to have in enabled a while back and it will continue to be enabled on major semi-annual updates. It is still not recommended.  Oddly, my fast machines with i7 and i9.extreme chips, regardless of hardwire or wifi have the problem.

CSAMD, 

If you are referring to SMB version 1, it does not help this problem, the only way I get the PC to show up again is by restarting the service FDResPub even though is started and running. 

Again this does not fail with 1803, but only with 1809 using the same machines and the same hardware. 

All my machines have I7 processors, but only fail when using ethernet,  if I use the wi-fi and disconnect the ethernet I have no issue.

Hi PCR,  

"(4) When I plug in Ethernet, Wi-Fi remains ON too, at "START, Settings, Network & Internet"..."

Sure it stays on, but that doesn't mean that it connects. 

It stays on because it can be used for direct wi-fi and miracast, but that doesn't mean that both the ethernet and the wi-fi are connected to the router.

Yes my adapters are set for private network and they stay that way after a reboot.

"(5) I don't think you've got an Ethernet driver problem, if the NET works. Does the icon have an "x" on it during a reboot at the sign-in screen? If not, I think it has gone on quick enough too."

The network adapter may show briefly a yellow exclamation mark, but that goes away immediately before even logging in.

(7) I do think you & Plarini have proven the problem is with that Function Discovery Resource Publication (FDResPub) service. We'd need to figure out why yours isn't restarting on its own. But I don't think the fix you do is so bad, really. Here is the setting at its Recovery tab...

The question why does it need a restart, when I look at FDResPub it is up and running after a reboot.

And why is the problem only affecting the Ethernet and not the Wi-Fi ?

This does not happen using win 10 1803 on the same machines that fail with 1809.

Here is your Dell site...

https://www.dell.com/support/home/us/en/19/product-support/product/xps-8700/drivers

Support for XPS 8700

(1) Uh-huh, MSFT beat the Borg & totally assimilated our Dell Wi-Fi drivers. It happened back in Windows 1607 & hasn't changed since then.

(2) Dell stopped updating our Ethernet drivers at the version you first reported. I went to Realtek for an update when (in 1803 I think) it began to ask to "reboot to complete" its install. It worked when plugged in, but just kept asking. I see there is another one now at Realtek to lift me to what you got (though mine is FE). I may not take it, as I like to stick with Dell & MSFT unless there is a problem. It appears to get half-assimilated only by MSFT.

(3) Update your other drivers, if the Dell site has greater versions (& MSFT hasn't fully assimilated them). Input your service tag to make the site hopefully more specific. Current BIOS version is in MSInfo32 (ask Cortana). Your site has version A13. Normally, I'd take only drivers for devices that actually show up in Device Manager. I never took Nvidia drivers, for instance, because only Intel was in there. And try to get the driver first through Device Manager (search automatically), which may actually get a higher version.

(4) When I plug in Ethernet, Wi-Fi remains ON too, at "START, Settings, Network & Internet"...

And, after the reboot in my test (after going to Private), both remained ON. The icon was still the Ethernet one, & my Wi-Fi printer remained in the Network folder. Does your Network remain Private after the reboot? If not, the Network folder would empty (after it is refreshed, but that's automatic with the reboot). Now, I plugged in Ethernet, turned OFF Wi-Fi, went to Private - & surprisingly everything still showed up in Network - even the Wi-Fi printer showed up. So, it appears not to matter whether Wi-Fi is ON or OFF.

(5) I don't think you've got an Ethernet driver problem, if the NET works. Does the icon have an "x" on it during a reboot at the sign-in screen? If not, I think it has gone on quick enough too.

(6) BTW, my SMB 1.0/CIFS is entirely OFF as in your picture.

(7) I do think you & Plarini have proven the problem is with that Function Discovery Resource Publication (FDResPub) service. We'd need to figure out why yours isn't restarting on its own. But I don't think the fix you do is so bad, really. Here is the setting at its Recovery tab...