windows 10 aio 1703 build 15063 august 2017 activation

They are getting rid of SMB v1.0, which is fair enough, it has real security issues. SMBv1 is not installed by default in Windows 10 Fall Creators Update 2017 and Windows Server, Semi-annual Yes, that's right folks, after 25 years of being able to browse our networks Microsoft have decided Workgroup users don't need this functionality any more. The Computer Browser service is broken in Windand is gone from future releases of Windows. It's not good news, but it is the answer. The Computer Browser service is disappearing, you will need to create permanent drive mappings and shortcuts to devices or folders so you don't need to browse, I wrote the below about it on another post. 'how did you get on?' just means 'have you had any progress?'

If a non-1703 pc is master browser all pcs but the 1703 pcs will get the list of pcs, the 1703 pcs net view works but just getsĪs it only happens to people running workgroups there is no fix yet, but you may be able to work around the issue until they get round to it by forcing a specific pc to be the master browser or configure a non-Microsoft device as the master browser. It is more likely to do with the known issue with the master browser that still hasn't been fixed.īasically, if a machine with 1703 is the master browser the other pcs in the workgroup can't net view but the 1703 can. I got the list from a post from Microsoft in the Community Forum.Īs it was working fine before the update to 1703 I doubt the issue is that 'SMB 1.0/CIFS File Sharing Support' is not already ticked. Network discovery is turned on as well as is file and printer sharing.Let's take one particular computer as an example: Since this is happening to all systems on the network, it does not seem like it is an issue for just any particular system.

I have rebooted the entire network (modems, routers, switches, computers and NAS) from the ground up and it has not made any difference. I did run the network Troubleshooting, but it found no problems. I do not have a HomeGroup defined and so following the Troubleshooting steps 10 - Network Discovery: Windows 10 Settings and Control Panel. All the rest have the same name as my primary desktop system. My wife's and it has a different user name.

Curiously, the one other system that each Windows 10 box sees is They only see themselves and the one other system. This issue is true for all systems on the network. Network discovery is turned on as well as is file and printer sharing. All devices can be found this way and so Windows sees them, but is not showing them in Windows Explorer. Other device can only be accessed by entering the network path, e.g., \LaCie-5big. Of the six devices active on the network, it only shows two. Since installing WindWindows Explorer is no longer finding most of the devices on my network.

Windows 10 aio 1703 build 15063 august 2017 activation