This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
"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.
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.
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.
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,
Make sure you've SMBv1 protocol enabled:
https://www.kapilarya.com/how-to-enable-or-disa...
If you're looking for HomeGroup, it is no longer available now because network sharing is changed on Windows now and HomeGroup is removed on V1803 or later.
Here are the alternatives atm:
https://www.kapilarya.com/homegroup-alternative...
Hope this helps!
Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
Thought that works, Microsoft recommends getting away from that standard because of issue like the wannacry virus attacks.
