Windows 10, Version 1809. Network does not show computers

Anonymous
2018-10-19T21:34:40+00:00

In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.

I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.

Any ideas?

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

243 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-12-06T02:21:35+00:00

    Have you seen the new cumulative...?...

    https://support.microsoft.com/en-us/help/4469342/november292018kb4469342osbuild17763167

    December 5, 2018—KB4469342 (OS Build 17763.168)

    It says, "Addresses an issue that may cause mapped drives to fail to reconnect after starting and logging onto a Windows device."

    I'm unsure that is close enough for a solution, but worth a look.

    Hello PCR,

     I installed the updates today and I'm now at build 17763.168, it made no difference for the problem described in this thread, I still had to re-enable the workaround to restart FDResPub to see my computer after a restart.

    Again  the problem is only on the machines that have both Ethernet and Wi-Fi adapters and they are connected to the router via Ethernet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-12-06T02:32:11+00:00

    Hi fg2001

    I have exactly the same problem that you describe, in fact I raised a question on this forum about it.

    Restarting the Function Discovery Resource Publication Service will fix the problem, until the next restart.

    I've set up 3 shortcuts (\PC-A, \PC-B, \PC-C) in File Explorer\Quick Access, as a work around.  You can also map the shared drives as an alternative.

    Presumably Microsoft will come up with a fix in due course.

    Hi TcatHF, 

    The shortcuts work too or you can use the workaround suggested by Plarini earlier on this thread to restart FDResPub with the task scheduler until Microsoft fixes the root of the bug.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-12-06T02:48:54+00:00

    "Thought that works, Microsoft recommends getting away from that standard because of issue like the wannacry virus attacks."

    Hi CSAMD, 

    SMBv1 was not checked in 1803 nor it is in 1809, it has nothing to do with the problem described in this thread which is only occurring with 1809.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-06T04:45:30+00:00

    Too bad. That sounded so good.

    Well, mine is 1809 with that latest update & with both Ethernet & Wi-Fi adapters. With only one computer, I never do file sharing & hardly even knew that Network folder existed (or anything else about it). The folder is empty until I switch to Private at "START, Settings, Network & Internet, Change connection properties"...

    Then, it fills with stuff...

    .

    I plugged in my Ethernet. It turned ON & Wi-Fi also remained ON. After a reboot, not only did nothing disappear, but a second "computer" called "full_biscuit" was there. I checked its properties & it appears to be an Amazon thing.

    But the question is - am I unafflicted with the Network folder problem?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-12-06T06:31:00+00:00

    Hi PCR, 

    Could you tell me the computer brand and model and also the model of Ethernet and Wi-Fi adapters you have and the drivers of both ?

    I think it may depend on how quick the Ethernet adapter is up and ready after a restart, so it could be affecting only some machines.

    The problem is that the same machines that work fine with 1803 fail with 1809. Since the hardware is the same something is screwed up in 1809.

    This happens only after a PC restart and not after a normal shutdown/power-up if fast startup is turned on. 

    If fast startup is turned off the problem happens in both cases.

    Was this answer helpful?

    0 comments