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.
I wanted to get the specific step-by-step of TcatHF's procedure in there for 70+ year-olds. So I'll be able to come back & read it myself in a few more years. And PCRSCOMPUTER was not showing until I did it. Apparently, it doesn't need for the Network to be Private for that, either.
Now that I've closed & reopened File Explorer, PCRSCOMPUTER has disappeared again...
And that's the way I like it, actually, having just one computer as I do.
Hi PCR,
We know that it works using the \ComputerName, but that is just another of many workarounds is not a fix.
In your sample you are pinning to quick access a PC that is already showing in the network. If it is already showing in the network there is no need to pin to quick access.
The bug that needs to be fixed is when the computer is not showing in the network place.
Is your computer 1803 or 1809 at "START, Settings, System, About"? There's a specific "fix" depending which. But what TcatHF wrote on page 2 works for either one...
(1) Open File Explorer.
(2) Right-click inside the Address Bar, & select "Edit address".
(3) Type in "\ComputerName" of the computer to connect, & hit ENTER.
File Explorer will go to the Network folder with that computer as a sub-folder.
(4) Right-click the sub-folder in the left pane, & select "Pin to Quick access".
This reply is addressed to all of the people who have tried to solve this problem with not seeing networked PCs. I am 70+ and don't know as much as all of you. But I can see it's not just me trying to get my 2 PC's to see each other and share files It's nice to know that it could well be Microsoft - just trying to change things when it doesn't need changing. I've wasted so much time trying to "fix" the issue and hopefully it will work eventually. I'm not clever enough try some of the options that have been put forward. Need the KISS principle :)
I can't explain it all. SMB version 1 did work but I prefer not to use it. As an aside, many peripherals only use that version with network attached devices. I keep an antique that I use a gateway when I need access to such devices. My problem started with 1809. Solutions that I have come across suggest that FDRP should be started as delayed automatic. That did work on the prior version. Perhaps on 18 core machines and other faster machines that's not enough of a "delay" and I am not going to go wifi in lieu of gigabit hardwire. Clearly, none of us should have this problem. It's not so much that there is a "bug" but more so the process in finding out that it is a bug and that we are not doing something "wrong". Unless I am incorrect, msft silence on the issue is deafening.
I use the script from a prior post. which is essentially restarting Functional Discovery.as posted by fg2001 using the script (or if want batch file)
cmd /c net stop FDResPub
cmd /c net start FDResPub
For now I did put it in Task Scheduler on one machine and may use it on others pay as you go as needed on others since traffic is usually only one way.
I don't expect a fix until April 2019 update.
Thanks for sharing your experience.
