Network Devices not Showing with File Explorer

Worked for me too. My question is: Should I do the reversal step too?

Ed Mullen said:

Worked for me too. My question is: Should I do the reversal step too?

Tried it and the answer is no. I suppose when MS fixes this then the reversal should be done.

Sage said:

The fall update broke the SMB (Server Message Block) component of the OS. Below is a work around that will fix your issue until such time as Microsoft patches this issue.
1. Open an administrator cmd prompt.
2. type the following: (press Enter after each line)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

then Restart the computer

All machines Win10 v1511 (b10586.104):

PC#1 showing up on my laptop without applying the tweak.
PC#2 shows up on my laptop AFTER applying the tweak.
PC#3 does not show up on my laptop AFTER applying the tweak.

AFTER applying the tweak to my laptop, PC#3 shows up BUT not actually able to access ANY of the shared folders, just get error "One or more network protocols are missing" and "Windows sockets registry entries required for network connectivity are missing". Tried admin cmd:
netsh int ipv4 install and restart but does not help.
netsh winsock reset and restart but does not help.

In order to get access to shared folders to work again on the laptop I had to revert using:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

Seems I can't win! One way I can see all the shares but cannot access them, the other way some shares don't show up but I can access them (type \\computername).

Many thanks, Sage. It worked like a charm.

I already had individual desktop icons on three of my four networked PCs but the Network icon didn't show them after installing Win10. It does now!

On one of my PCs (my wife's) I hadn't extracted the individual workgroup PC icons from Network and I was stuck.

All's well that ends well.

Sage said:

The fall update broke the SMB (Server Message Block) component of the OS. Below is a work around that will fix your issue until such time as Microsoft patches this issue.
1. Open an administrator cmd prompt.
2. type the following: (press Enter after each line)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

then Restart the computer

To reverse this change and re-enable SMBv3 run the following commands at at the elevated command prompt

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

then Restart the computer

I registered just so I could thank Sage. I have been struggling with this problem for months and have spent the last two days looking for a fix and trying all kinds of CMD fixes and none of them fixed anything. Finally something that works on all eleven of my computers.
Thank you Sage!

stony41 said:

Many thanks, Sage. It worked like a charm.

As tends to happen with Windows networking, I have found today that I have one failure.

I decided to try the fix on my 11-inch laptop that doesn't reside on my home network permanently. When I opened it, it was showing itself and just one of my three other PCs. I ran the fix and unfortunately got the same limited result. Of course, in typical Windows fashion the PCs that it couldn't see could see it.

This failure isn't critical, but it would have been nice to get the fix to work as it had with my four other PCs.

this may work for you, it did for me.

mount the nas
create a shortcut
put the shortcut in the startup folder
restart your machine

with any luck after the system detects your network the nas will show up in network devices

Sage said:

The fall update broke the SMB (Server Message Block) component of the OS. Below is a work around that will fix your issue until such time as Microsoft patches this issue.
1. Open an administrator cmd prompt.
2. type the following: (press Enter after each line)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

then Restart the computer

To reverse this change and re-enable SMBv3 run the following commands at at the elevated command prompt

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

then Restart the computer

The fix didn't do anything for me. I still can't see it on boot-up.

One thing that may help those in the same boat as me is ...
In the Explorer Path text box, if I type
\\NAS
then Windows will then magically find it.

Here's a link of what worked for me... My home server and nas devices are not showing in Network Windows 10 - Microsoft Community
Basically, in your IPv4 Advanced settings/WINS, turn on "Enable NetBIOS over TCP/IP"...Mine was set to Auto. After I turned it ON and rebooted, I could see my NAS and it's shares :)

Sage said:

The fall update broke the SMB (Server Message Block) component of the OS. Below is a work around that will fix your issue until such time as Microsoft patches this issue.
1. Open an administrator cmd prompt.
2. type the following: (press Enter after each line)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

then Restart the computer

To reverse this change and re-enable SMBv3 run the following commands at at the elevated command prompt

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

then Restart the computer

So I did this and now I can see the computer itself, but nothing else on the network, despite getting "SUCCESS" for both instructions. I noticed though that I can enter the name of my router into the address bar of File Explorer and then it appears as a computer in the tree view of Network but still not in the main pane. There are also two other systems running the latest version of Windows 10 64-bit on the network. Any suggestions?