Network Computers are no longer showing on my Windows 10 Desktop

Eagle51 · 04 Feb 2018

Hey TV2,
BTW ... I just remembered, you can Disable SMBv1 Server/Client without uninstalling them. So, if you wanted to test just using SMBv2 you could try disabling them on each PC first to see how other PC's and Devices react, before removing SMBv1.

Note: If you're NOT sure what the following does (and how to reverse it) and/or you're NOT comfortable doing it ... THEN DON'T DO IT

Open PowerShell as Administrator
Set-SmbServerConfiguration -EnableSMB1Protocol $false
Set-SmbServerConfiguration -EnableSMB2Protocol $true
sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
sc.exe config mrxsmb20 start= auto
sc.exe config browser start= disabled

Reboot PC ...

Reference - https://support.microsoft.com/en-us/...in-windows-and

Edit: If you try testing this and need/want help, then start a new thread please.

TV2 · 04 Feb 2018

Will do!

TheChrisGregory · 02 Apr 2018

After a fair amount of fiddling around and trial and error the following solution worked for me on a simple Private Home PC network, all windows 10, with Win 10 Pro and Win 10 Home, same solution applied to each PC -

1. In 'Control Panel/Programs and Features/Turn Windows Features on or off', turn off or remove all SMB V1.0/CIFS File Sharing Support features completely (Client, Server and Automatic Removal).

2. Set the following system services in 'Computer Management/Services' to "Automatic/Delayed Start" in Properties/Startup type - "Function Discovery Provider Host" & "Function Discovery Resource Publication" .

3. In 'Control Panel/Network and Sharing Centre' ensure Network Discovery is turned on (for Private Networks) and ensure that 'Turn on automatic setup of network connected devices' is checked.

4. In Network Centre (Windows 10 Settings) perform a network reset, which will require a re-boot.

5. Once restarted, open an Windows Explorer window and browse the network, and re-enable Network Discovery for your private network.

This MS link was the real clue for me, after filtering out the myriad of other suggestions, please read it carefully -

https://support.microsoft.com/en-us/...r-version-1709

Chris

TheChrisGregory · 22 Jun 2018

I also noticed that if some of my computers had the IPv6 protocol enabled (network adapater/properties) on what is essentially a small home IPv4 network (192.168.x.x), this would cause connectivity problems. Remote desktop (IPv4) requests to those computers with IPv6 enabled would generally not respond at all, but occasionally they would - it seemed quite random. Checking that all the network adapters had IPv6 disabled resolved those problems.

madmax2 · 03 Nov 2018

Eagle51 said:

1. Yes, SMBv1 was deprecated due to security concerns (it was patched) and because it's an old technology.
2. You can map a network drive for shared folders.

I also just encounter this problem in 1803

How do you map a network drive if when mapping you click browse, there is no pcs under the network..

Seems like you still need SMB v1 to be able to see those network PCs.

Network Computers are no longer showing on my Windows 10 Desktop

IPv6 & IPv4