Windows 10, Version 1809. Network does not show computers

tiffy2VN, 

It looks like you have a different problem than the one described in this thread.

Your issue seems to be related to power management setting with your Ethernet network adapter which apparently is not waking up after a fast startup.

I saw a suggestion to uncheck "Allow the computer to turn off this device to save power" to prevent the adapter for going to sleep. 

Which brand and model is your Ethernet adapter ?

Maybe there is some specific problem with the Model you have.

Perhaps I should of mentioned earlier, my original issue was indeed local network devices randomly not appearing in Win Explorer, tried all the suggestions listed in this thread with limited success, nothing produced a 100% cure on my system.

A few months ago the situation for some reason progressed to no PC LAN connections at all on first boot, readily noticable as no internet access on my desktop PC (ethernet connected) even though my modem/router had a perfectly healthy connection to the line, just not connecting to the LAN, all Wi-Fi connections obviously still healthy.

A restart always re-connected to the modem/router, this was required every time.

The only 100% cure for this situation was in my case to disable Win "fast start-up", this also completely cured the LAN devices visibility issue in Win Explorer.

Can't remember exactly where this "fix" was listed, certainly not original on my part.

As stated earlier, I'am still running Win V.1809 and have avoided V.1903 to date.

Wagnard, 

Keep in mind that the problem is timing dependent.

If the service FDResPub is started before the network adapter is up and running then you have the problem.

Anything that delays the network adapter from coming up and ready can cause the issue.

In one of my failing machines just using a newer network driver eliminated the problem.

The issue is that MS is not checking the status of the connection before it starts FDResPub service.

The symptom discussed in this thread is that the Computer is not visible on the network unless you restart FDResPub.

When that is the case the workaround suggested by Galileo1564 previously in this thread takes care of the problem.

If you get the same problem again before an official fix is available from MS, just try the workaround, it will automatically restart that service for you without further manual intervention.

After trying all of the suggestions in this post over quite a long time period with limited success have found that the only solution that works 100% on my system is to disable fast start-up which does not appear to noticably slow down boot-up in my case, certainly something I can live with and is much less annoying than having to re-start at every boot in order to gain network connection on either the mobo Realtek NIC or with a added PCI Intel NIC..

I have stuck with Win V.1809 and still avoid V.1903 after bad experiences on first upgrade.

That is really weird, because the problem usually happens after a restart and not after a Fast Startup.

Disabling Fast Startup you are just forcing a full Restart each time you shutdown and power up again.

In my failing machines it is just the opposite, it never fails when using Fast Startup, but fails every time after a Restart.

1. With Windows 1809 I had 2 machines with the problem.
2. With Windows 1903 only  one machine has the problem and it is intermittent.
3. With Windows 20H1 insider builds,  5 of my machines have the problem solid after a restart, but not after a Fast Startup (Regular shutdown and power on).

I have manage to fix it on my side.

Here is the story.

First, I have an Asus ROG Strix Z390-H motherboard.

I have tried re-installing Windows 1903 from USB ISO (not just the refresh option).

At first it looked that it work but when I changed the computer name, the problem came back.

Note: at that point I only had minimum driver install ie: chipset, network card etc..

Then I re-installed again and with no driver (installed by me) and the problem was still there.

Again re-installed but this time, decided to DISABLED in my bios something called Armory crate (it was in the "tools" section). This option would make a pop-up right after installing windows suggesting to download Armory Crate. I always deny it.

Even when I deny it, a service named :Asusupdatecheck (or something similar) is install on the system.

I suspect this is the culprit.

Sadly , even after removing it, it will return (probably because of the bios option always checking for it).

So on my end that service is *possibly* making irremediable damage (or hard to fix)

But this time (last time I re-installed) that service didn't install  and the Armory crate didn't pop. (as expected by disabling that bios option).

And this time I have also no problem with the computer listed in network even after changing the name.

So, just sharing my experience.... If you have an Asus board that does the same, you may try what I did.

Some other software from other board manufacturer could maybe do the same.

Good luck.