Windows 10: Creators Update destroyed Network Discovery on wired LAN

Supposedly, both SMBv1 and SMBv2/3 are enabled on the laptop. The PowerShell Get samba config applet shows TRUE for SMBv2 but SMBv1 is blank even though I have explicitly set it to true via PowerShell, registry edits, enabling in NIC properties, etc. Other methods show SMBv1 as enabled.

I do not think Samba on the unRAID NAS is in any way the issue; especially since all other computers can access it without issue and see all public shares. It does not appear that the NAS is limited to SMBv1. Most samba issues from the NAS side (excellent support and community for unRAID) seem to be related to Windows credentials and authentication issues that need to be cleaned up from the Windows side.

I have set the NAS as the local master browser as it has an excellent utility for doing so and will report which machine is the master browser.





A reinstall of Windows on the laptop may be in order (what a PITA). What frustrates me the most is that this was all working last week even though Win10 CU has been installed on the laptop for a couple of months. Unfortunately, I discovered that System Protection was off on that laptop so I cannot just do a System restore to a working config. It seems that Windows version updates frequently mess with such settings.

 

I finally found the solution. Big headache of trying to find it, but the breakdown is at [SOLVED] Disabling SMB1 stops domain authentication - Windows Forum - Spiceworks

You are leaving smb1 enabled in Windows Features under Programs and Features, since the Computer Browser Service is attached to that (Why Microsoft could not see that issue and leave CB to not get removed out of Services, shows proof that we are smarter than the idiots in India). Then just enter the following commands to disable the smb1 bugger:

To disable SMBv1 on the SMB client, run the following commands:

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

Yep, works like a charm, just make sure if you have a NAS, that it is not set to be the SMB Master Browser, or it will break Windows, unless you feel like fixing Windows to not be the Master Browser, which to me is too huge of a headache.

 

Nothing in this or any other thread on the subject has resulted in a solution. I did manage to fix a few things, but, the laptop still only sees itself in the Network. I am running a full backup now preparing for a complete OS and apps reinstall.

 

I decided to reinstall Windows 10 1703 (Creator's Update) on the problematic laptop as doing so allowed me to keep files and installed apps. Worst case; I would have to reinstall a prior version and all apps. Of course I backed up up the entire system first.

The OS reinstall WORKED! All computers appear in the Windows Explorer Network and all apps remained installed and functional (at least all those I have tested). Hopefully the problem is resolved "permanently." There must have been some problems with OS core files or drivers that were fixed by the reinstall of the OS.

 

I just gave you the solution in how to fix keeping Computer Browser Service running, while disabling SMBv1 from the Command prompt and the link to the thread that I found yesterday while doing some more searching.

 

There are no "core" files at fault. What is at fault is when SMBv1 is shut down or another computer becomes Master, it will cause things to not work. See my post above this one and the post at #30 in regards to how to fix the issue with Computer Browser Service no longer in Services when SMBv1 is disabled or completely removed by Microsoft.

 

I tried every combination of suggestions in this thread for enabling/disabling SMBv1, setting router as Master Browser, enabling NetBIOS over tcpip, etc. As has been mentioned here and in other threads, sometimes enabling a feature through one method alone does not change the setting. I had to use PowerShell applets, registry tweaks and programs/features or interface settings to get SMB and/or NetBIOS settings where I needed them to be. No changes were ever made to any settings on any other computer.

I once tried the "force the router with a USB stick to be the master browser" trick and it made no difference. My NAS was before and continues to be the master browser. I have not allowed any Windows computer to become the master browser (as far as I know) since the NAS can ensure that it is the elected master browser and always reports itself as such. Despite ensuring that SMBv1 was enabled and NetBIOS over tcpip was enabled and that no other Windows computer was the master browser, the laptop simply would not show any other computers in the Network. After yesterday's reinstall, all is well. It has survived several reboots and an update to version 1703.540 (the latest) and continues to display all other devices in the network. It is possible that all my fiddling broke something in SMB, NetBIOS, etc. and that the reinstall simply fixed what I was not able to do manually. I wish I knew exactly what that was for future reference, but, all devices on the network are now behaving as expected.

 

Again I gave the solution to disable SMBv1, not in Windows Features, along with changing Computer Browser Service to Automatic, which fixes the problem. If you are still having issues, then there is something else going on that is not a part of Windows or its services. There is no force the router to fix the problem. The router has zero interest in Master Browser or Samba, unless it has its own form of SMB/CIFS that is proprietary, which would need to be addressed to the manufacturer. If third party firmware on your router, then contact the group that screwed up their firmware.

 

I am still having problems with this Master stuff.

Never did all these years.

It's driving me nuts trying to see boxes on my LAN.

Done the shut all down then main one first up. All mine at 1703.

I changed the registry to 1 for the Main box but yet whomever is started first, gets the Master role.

I use Netbscanner to check who is who on the network. Great free program.

 

It appears I'm suffering from this exact same problem.Should I jump aboard this thread or should I start a new thread topic. Please advise.

 

.I'm confused by what you mean with the NAS being set as the SMB Master Browser. What is the default setting? I have a Synology RS815+.

Since upgrading Windows, I've been unable to see other computers in network locations or to connect/browse to my NAS. Trying to make sure I don't mess up here and mess up Windows.

 

I have a NAS a Qnap TS231P on the same LAN and I have not set it as Master and it does not even show on my Netbscanner inquiries.

All Win 10 1703 boxes have static IPs however the NAS is DHCP. Maybe that should be static too!

The SMP1 resolve sounds good but I am a bit hesitant as I have never done that before and thge last thing I need is a really messed up box or network.

 

Windows 10 needs a lot more than better interface and prettier design. User experience will not be significantly improved unless they improve the system as a whole. I mean, when you have to learn how to remove duplicate files, it says something. I am getting Vista flashbacks. Not to mention my boosting adventures when I tried to become a gaming streamer. At least Macs are easier to handle this way - when they break, they really break, factory reset and throwing it in the trash are the best and only solutions. Windows makes you want to keep it safe, fix it. And Windows 10 is like an abusive partner to me in this regard.
I desperately hope for something more substantial.

 

Disable the Master Browser

Good news for now! I just ran across this article by googling "Master Browser" and so far so good. I can see my Freenas folders again! A quick registry change and rebooting (bringing up Freenas first) then Win10 switched it. If it stays, we'll see. I have saved the registry key if I need to re-apply it as well as the pre-"Master Browser" key if I have to revert.

 

The only fix that worked for me was to revert to Windows 7. My network is restored to me. My legacy software will install and run. And my taskbar isn't clogged by Cortana. Win-Win.