@TcatHF
You are most welcome - glad the workaround helped you!
galileo
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
@TcatHF
You are most welcome - glad the workaround helped you!
galileo
Hello Galileo1564
I have 5 pcs in a home network, a home-build Desktop, an ASUS Notebook, an Intel ComputeStick, Surface Studio, and Surface Pro4. The Desktop is ethernet only. The rest are Ethernet or Wi-Fi. The ComputeStick is still on build 1803 and has no network problems. The rest are build 1809, and would not see themselves, or the other 1809 devices, in File Explorer. They were all connected to the network and I could access them using shortcuts (\<Computer name>). The command script made things better, but the devices that had Ethernet or Wi-Fi adapters had to be connected via Wi-Fi, and the device display in File Explorer was inconsistent. The direct task, by waiting until a network connection was established, solved the problem, all 1809 PCs now appear in File Explorer, and those with two adapters can be connected by Ethernet, or Wi-Fi. The range of the devices, two of them over five years old, to the latest, only six months old, shows it to be a good, robust solution. Well done.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
galileo1564 - Thank You, your workaround method seems to be working well for me. I wonder if there is some way to get notified when MS fixes the problem so we will know when to remove the Scheduled workaround Task.
Hi Galileo1564,
I tried your workaround method instead of the previous script on 2 of my computers and it works fine too.