Windows 10: Creators Update destroyed Network Discovery on wired LAN

What fixed my win10Pro machine not being able to be seen by other machines on the network after updating to 1703 was to update the network adaptor driver and restart the computer. Now all machines (a win7 and XP machine) can see the win10 machine.

 

All machines have up to date drivers. And I've tried every fix that I could find on the net. The LAN is mostly Win10 machines. And they exhibit the Network Search / Master Browser bug, dropping computers from the NETWORK subsection of FILE EXPLORER.

 

I had same problem. All computers were 1703. I turned all computers off. Pulled the power cord from the router. Waited 20 seconds. plugged in a USB memory stick. powered router back up and waited for it to fully initialize (about 2 minutes). Started turning computers back on and they could all see each other.

In addition, I have some NAS devices that could be located on the local network only by IP address, not be device name (such as NAS01). After this procedure, everything was visible and accessible again.

I have no idea why the USB thing worked, but thank to Eagle51!

 

Microsoft put out a bulletin to roll back to AE and defer going to CU. I have to map by IP to a network share on my NAS, for the machine I am having to run Windows on to do some Genealogy work on.

I have my NAS running as Master Browser, just have not gotten around with digging deeper into the whole mess, since I am able to just map to the one folder I need to get to.

 

I have the same problem mentioned in this thread and the funny thing is it just started yesterday. All of the wired PCs (Windows 10 1703 with one WIndows 7) can see each other and the Linux NAS computer in the Windows Network. However, the Windows 10 1703 laptop can only see itself. Yesterday morning it could see the whole network correctly but now it only sees itself. Typing \\computer_name in the address bar or trying to map a drive by computer name fails. The only way to access other computers is by IP address. That is fine with the NAS since it has a fixed IP, with the other and their DHCP address it means more work.

On the laptop I tried the ipscan25.exe mentioned by the OP and it does not see all computers on the network, but, those it does see I can access.

My NAS was specifically set in the SMB settings to be the master browser. I turned this off and tried the USB stick in the router solution with no change. The laptop will only see itself.

I updated the NIC drivers to the latest for my model on the Lenovo site as well as updating some other things while I was at it. No change. I have checked and double checked network discovery and sharing settings on all computers

This is most frustrating since it was working. In fact I was streaming a video off the NAS yesterday morning when it just decided to quit accessing the NAS computer via windows network. First the audio went, then the video and then everything disappeared from the Windows network on that machine and nothing will force the missing computers to show up. Most frustrating.

 

"Readyshare (the USB stick in the router)" did become the master browser, so, the USB stick trick worked to force the router to become master browser; however, the laptop still wants to be alone and not communicate with anything on the network accept by IP address.

 

Addendum: The latest scanner is advanced_ip_scanner.exe, not scanner25.exe.

I also experienced another problem with Win10 CU (1703) - the inability to re-install my PVR software (Beyond TV) - even when using cmd.exe in administrator mode. I tried rolling back to an earlier version, and the bug remained. Ditto, for the network discovery / master browser bug. This effectively ended my tolerance for Win 10. I have since re-installed Win7 on all machines and my problems are no more.

 

I have given up on trying to figure out how to fix this mess that Microsoft has caused. I spent two days trying to fix their mistake with Network Discovery, that I just mapped our NAS shares that my wife needs on the desktop that I have to use for a genealogy program that the person who wrote it, only wrote a Windows version.

 

It looks like Snapstream no longer updates Beyond TV, because they have gotten into a bigger market with education, healthcare and government.

Next PVR, Kodi or Plex would be your best choices. I use Plex for our HDHomerun tuner that we have for watching Sub-Channels and the Cubs playing on one of the locals that is only in HD with OTA.

 

It worked for me.
After weeks trying to solve the problem.
Many thanks

 

I tried #2, but it didn't work for long. After a day or so, started dropping computers from the list.

 

If you haven't already, on your Win10 PCs try the following ...

Windows Services > Computer Browser
Stop if running
Set Startup Type to Manual

Regedit > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
MaintainServerList = No

 

I have not seen one fix for how Microsoft found a way to hack their SMB to allow the discovery services under SMB1 to work with SMB 2 & 3. I just enabled SMB1 to see what would happen, since having to enter the IP of our NAS on the network was getting old. Everything is back in Explorer for those devices on the network that have shares available.

As slow as Microsoft is in fixing the problems that they create to cause everyone headaches. I would suggest that if you do decide to enable SMB1 to fix shares not being there, then enable a Firewall rule to block any outside the network access. Do this at your own risk if you do not have a good Gateway, or continue to map with the IP of the device.

 

Like many here, I have one Windows 10 (1703 CU) computer that shows no other computers in the network other than itself. All other computers (mix of Win10 and Win7) show the others in the Windows Explorer Network, including the misbehaving computer.

Running ipconfig /all on all computers reveals the one difference I can identify between the problematic laptop and all the rest. NetBIOS over tcpip on the wireless adapter on the laptop shows disabled. On all the other computers it is enabled.

My Network contains the following machines (each with shared folders that need to be accessed by the others):
- NAS box running Samba (this machine is configured as the local master browser and is elected as such)
- Windows 10 wired desktop (version 1703 CU)
- Windows 7 wired desktop
- Windows 10 (pre 1703 version) wireless laptop
- Windows 10 (version 1703 CU) wireless laptop - this is the problem machine

I have tried everything to enable NetBIOS over tcpip on the problem machine. Checked this option in the network adapter WINS tab, modify registry key to set this option on this interface, run the PowerShell wmic nicconfig, performed a network reset and reconfigured, etc. After all of these, ipconfig /all continues to report that NetBIOS over tcpip remains disabled on this NIC.

The problems I see on this laptop are the following:
- Shows only itself in the Network
- Can connect (non-persistent) to other Windows computers by name; e.g. \\servernane in Network address bar and these then show up in Quick Access until Explorer is closed or machine is rebooted
- Cannot connect to NAS server other than through IP address; it can't find it by server name
- Even though the laptop appears in the Network on all other machines, it is NOT accessible by any of them via clicking on the laptop in the Network or by attempting to access it by IP address. It can be pinged from all other computers.

The bottom line is that NetBios over tcpip is the only difference and nothing I have tried will enable this service on the problematic laptop.

Any ideas other than those I have tried?

 

Hoopster you have done everything that I have done and that is why I ended up just going back to enable SMBv1. Even Samba does not always work in a mixed environment, but Microsoft should have thought of the whole Samba/CIFS thing when SMBv2 rolled out, which is now becoming to the point that it is at its end of life and SMBv3 is where the NAS manufacturers are at for those that are on the higher end.

I guess that we could just all resort to using FTP/SFTP if Microsoft cannot get their game together.

I just went and tried a fix for Master Browser, because my Synology NAS is set to be it. Now Windows 10 is stating too many connections. I may just end up give up and reinstall fresh.