can't sign on
Windows 10, Version 1809. Network does not show computers
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.
243 answers
Sort by: Oldest
-
Anonymous
2018-12-09T01:28:53+00:00 -
Anonymous
2018-12-09T01:30:53+00:00 can't sign in
-
Anonymous
2018-12-26T18:09:43+00:00 Hi Albertk_77,
There is still a problem that is not fixed in the latest 17763.195.
The problem affects computers that have both the Ethernet and the wi-fi adapter and they are connected to the router via Ethernet.
For those cases the workaround is to restart the service Function Discovery Resource Publication.
There is a workaround procedure to make the restart automatically described in another thread by
Plarini.
A restart of the FDResPub service gets it working properly. I came up with a workaround to restart the service automatically at system startup. You may have already done this, but others may benefit.
- Create a command script named FDResPub.cmd with these two lines:
cmd /c net stop FDResPub
cmd /c net start FDResPub
- Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
- Use Task Scheduler to create a new task:
Name: FDResPub
Description: Restart the FDResPub service.
Run whether user is logged on or not.
Run with highest privileges.
Configure for: Windows 10
Triggers: At Startup
Actions: Start a program C:\Scripts\FDResPub.cmd
Optional start at: C:\Scripts
This has worked for both restarts and shutdowns with Fast Start disabled.
-
Anonymous
2018-12-28T03:55:39+00:00 Works only on first restart. I use the scrpit to turn function discovery off then on.
Question will be should we keep this bug or after it is fixed deal with new ones.