Creators Update destroyed Network Discovery on wired LAN

Stigg said:

There are numerous threads about this across numerous forums.
I don't think Microsoft has released a fix yet. [TRUE]

Even though they are not visible in Explorer, you still should be able to access network computers by typing: \\[Computer Name] into the address bar.[thanks]

That works, when the computer name does not show up in the drive mapping window.

I have the same problem my network drive is not showing in the network and also the other computers. i have used a solution found on the internet open regedit:

• Click Start, type regedit in the Start programs and files box, and then press ENTER.
  
• Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
  
• Point to New, and then click DWORD Value.
  
• Type EnableLinkedConnections, and then press ENTER.
  
• Right-click EnableLinkedConnections, and then click Modify.
  
• In the Value data box, type 1, and then click OK.
  
• Exit Registry Editor, and then restart the computer.
  this has worked for a time but after a few reboots the network drive is not showing in the network.
  Other solutions Turn On or Off Network Discovery in Windows 10 Windows 10 Network Sharing Tutorials
  but give met not the solution.
  also on a other computer with creator upgrade everthing work fine.
  
  
  

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.

larry17 said:

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.

Eagle51 said:

Until MS fixes the Master Browser issue with 1703(Creators Update), here are a couple of workarounds that should work.
1. If you have a router that has a USB port (and a USB stick) - Shut down all PC's, insert USB stick in the router (may need to reboot router), then start the other PCs. This should make the router the Master Browser.
2. If you have a pre 1703 PC (1607,win7,win8) on your network - Shut down all PC's, start the pre 1703 PC first, then the other PC's. This should make the pre 1703 PC the Master Browser.

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!

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.

Hoopster said:

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.
.

"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.

jetgraphics said:

I am thoroughly [expletive deleted] disgusted with Micro$oft and Windoze 10.
I believe I shall transition to Ubuntu / Xen, and run Win7 as a guest OS, and scrap Win10.

However, in the meantime, there is an application that bypasses the problem: ipscan25.exe.
Advanced IP Scanner - Help
It scans your LAN and lists all computers.
You can click on an entry and it will open it in the FILE EXPLORER.

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.