none
Anyone else notice the network issues with Windows 10 Creator's edition?

    Question

  • I installed Win 10 creators edition on my main PC. Strangely I could no longer connect to the shares on it from my Oppo BD player. Stranger still I turned on one of my spare PCs and I could no longer connect to the shared folders on that PC either! I thought it might be some update or master browser issue. I turned off my main PC with creators edition and strangely enough my win 10 anniversary edition now showed up on the oppo. I then turned on my main PC (creator's edition) again and the shares for it also showed on my oppo. But when I boot the creator's edition PC first it doesn't show up and any subsequent windows PCs (creator's or anniversary) don't show up either.

    I set up a WINS server in case that might help and pointed to the wins server on the NetBIOS page of network properties.  It didn't help so I looked at ipconfig to verify that I had the wins correct - the wins properties no longer show in ipconfig on Windows Creator's edition.

    I did some master browser tests and it doesn't seem to show what the problem is (at least from my ability to check).   I did test the shares between Windows 10 editions and no problems.

    I did a search and someone else trying to connect to the SMB share with his non-windows device had a similar problem.

    I just went to recovery and went to an earlier build and boom the shares show again - no problem.

    Tuesday, April 11, 2017 4:00 PM

All replies

  • Hi,

    Did you mean before Creator Update, all computers show on the Oppo?

    Please run network reset tool to see if it can resolve the issue:

    1. Select the Start  button, then select Settings  > Network & Internet  > Status > Network reset.

    2. On the Network reset screen, select Reset now > Yes to confirm.

    3. Wait for your PC to restart and see if that fixes the problem.

    If it cannot resolve your issue, please submit this feedback via the built-in Feedback app. And roll back to previous build as a workaround temporarily.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Tinchote2 Saturday, September 16, 2017 4:15 AM
    Wednesday, April 12, 2017 2:05 AM
    Moderator
  • Have the same issue, can't connect to shares on Windows 10 creators edition Machines via netbios or fqdn name, however it works if I connect via ipv4 (\\192.168.1.1\c$ for example). Windows firewall rules are enabled to allow incoming filesharing traffic. Worked with Windows 10 1511 and 1607, the problem appears only with 1703 (creators edition). The computers were upgraded from 1607 via upgrade-task-sequence configuration manager.

    Wednesday, April 12, 2017 7:41 AM
  • Hi,

    Did you mean before Creator Update, all computers show on the Oppo?

    Please run network reset tool to see if it can resolve the issue:

    1. Select the Start  button, then select Settings  > Network & Internet  > Status > Network reset.

    2. On the Network reset screen, select Reset now > Yes to confirm.

    3. Wait for your PC to restart and see if that fixes the problem.

    If it cannot resolve your issue, please submit this feedback via the built-in Feedback app. And roll back to previous build as a workaround temporarily.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Yes before the creator's update all did show.   I have tried a  reset and have tried removing my nic and adding it back.
    Thursday, April 13, 2017 12:16 AM
  • Have the same issue, can't connect to shares on Windows 10 creators edition Machines via netbios or fqdn name, however it works if I connect via ipv4 (\\192.168.1.1\c$ for example). Windows firewall rules are enabled to allow incoming filesharing traffic. Worked with Windows 10 1511 and 1607, the problem appears only with 1703 (creators edition). The computers were upgraded from 1607 via upgrade-task-sequence configuration manager.

    ! Unfortunately my Oppo requires a broadcast list - it can't be told to go to an IP or even a name. I also tried disabling the firewall.

    • Edited by boe_d Thursday, April 13, 2017 12:17 AM
    Thursday, April 13, 2017 12:17 AM
  • I also can no longer connect to network shares.  

    Specifically I can't access the machine using ES File Explorer on Android after the update.  I use this to stream videos between the PC and the Android. ES File Explorer is now asking for login credentials when I tap my PC. No credentials are valid.  Previously no credentials were even required because I have the network shares set to "Everyone". 

    ----------------------------------

    My temporary fix around this BS was to create a new IIS site with the root directory set to the media drive. I then had to set the IIS application pool user to my Microsoft xxx@live.com account.  Then set the media drives permissions so that my microsoft account has full control of the media drive because "Authenticated Users" wasn't enough apparently. Next I had to add MIME types for different media types such as ".mkv - video/x-matroska". Now to play media on other devices on my local network I have to use a http browser such as Chrome. 

    If you're going to force upgrades get your s*** together microsoft. Also FTP has the same login credentials issue, because I tried that before I tried http.  Allowing Anonymous Users doesn't seem to work and no login credentials I have work. 

    Thursday, April 13, 2017 6:49 AM
  • We can no longer connect to shares either on our 1703 Windows 10 PCs
    Tuesday, April 18, 2017 7:46 PM
  •  my Oppo requires a broadcast list.

    This reminds me that there was a problem in the preview that had a workaround that took advantage of having some broadcast traffic from its  ipconfig /renew6   command and I wondered if that worked what about  ipconfig /registerDNS  instead, since that seemed to be more on target...

    Here's an example.  (I couldn't find my comments--naturally!)  

    https://social.technet.microsoft.com/Forums/windows/en-US/9cb202d0-8f0f-445b-a7ce-1aa46bfeb883/windows-10-anniversary-update-breaks-dhcpv6-client?forum=win10itpronetworking

    (BING search for
        ipconfig  renew6  site:microsoft.com
    Custom Date:  Last year
    )

    The last post claims that the symptom was fixed (at least in non-Enterprise versions) but maybe there was a regression or maybe the fix created new related problems?

    In any case, does that workaround do anything to change your new symptom?



    Robert Aldwinckle
    ---

    Wednesday, April 19, 2017 6:28 PM
  • We are experiencing the same issue across several of our client's networks.  After the Windows Redstone 2 update, Workgroup shared computers and folders are no longer visible in Network list under File explorer unless a Homegroup is setup.  Even with the Homegroup, a WIFI connected device can not see any Homegroups on the network, and devices can not find Homegroups if devices are connected to different switches.

    Prior to the update, all shared folders were present and connected.  In some cases, legacy shared printers on local devices were connected, and now can only be connected via Homegroups when devices are connected in the same manner on a switch.

    We've attempted resets, changes of settings (Windows to Manage shares vs Homegroup), reset of switches and gateways, etc. without success.  

    This is occurring across several different networks.

    Friday, April 21, 2017 5:31 PM
  •  reset of switches and gateways, etc. without success.  

    Since a Homegroup implies IPv6 connectivity what about changing that?  This also would raise the point which was mentioned in one of the older threads about this symptom that knowing the Discovery method could provide a clue.  E.g. enable that column in the Network folder in File Explorer to see it.  I wish they would let that choice persist.  It is annoying having to change it every time I want to see it!


    Robert Aldwinckle
    ---

    Friday, April 21, 2017 6:48 PM
  • I just noticed this on my recently updated Win 10 Pro workstation. I can map drives and shares just fine, but damned if I can't see anything else on the network, Mac or Windows. However on my Dell XPS13 I can see everything just fine and it's been updated as well. Rebooted everything on my network and reset the network and still nothing.
    Friday, April 21, 2017 8:24 PM
  • Same issue here,I have a HTPC set up on my TV running KODI connected to the main PC that has all my digital content on. Was working 100% till Creator edition update was loaded at which point I was completely unable to connect the the SMB shares. I can setup the homegroup shares without any issue but these folders can not be viewed in KODI only via windows explorer.
    Saturday, April 22, 2017 1:06 PM
  • i have the same issue, before the creators update my wd tv live could see my network share pc, now it can't, i tried alot it must me a bug 
    Saturday, April 22, 2017 8:22 PM
  • I am having the exact same issue.  I have a network with 7 Windows 10 units that received the 1607 update.  For some reason 1 still sees the network computers fine.   The other 6 do not.  I have duplicated setting and done the reset with out success.  Apparently MS is not helping yet.  
    Sunday, April 23, 2017 12:51 AM
  • Frustrating.  I'm sure there are a lot of the same--loss of discovery.  And in our case, even manually entering the IP or FQDN for shares or other computers that were 'upgraded'... (not sure that's the word I want to use)... we either dont see the computers or if we do, some or all of the shares arent accessible.  ... even tho before the 1703 update they all worked.. win10pro, win7pro/ult, nas, etc.

    We are fully peer in this setup and again nothing changed other than what MS's update did.

    I wonder if there are any MS guys actually paying attention to this one.  It is very frustrating not only for us internally, but our smb customers that are running peer networking with what was a stable win10pro environment.

    Chet.
    MS Partner, Houston, TX

    Sunday, April 23, 2017 7:27 AM
  • It is the Master Browser in Win 10 (1703).

    I still have one machine in my LAN running Win 10 (1607). I made that machine the Master Browser and my WD TV Live (streaming device) could see the shares on both machines. After that I switched the Master Browser back to Auto on the 1703 machine and the shares were gone again.

    So I guess it is fair to say Master Browser is not working correctly in 1703. 

    • Proposed as answer by rob5289 Wednesday, April 26, 2017 4:48 PM
    Sunday, April 23, 2017 4:43 PM
  • I've also got the same issue since upgrading to Windows 10 Creator's Edition.

    Tuesday, April 25, 2017 6:05 AM
  • Hi guys,

    I noticed with last two upgrades problems with FTP speed. Using filezilla on latest Windows 10 Creators Update and previous update as well.
    Can't get more than 500kb/s per file.

    Tested speed from the Windows 8.1 pro under the same network it works fine. OSX Yosemite works fine as well.
    Same file same settings on these two is downloading 10mb/s but on windows 10 500kb/s and not more than than.

    Month and half ago it was working well now it's total disaster.
    Login in to SFTP -SSH is impossible on latest win10 upgrade.

    Preview of Monthly quality roll-up April 2017 is making these problems as well. Didn't do it on Windows 8.1 Pro and it's working fine.

    Anyone experiencing or had a same problems?


    • Edited by vfxmag Tuesday, April 25, 2017 8:32 AM
    Tuesday, April 25, 2017 8:13 AM
  • Guys good news...
    Found solution for this problem:

    1. Tap on the Windows-key, type cmd.exe, hold down Shift and Ctrl keys, and hit enter.
    2. Confirm the UAC prompt that opens.
    3. Run the command netsh interface tcp show global.

    Run the following command to disable Window Auto-Tuning on Windows 10:

    netsh int tcp set global autotuninglevel=disabled

    This is done by running the following command:
    • netsh int tcp set global autotuninglevel=normal

    Tuesday, April 25, 2017 11:35 AM
  • it is because that you are trying to use your Microsoft account as user name. make a local account an the target machine. and on your machine add target machine to  manage credentials. next time you try to access to the target computer hard drive it will use it and you will see no errors 
    Tuesday, April 25, 2017 12:11 PM
  • not using Microsoft account as user name. Never set this up.

    Tuesday, April 25, 2017 2:15 PM
  • I've seen issues with wifi and the speeds i get more than anything.  I saw major drops in performance over wifi and SMB/CIFS shares. I was able to transfer files around 30MB/s over my 802.11ac network on the 1607 build but once i went to 1703 creator built my speeds went to a horrible 500KB/s to 1MB/s. Once i rolled back to 1607; speeds were back to 30MB/s again. 

    Prior to rolling back, i tried the latest drivers and several older versions of the Intel Proset Wireless drivers; even reverted to the windows updates version of the driver; same horrible performance.  I have a Brix S with Intel 3165 wifi.  Seems creator update has a ton of wifi issues from what i've seen just in the last week and forums.



    Paid IT Geek; mobile/desktops/deployments

    Wednesday, April 26, 2017 3:21 PM
  • If you're going to force upgrades get your s*** together microsoft. Also FTP has the same login credentials issue, because I tried that before I tried http.  Allowing Anonymous Users doesn't seem to work and no login credentials I have work. 

    agreed. we have just rolled out win10 at work (1607) build and seriously have already gotten several bad windows and office updates that has hurt our productivity greatly.  they should NEVER force us to update; it is on us if we get hacked however it really should be on them on building a proper and secure OS to start with.

    Paid IT Geek; mobile/desktops/deployments

    Wednesday, April 26, 2017 3:23 PM
  • Guys good news...
    Found solution for this problem:

    1. Tap on the Windows-key, type cmd.exe, hold down Shift and Ctrl keys, and hit enter.
    2. Confirm the UAC prompt that opens.
    3. Run the command netsh interface tcp show global.

    Run the following command to disable Window Auto-Tuning on Windows 10:

    netsh int tcp set global autotuninglevel=disabled

    This is done by running the following command:
    • netsh int tcp set global autotuninglevel=normal

    i may try updating to creators build again and try this. i think you are onto something my friend! :) thanks for posting your possible solution; us geeks gotta band together on this one :)

    Paid IT Geek; mobile/desktops/deployments

    Wednesday, April 26, 2017 4:17 PM
  • Can confirm. I rolled back two Creator's Edition PCs on my peer-to-peer network and made sure that one was master browser. My WDTV Live could then see and access the usual shares. When a 1703 machine is master browser, none of the other computers show up in the WDTV's "network shares".

    This is now quite repeatable behavior. Before turning on the WDTV Live, I have to start up a non-1703 unit and stop the computer browser on the 1703  (which has the media files). Then the WDTV works as expected.

    Network reset and the netsh commands mentioned in this thread had no effect.


    Friday, April 28, 2017 8:23 PM
  • Can confirm too. I have the same problem WD Tv Live + Win 10 1703.

    Microsoft guys, please give us a hope !!!

    Saturday, April 29, 2017 12:25 PM
  • Guys good news...
    Found solution for this problem:

    1. Tap on the Windows-key, type cmd.exe, hold down Shift and Ctrl keys, and hit enter.
    2. Confirm the UAC prompt that opens.
    3. Run the command netsh interface tcp show global.

    Run the following command to disable Window Auto-Tuning on Windows 10:

    netsh int tcp set global autotuninglevel=disabled

    This is done by running the following command:
    • netsh int tcp set global autotuninglevel=normal

    I tested autotuning - does not solve the browser issue in my environment although turning on a 1607 computer and disabling browser service on a CU edition does.
    Sunday, April 30, 2017 7:02 PM
  • it is because that you are trying to use your Microsoft account as user name. make a local account an the target machine. and on your machine add target machine to  manage credentials. next time you try to access to the target computer hard drive it will use it and you will see no errors 
    This is not the case for me - I don't use MS account for anything - all local accounts.
    Sunday, April 30, 2017 7:03 PM
  • Use Registry Editor and check Win10 settings.  Make these changes and it should work.

    KEY: HKLM\System\CurrentControlSet\Control\Lsa
    DATA: everyoneincludesanonymous = 1
    KEY: HKLM\System\CurrentControlSet\Control\Lsa
    DATA: NoLmHash = 0
    KEY: HKLM\System\CurrentControlSet\Control\Lsa
    DATA: LmCompatibilityLevel = 1
    KEY: HKLM\System\CurrentControlSet\Services\LanManServer\Parameters
    DATA: restrictnullsessaccess = 0

    Tested in my environment -does not help.

    Tested with a friend - seem same problem - only solution so far is to either disable Computer Browser on the 1703 edition and boot a 1607 computer on the same network or roll back the 1703 edition to Windows 1607.

    • Edited by boe_d Sunday, April 30, 2017 8:28 PM
    Sunday, April 30, 2017 7:12 PM
  • I think more people are going to have to write to MS - I've already sent them something but I did that when beta testing vista telling them Vista was slow but it didn't have much impact :O
    Sunday, April 30, 2017 7:18 PM
  • I did the following to fix my file shares on a 1703 desktop:

    start -> run -> ncpa.cpl

    right click active network adapter -> properties -> uncheck "File and Printer Sharing for Microsoft Networks" -> OK

    right click active network adapter -> properties -> check "File and Printer Sharing for Microsoft Networks" - > OK



    File shares started working again. Also tested with a ios device using Remote File Manager and was able to browse 1703 desktop windows share.

    D


    • Proposed as answer by Zverev Eugene Wednesday, June 28, 2017 12:44 PM
    Monday, May 01, 2017 1:44 AM
  • I did the following to fix my file shares on a 1703 desktop:

    start -> run -> ncpa.cpl

    right click active network adapter -> properties -> uncheck "File and Printer Sharing for Microsoft Networks" -> OK

    right click active network adapter -> properties -> check "File and Printer Sharing for Microsoft Networks" - > OK



    File shares started working again. Also tested with a ios device using Remote File Manager and was able to browse 1703 desktop windows share.

    D

    That didn't work for me, unfortunately.
    Monday, May 01, 2017 8:43 AM
  • I've also tried enabling disabling smb/cifs, disabling sharing, logout, renabling windows sharing.   I've tried creating new shares.   Again the issue really really really seems to be the master browser/computer browser service in Windows 10 Creators Edition.
    Monday, May 01, 2017 1:52 PM
  • This is exactly the same network neighborhood browsing problem that arose at the end of 2015 after a major update at that time, and persisted into the early months of 2016, until it mysteriously vanished after a subsequent update that must have contained a fix.

    Accessing shares, in and of itself, works perfectly well, but many (all?) of us are unable to browse our networks in the way with which we have become familiar since the early days of Windows networking. While not normally a necessary feature, it is an enormous convenience that has, apparently, become expendable in the interests of heightened security, at least in the eyes of Microsoft's software engineers.

    I have tried every single proposed fix found anywhere and everywhere on the web, and nothing has worked. I did exactly the same thing in 2015, and the only thing that eventually worked was waiting for Microsoft to issue a fix. I probably won't give up, just like many of you, and will continue to twist and tweak my network settings in an (apparently) futile effort to restore network browsing.  I have little hope of success, and my greatest worry is doing more harm than good by FUBAR-ing my current setup so badly that it will never be right again. <Sigh.>
    • Proposed as answer by JacekCh Thursday, July 20, 2017 2:38 PM
    • Unproposed as answer by JacekCh Thursday, July 20, 2017 2:39 PM
    Monday, May 01, 2017 2:06 PM
  • I wanted to chime in and say I'm having the same issues as well after updating to the 1703 build.  I have 2 WDLive TV boxes that were working fine until the update.  Once I updated they no longer see anything on the network.  I too have tried the fixes here and so far nothing has worked.  Don't really want to have to roll back but in the end I will if it fixes the issues until the issues with 1703 have been resolved.
    Monday, May 01, 2017 11:57 PM
  • I found the problem on my offending computer. Below is how I fixed it. I hope this fixes it for you also.
    For some reason, my file sharing connections encryption setting was changed to "Enable file sharing for devices that use 40- or 56-bit encryption".


    Go to the problem computer and do the following.

    1. Open Network and Sharing Center
    2. Click "Change advanced sharing settings"
    3. Select "All Networks"
    4. Under "File sharing connections", select "Use 128-bit encryption to help protect file sharing connections (recommended)"
    5. Restart.

    Your computer should now be visible again.
    You may have to ensure that the same encryption setting is on all computers in your network.
    Tuesday, May 02, 2017 1:38 AM
  • I found the problem on my offending computer. Below is how I fixed it. I hope this fixes it for you also.
    For some reason, my file sharing connections encryption setting was changed to "Enable file sharing for devices that use 40- or 56-bit encryption".


    Go to the problem computer and do the following.

    1. Open Network and Sharing Center
    2. Click "Change advanced sharing settings"
    3. Select "All Networks"
    4. Under "File sharing connections", select "Use 128-bit encryption to help protect file sharing connections (recommended)"
    5. Restart.

    Your computer should now be visible again.
    You may have to ensure that the same encryption setting is on all computers in your network.

    checked on mine - unfortunately it was already set for 128 - changing it in any way does not help.   The issue appears to be a master browser/computer browser glitch in Windows 10 version 1703.
     I have different nics on each system and the latest drivers on each. 
    • Edited by boe_d Friday, May 05, 2017 5:08 PM
    Wednesday, May 03, 2017 1:12 AM
  • This free utility made me no longer care about this absurd problem: http://www.advanced-ip-scanner.com/

    It doesn't "fix" what is broken in Windows network browsing, but it completely replaces the lost functionality with a superior capability, and it is unequivocally free.
    Wednesday, May 03, 2017 8:28 AM
  • I have found a problem with network discovery since installing 1703.
    I started with 5 PC's with win10 build 1607. I upgraded them one at a time to Win10 1703 over a period of a few days. I found a few anomolies with Internat Explorer and the Control panel link from start up menu disappearing but nothing too worrying until I had all 5 working together on myhome  network. I then noticed that Network discovery was not working correctly. It took a good deal of checking network settings and the services. It was at first a bit confusing and certainly time consuming with lots of restarts and restesting. It was rather unclear when a machine would not display the Network list in Windows Exploere. Was it because that machine was not discovering the aother machines on the network or was it because the other machines were not discoverable. Anyway I managed to get to a clear conclusion on this and I list the findings here.

    1. Before upgrading all 5 machines were working perfectly on Build 1607. Each could see all 5 In the Explorer Network display and this display would track macines as they joined and left the network in real time.
    2. After upgrading, 3 of the machines worked correctly as described in 1. above but two would not display anything in the Network list. The two bad machines could be seen in the Network list of the three good machines but neither could see any other machines good or bad.
    3. The main difference between the 3 good machines and the 2 bad is the good machines are all pretty modern systems and the two bad ones are older machines. One is used for test and experimental purposes and the other is used as a print server.
    4. It looks very much then like a hardware/driver issue rather than a OS setting. All 5 machines have exactly the same parameters set for Networks   and the same services running.
    5 Looking closer I discovered that the two bad machines , one a Dell Optiplex 745 and the other an HP DC5758 small form factor each have the same Network chip set on their motherboards. Broadcom NetExtreme 57xx Gigabyte controllers AND the same drivers . Version 17.2.1.0 dated 19/8/2015. The driver was not changed by Windows upgrade from 1607 ( some drivers do change for a major upgrade I know from previous experience). The driver a signed by Microsoft. These machines do not have the same motherbaords only the same controller chips
    6. So as a final step I reverted my test machine to 1607 and without doing anything else to it apart from checking that the drver for the network card was the same version as before this machine then could see all the others and began to display correctly in the Network list as it did before.
    7. Though not a complete proof it looks very much like the 1703 version of Windows 10 is unable to see other machines in the Network but can be seen by machines with 1703 or 1607 when this Controller and driver are installed.

    8.I can add that I bought a PCIe Controller based on the Realtek PCIe GBE family and that corrected the problem. All works fine now in 1703 which I reinstalled after fitting the card. It appears my hunch was correct. It cost just £3.96 from Maplin. Thank goodness for hunches. Tony Parsons


    • Edited by Tony Parsons Saturday, May 06, 2017 1:39 PM
    • Proposed as answer by Tony Parsons Saturday, May 06, 2017 1:39 PM
    Friday, May 05, 2017 8:45 AM
  • To complete my posting of May 05, 2017 about the anomalous Network Discovery I can add that I bought a PCIe Controller based on the Realtek PCIe GBE family and that corrected the problem. All works fine now in 1703 which I reinstalled after fitting the card. It appears my hunch was correct. It cost just £3.96 from Maplin. Thank goodness for hunches. Tony Parsons
    Saturday, May 06, 2017 1:37 PM
  • So Oppo BD player is working fine now?

    I have the same problem with WD TV Live.

    Saturday, May 06, 2017 9:19 PM
  • Just to point out that both my desktop and the server (Server 2012 R2) have a Realtek PCIe GBE family network controller and the WD Live can't see any network shares since the Creators Update.

    Switching to NVidia Shield where I can point directly to the server's IP.

    Sunday, May 07, 2017 9:30 PM
  • A lot of people have the same issue (so am i)... looks like its a 1703 bug...
    Monday, May 08, 2017 9:10 PM
  • Thank you . This fixed my networking issue (on a domain but the network profile was set to public). I suspect a recent update caused the problem.

    Andrew

    Tuesday, May 09, 2017 8:45 AM
  • I did the following to fix my file shares on a 1703 desktop:

    start -> run -> ncpa.cpl

    right click active network adapter -> properties -> uncheck "File and Printer Sharing for Microsoft Networks" -> OK

    right click active network adapter -> properties -> check "File and Printer Sharing for Microsoft Networks" - > OK



    File shares started working again. Also tested with a ios device using Remote File Manager and was able to browse 1703 desktop windows share.

    D


    This solved my problem! Thanks!
    Saturday, May 13, 2017 9:01 AM
  • Is It fix WDTV Live problem?
    Saturday, May 13, 2017 11:52 AM
  • I installed the Creators Update on my Surface Pro 3 and on my Desktop-PC. Unfortunately... Now, i cant't connect my Network Media-Player (WD TV Live Media Player) to all my shares. I hate every time to copy my files to an external HD, again, again, again.

    In many forums i read about the same and similar problems from many peoples.

    Saturday, May 13, 2017 1:35 PM
  • I've lost all access to my NAS, as well as to the other computers on my network. This is a serious issue, especially for normal domestic users like myself who simply cannot understand the discussion here about "broadcast" and "ipconfig".
    Saturday, May 13, 2017 4:49 PM
  • I'm experiencing the problem that scanning from a network device (mfp) to a computer does not work anymore.

    - Credentials are correct

    - Different brands of Printers

    - Was working fine in 1607

    - Different Networks (different customers, persists even on my own client, in my own network)

    - Scanning to clients that have not been updated yet (still on 1607) works perfectly

    I'm afraid this issue will also come to Servers (2016) when installing the update 1703 (2017-05). Now how many mfp's scan to shared folders on a server. Immagine that.....

    Saturday, May 13, 2017 6:40 PM
  • Looks like whatever the issue is KB4019472 for 1607 causes the same problem.   To be clear, we aren't talking about SMB between two windows computers we are talking about SMB between a windows computer and a device - NAS, WDTV, Oppo etc.

    • Edited by boe_d Saturday, May 13, 2017 11:11 PM
    Saturday, May 13, 2017 9:29 PM
  • I am encountering the same problem:

    1. I can nslookup all devices on my network, but I can't ping neither router , NAS nor Linux. I can only see another windows pc on my network. 

    2. Some research reveiled that enabling Netbios could help, at least for the NAS.

    3. Netbios, however strangely cannot be enabled in Windows 10 creator.

    4. The second windows pc still is pre-creators and shows netbios enabled. It can perfectly see everything on the network. 

    5. Network reset, as suggested by microsoft did not do the job.

    Hence I blame it on the creators update and most likely on the permanently disabled netbios. 

    Any other updates?

    Thanks, Daniel



    Monday, May 15, 2017 12:17 AM
  • 3. Netbios, however strangely cannot be enabled in Windows 10 creator.

    Daniel,

    Can you explain further how you weren't able to enable NetBIOS in v1703?  I'm not having any problem with this setting.

    Monday, May 15, 2017 8:20 AM
  • Hi,

    I too experienced trouble with shares no more shown within MS Explorer.

    After looking in detail to the NIC protocols I manually added "Reliable Multicast-Protocol" and my shares reappeared in MS Explorer.

    I hope this will solve your issue.

    Kind regards

    Ottmar

    Monday, May 15, 2017 10:04 AM
  • Hi,

    I have the same problem to use or map samba network shares by Explorer after Creators Update (1703).

    For me it works to use the command shell (as user not admin) and the command "net use m: \\SERVER\SHARE /persistent:yes" 

    After this the mapping is established and the share is available within Explorer, too.

    Seems to be something wrong for mapping or using network shares within Explorer.

    kind regards

    Axel

    Monday, May 15, 2017 10:54 AM
  • John,

    thanks for the reply!

    I compared an older win10 pc with the problematic one. The former shows all network connected devices and "ipconfig /all" reveals activated Netbios over TCP/IP. The Creators machine does neither show the devices nor activated Netbios. In addition I cannot force Windows to use it: Whatever settings I try in Ip4 advanced config, it does not change this.

    I have to admit I am NOT a network expert, but I'd like my computer to work again. Therefore I had guessed that this could be a problem.

    Any suggestions?

    Monday, May 15, 2017 9:04 PM
  • I compared an older win10 pc with the problematic one. The former shows all network connected devices and "ipconfig /all" reveals activated Netbios over TCP/IP. The Creators machine does neither show the devices nor activated Netbios. In addition I cannot force Windows to use it: Whatever settings I try in Ip4 advanced config, it does not change this.

    Logged in to a user with admin rights, go to Settings (Win + I) and click on Devices.  On the right side under "Related settings", click on Device Manager.

    On the Device Manager, expand the Network adapters, right click on the adapter you use, and click Uninstall Device.  Reboot and the adapter will be reinstalled.  Check ipconfig and see if NetBIOS is enabled.  Also confirm that you can enable it under the adapter's advance config as you had tried previously.

    If this doesn't work, repeat the procedure but instead of clicking Uninstall Device, click Update Driver to determine if an updated driver is available.  If it is, let it install and re-check the issue.  You can always rollback the driver update if you need to.

    Post back with your results.


    • Edited by john.b_ Monday, May 15, 2017 10:46 PM
    Monday, May 15, 2017 10:46 PM
  • No luck. In addition I cannot ping my router by name and it appears that win10 creators will only use ipv6 for this. My router does not have this enabled.
    Monday, May 15, 2017 11:54 PM
  • appears that win10 creators will only use ipv6 for this. My router does not have this enabled.

    If ISATAP was working properly that would not matter.



    Robert Aldwinckle
    ---

    Tuesday, May 16, 2017 12:13 AM
  • John, Robert,

    somehow my fault. I've updated my router some time ago. Windows 10 creators obviously did not like to talk properly with it after that. Everything is working again now - with some replacement router.

    Therefore the question still remains: why did everything work with pc2 (running pre-creator update), but not with pc1 (win10 creators). Anyway, I am out of eagerness to find out at the moment. I'll stick with the replacment device. 

    Thanks again,

    Daniel

    Tuesday, May 16, 2017 12:46 AM
  • Tried the uninstall adapters including drivers, reinstalled with the latest drivers (april 2017 for mine) no joy.
    Wednesday, May 17, 2017 11:54 AM
  • Tried the uninstall adapters including drivers

    How?  Coincidentally someone gave another Like for  netcfg -d  yesterday and indicated it solved a discoverability issue.

    https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-network-computers-missing-on-some/382f483f-f3dd-4093-841b-07441864d59f?page=4&msgId=7a41b5b5-eacb-4d4d-9370-1d10b7118040



    Robert Aldwinckle
    ---

    Wednesday, May 17, 2017 12:49 PM
  • I have the same issue but with Kodi Krypton on my TV. I cant acess my movies/TV Shows since the creator update and when I try to find my computer in the SMB section of Kodi on my TV, can't find it. Strangely, I dont have this problem with my MacBook who still has acess to my shared folders. But Kodi on my MacBook doesn't find my Windows 1703 either.

    ----------------------------------------------------------------------------------------------------------------

    So I tried the "NetCFq.exe -d" command as admin, it worked on my other computer running Windows 1607 (I can see my 1703 PC). Now I can see my both of my computers on my TV Kodi but still unable to connect.

    ----------------------------------------------------------------------------------------------------------------

    After a bit of testing, the "NetCfg.exe -d" command solved my problem. My connection problem was with the password protection of the shared computer on the network, I disabled it and now it works!




    • Edited by Larousse96 Thursday, May 18, 2017 4:31 PM
    • Proposed as answer by Larousse96 Thursday, May 18, 2017 4:31 PM
    Thursday, May 18, 2017 3:16 PM
  • Tried the uninstall adapters including drivers

    How?  Coincidentally someone gave another Like for  netcfg -d  yesterday and indicated it solved a discoverability issue.

    https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-network-computers-missing-on-some/382f483f-f3dd-4093-841b-07441864d59f?page=4&msgId=7a41b5b5-eacb-4d4d-9370-1d10b7118040


    Robert Aldwinckle
    ---

    I went to device manager - removed the adapter and the drivers.  netcfg -d doesn't solve my problems - never had issues between windows devices - just windows devices and DEVICES -e.g. Oppo BluRay player (Doesn't run a windows OS).    I think that is the problem - there are people here talking about windows to windows and windows to devices - probably need to be two different threads as the solutions to windows to windows don't help with windows to devices.


    Saturday, May 20, 2017 2:38 AM
  • I had some spare time today so I did a FRESH install of Windows 10 CU. As long as I had my 1607 windows computer on the shares on my CU computer showed up. If my 1607 computer was turned off and I turn on my CU is turned on it doesn't show up on my Oppo. It isn't a matter of it showing up and not being able to get to the share, it doesn't show up at all. The Oppo is a very simple device, you can't program in IP addresses of other devices it only shows what the computer browser is handing out. The computer browser/master browser seems to be the issue in the CU version of Windows when trying to browse from NON windows devices.
    Saturday, May 20, 2017 2:41 AM
  • Windows 1703 network stack is screwed up somehow. I see different problems on different areas frequently and no viable solutions. Only some workarounds :(

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.

    Saturday, May 20, 2017 5:47 AM
  • I tried the "NetCfg.exe -d" and it did not work.  I have to computers on the CU.  On CPU1, I can access the network share on CPU2.  But on CPU2, I cannot access the network share on CPU1.

    On both I can access CPU3 and CPU4, but I do not need anything on those!

    However, I just tried this.  On CPU1, I went to the network adapter properties, unchecked the file and print sharing.  Close it.  and then went back in and rechecked it, and now I can access CPU1 shares from CPU2

    Saturday, May 20, 2017 11:24 AM
  • Oppo not working for me - I have a number of adapters - intel, realtek, killer - none work even with the latest drivers direct from the manufacturers or using the MS supplied drivers.   There are the people with windows to Windows browsing - most seem fooled to think they've solved it because they reboot or disable computer browser on it and it just moves the master browser to another computer on their network.    For people with DEVICES (not running windows) there is no solution yet.
    • Edited by boe_d Saturday, May 20, 2017 1:46 PM
    Saturday, May 20, 2017 1:45 PM
  • Just to report that without any changes on my behalf (that I am aware of) my WD Live magically saw the whole network in Windows Shares yesterday night.

    Still no idea what changed but everything works.

    Saturday, May 20, 2017 3:41 PM
  • Our WDTV magically sees all the network shares if I have the appropriate device running as master browser. A non-1703 Windows machine, the ancient NAS, even a "compute stick" - anything but the "Creator's Edition" is fine. I'll have to try a Pi.

    When only the 1703 machine, with the media shares, is running, I can still cast directly to the WDTV, and after some experimenting I enabled Windows Media Player as a streamer, which works reasonably well. So we are not completely out of luck.


    Saturday, May 20, 2017 7:46 PM
  • Anyone know where to download the 1607 edition of Windows 10? All I can find on the download page is the CrapUpdate edition.
    Sunday, May 21, 2017 5:31 AM
  • I managed to get a good copy (1607) from a friend.
    Sunday, May 21, 2017 9:23 PM
  • Hi

    It is a block of port 445 in the windows firewall on new Creators edition.

    Open windows firewall then advanced then inbox

    You will see the block for 445 TCP and UDP

    simply open each and allow connection

    all shares will work

    Wednesday, May 24, 2017 12:03 AM
  • Changed it on all my systems and all is sharing nicely now.  In addition, had to change this on all systems running 1607 as well; not only on 1703.

    Now to the ultimate question.  Why was port 445 blocked in the first place?  

    Update:  Found out port 445 was blocked due to the recent WannaCry ransomware virus.   

    Wednesday, May 24, 2017 12:47 AM
  • Hi

    It is a block of port 445 in the windows firewall on new Creators edition.

    Open windows firewall then advanced then inbox

    You will see the block for 445 TCP and UDP

    simply open each and allow connection

    all shares will work

    Unfortunately that is not it for non windows devices - I had turned off Windows firewall completely on 1703 and it didn't help.

    • Edited by boe_d Wednesday, May 24, 2017 2:58 AM
    Wednesday, May 24, 2017 2:57 AM
  • I've done multiple combinations of all of these and cannot resolve.

    I have four pcs with all with Windows 10 CU on a home office peer to peer network with a QNAP NAS (QTS 4.3.3 Linux based).  All of this is routed through an ASUS RT AC5300 running the latest Merlin firmware 380.66_2.

    One of the pcs connected ethernet through a powerline adapter (not sure that matters) was able to see all the devices until it restarted this morning, now it has turned "zombie" like the rest.  The "zombies" sometimes see one of the other devices and might even see themselves but never see the NAS running Linux.

    I'm able to search and find everything either by host name or by ip so the firewall is not blocking access to the device or shares.

    I'm tempted to try creating a homegroup to see if that changes anything, that comes with it's own frustrations... thinking it may be something with IPV6? 

    Thursday, May 25, 2017 3:20 AM
  • I have the same issue.  When I updated to 1703 several of my computers became invisible on the home network.  The visible computers all have an Intel Ethernet chip of one vintage or another on the motherboard.  The computers that became invisible had Broadcom and Killer Ethernet chips on their motherboards.  Somebody above said that either Intel or Realtek Ethernet chips/adapters work on 1703.  I guess I agree!  Although, it's only subjective, it seems that the Discovery process is slower now that I'm trying to use 1703.

    Microsoft, I'm losing faith, this seems like the same kind of BS that went on in W8.1.  I don't understand how something this obvious did not get resolved before releasing the 1703 update.


    • Edited by Ken1440 Friday, May 26, 2017 10:17 AM
    Friday, May 26, 2017 10:11 AM
  • My consistent workaround is on the computer I cannot access, go to network properties and un-check file and print sharing.  Hit ok.  Go back into properties, and check again.

    This has to be done after any reboot.

    Friday, May 26, 2017 4:36 PM
  • One of my machines that isn't working has intel, one that isn't working has killer and two that are not working have broadcom... I wish it was something as easy as driver or hardware incompatibility but I think it is something with SMB since my linux os nas was visible before and now invisible at least to network discovery. 
    Friday, May 26, 2017 6:18 PM
  • Tried but this doesn't work for me on any of my home machines.
    Friday, May 26, 2017 6:19 PM
  • For what it's worth, this morning I turned on one computer and the server. Much to my surprise the Server with the Killer Ethernet adapter was recognized on the network! 

    But...when I turned on a second computer all that was recognized on the network by the second computer was the two computers with an Intel Ethernet adaptor. 

    Then just to prove a point I rebooted the first computer while the second computer was on along with the server with the Killer network adapter  The rebooted system no longer recognized the server - only the two systems with the Intel adapters.  This may explain why there are different issues being reported on this thread.

    Then I turned off both computers and left the server on.  This time when I booted the first computer that had recognized the server earlier - it no longer recognized the server with the Killer Ethernet adapter.

    Seems like networks discovery gets confused when there are multiple computers on the network with different Ethernet adapters and it can only handle reliably computers with the Intel Ethernet adapter (in my case) and/or Realtek Ethernet adapters as someone suggested above??

    We'll see what happens to network discovery tomorrow, maybe it has some day/time sensitive AI built in - just kidding.





    • Edited by Ken1440 Saturday, May 27, 2017 10:04 AM
    Saturday, May 27, 2017 9:41 AM
  • At this point it would be nice if Microsoft would acknowledge that there is a problem with WHQL drivers or the network discovery code/service in the Creator Update AND that they are working on a fix... might save ALL of us some time looking for an easy fix that clearly is not coming.
    Saturday, May 27, 2017 11:45 AM
  • "Can confirm. I rolled back two Creator's Edition PCs on my peer-to-peer network and made sure that one was master browser. My WDTV Live could then see and access the usual shares. When a 1703 machine is master browser, none of the other computers show up in the WDTV's "network shares".

    This is now quite repeatable behavior. Before turning on the WDTV Live, I have to start up a non-1703 unit and stop the computer browser on the 1703  (which has the media files). Then the WDTV works as expected.

    Network reset and the netsh commands mentioned in this thread had no effect.

    Friday, April 28, 2017 8:23 PM - Happy Lemming"

    This post is exactly right, at least in my case.

    If a 1703 system is the Master Browser NetBios will not function correctly. The workaround is to ensure a non-1703 system is Master Browser, either by booting it first onto the network or by forcing another device to assume Master Browser.

    I have a Netgear router that has a USB port, which I never used. But I plugged in a thumbdrive, which enabled network sharing. When I turned off all systems on the network the Netgear became the Master Browser, and will remain Master Browser - at least until a router reboot.

    Now other systems can be turned on/off and everything works like it is supposed to, and has for days.

    I'm not sure about all the sidetracks to adapter types, blocked ports, resetting services, etc. All I can say is that in my mix of 4 1703 systems, 1 1607 system, and 1 Windows 7 system that if a 1703 system is the first booted, becomes Master Browser, then the network is hosed. If the 1607 or Windows 7 system is booted first then all is fine.

    Scottie's LanScan is the easiest way to find out which device is the Master Browser. When 1703 is the Master Browser neither this app or Net View DOS command will execute on the other systems on the network, but will on the 1703 system.

    https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

    Clearly 1703 has broke NetBios somehow.



    Saturday, May 27, 2017 1:56 PM
  • The problem on my network is that machines cannot retrieve a list of servers from the master browser (error 8021 for the computer browser service).  This only happens when the master browser is a machine running the 64 bit version of 1703.  When the master browser is a machine running the 32 bit version of 1703, the list of servers is correctly received.  Another symptom of he problem is that running "net view" on the non-master browser machines gives a "service not running error" when the list of servers is not retrieved.

    The master browser 64 bit machine can always see all the other machines on the network (and "net view" works, too) while all the non-master browser machines can usually not even see themselves in a network view (although all the machines can ping each other by their ip addresses or their NetBios names).

    The problem looks to be with only the 64 bit version of 1703, at least on the Pro and Home versions running on my network.

    Saturday, May 27, 2017 7:56 PM
  • I just wasted a morning trying to get windows support to help.  Afetr buying an assure subscription they gave up and pointed me to business support.  I got a credit for support and then restored previous version and stopped feature updates.  Any share with user code and password fails as NOT AUTHORIZED- shares a guest are OK.

    Ron Kirschner

    Saturday, May 27, 2017 10:18 PM
  • Definitely a workaround...

    Plugged a USB drive into the port on my ASUS RT-AC5300 and set the firmware to make the USB drive the Master Browser... almost instantly all 1703 machines resolve net view and all network devices are displayed in Windows Explorer.

    Agree that 1703 broke Netbios/Master browser. 

    Sunday, May 28, 2017 4:53 AM
  • The problem on my network is that machines cannot retrieve a list of servers from the master browser (error 8021 for the computer browser service).  This only happens when the master browser is a machine running the 64 bit version of 1703.  When the master browser is a machine running the 32 bit version of 1703, the list of servers is correctly received.

    I'm now seeing this as well but apparently just started with build 15063.332.  Which build(s) are you running?

    For now I've used the registry on the 64-bit PC's and set the following string to value No

    HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList

    This appears to work by allowing only 32-bit PC's to be Master Browsers.  When there is no 32-bit PC online to serve as Master Browser, the 64-bit PC's can see each other via WSD discovery.
    Sunday, May 28, 2017 1:29 PM
  • "set the firmware to make the USB drive the Master Browser"

    How did you do that?  What firmware on what device?  I have a ASUS RT-AC66u and while I can enable the shared USB port I don't see any setting for determining the master browser.


    Woody - Windows 7 64-bit Redmond, WA

    Tuesday, May 30, 2017 11:14 PM
  • Funny thing is that I don't even have a "browser":


    ________________ drahnier

    Wednesday, May 31, 2017 12:44 AM
  •  don't even have a "browser"

    It's a Master Browser unless you have disabled it.

    Try using  nbtstat -N

    Interesting.  I had to use  nbtstat  -a <host name of Master browser>  to find that host and its name table.  I can't remember if I have disabled having a Master Browser on this W10 host.  It would have been before I got the CU, so that would mean the upgrade preserves that preference (or maybe now creates it by default?)   This host can be multi-homed which is why I would have done that.

    Why isn't W10 at least updating the cache when I do those things?  Even  nbtstat  -RR  isn't finding it.

    Oh.  I just saw John.B_'s point about 32-bit.  My Master Browser is my Surface RT.   ; )



    Robert Aldwinckle
    ---

    Wednesday, May 31, 2017 1:21 AM
  • I have seen this problem with the master browser on 64 bit Windows 10 machines (and not on 32 bit Win 10) since the public release of the Creator update.  It was a problem on version 10563.296 yesterday and version 10563.332 after today's update.  I did not run any of the insider versions of the Creator update.

    Wednesday, May 31, 2017 1:34 AM
  • For now I've used the registry on the 64-bit PC's and set the following string to value No

    HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList


     
    Mine is set to false.  Who's right?   <eg>

    https://support.microsoft.com/en-us/help/191611/symptoms-of-multihomed-browsers 

    <quotes>
    Note In Windows 2000, instead of the value false, use the value no.

    Last Review: Mar 15, 2008 - Revision: 1

    </quotes>



    Robert Aldwinckle
    ---

    Wednesday, May 31, 2017 3:11 AM
  • "set the firmware to make the USB drive the Master Browser"

    How did you do that?  What firmware on what device?  I have a ASUS RT-AC66u and while I can enable the shared USB port I don't see any setting for determining the master browser.


    Woody - Windows 7 64-bit Redmond, WA

    I'm running Asuswrt-Merlin firmware on my ASUS routers (RT-AC5300 and RT-AC3200) current version is 380.66-4 and is available for you router... this may not be an option in the base firmware.


    • Edited by chuckwi11 Wednesday, May 31, 2017 5:57 AM
    Wednesday, May 31, 2017 4:41 AM
  • If one of computers is 32 bit and others are 64 bit, turn all off and turn on 32 bit  and then the rest.  Then it will work as it did before. I guess it makes the 32 machine the master browser.
    Thursday, June 08, 2017 3:50 PM
  • This worked for me also. Running ASUS RT-68U router with AsusMerlin firmware. Forcing the router to be the Master Browser brought all the network devices back.
    Thursday, June 08, 2017 11:29 PM
  • The only thing that isn't resolved is networked printers... In Explorer I can see my NAS and Samba shares but using the Asus router as the master browser will not publish the printers.  The networked printers are there and can be printed to from MS Office, Adobe, etc but do not automagically appear in Windows Explorer. I'll be Investigating a workaround for this as well.
    • Proposed as answer by Justanothercog Saturday, June 10, 2017 3:14 PM
    • Unproposed as answer by Justanothercog Saturday, June 10, 2017 3:14 PM
    Friday, June 09, 2017 8:58 AM
  • I just installed the Creators Update 2 days ago on my laptop. After doing that, I noticed my RDP connection to that device stopped working. I went into my ASUS RT-AC88U router to check settings for the fixed IP address I assigned and noticed that the IP address on my laptop was different that what I told the router to assign to it a month ago. THEN I noticed that the MAC address for my wireless NIC on the PC was not what it was the week before! Creators Update changed the MAC address (which caused my router to assign it a new DHCP address since it saw a "new" PC connecting). 

    I suspect a lot of the issues people are having is due to this. You might trying changing the MAC address back to the original address and see if it corrects the problem (if in fact yours got changed). I was able to identify the old MAC address by going into my ASUS router LAN/DHCP Server settings. From there I started to create a new manually assigned IP address and selected "Show Offline Client List" to see the old connection instance. This displayed the original MAC address.....which did not match the current MAC address.

    Now why the heck would Microsoft change my wireless adapter MAC address??? This has only got to create huge issues for some folks like me. Anyway, everything now connects properly (shares, RDP, etc).

    ========================================================

    Update on above about an hour later:

    Aaahaaa!!! It's a "feature" ;-P  The creators update decided to turn on "Use Random hardware addresses" in the Network/WiFi settings. It was set in general for all WiFi networks. I turned that off and went into each "Manage known networks" Wifi network and also turned it off there as well. You can leave the General setting to "On" and turn it "Off" for specific networks only, as an option. That made my old MAC address return.

    I never turned that option on, but it's possible that one of the Creators Update install "questions" that I answered caused this to be set by the update (without telling me EXACTLY what the answer to their question would change on my PC.)

    • Edited by Justanothercog Saturday, June 10, 2017 5:59 PM Updated information
    Saturday, June 10, 2017 4:20 PM
  • Hello and thanks to everyone who has posted to this thread. For those who are having issues connecting to \\ComputerName\ShareName can you please post the results of these two PowerShell commands and give a summary of your scenario? This will us to investigate internally

    Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"

    and

    Get-SmbServerConfiguration

    Thanks!

    Warren


    Tuesday, June 13, 2017 7:37 PM
  • I'm the one whose WDTV player cannot see 64-bit Creator's Edition shared folders when that PC is master browser.

    PS C:\Users\lemmi_000> Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"


    EnableAuthenticateUserSharing : 0
    NullSessionPipes              : {}
    ServiceDll                    : C:\Windows\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    restrictnullsessaccess        : 1
    AdjustedNullSessionPipes      : 3
    EnableForcedLogoff            : 1
    EnableSecuritySignature       : 0
    LmAnnounce                    : 0
    RequireSecuritySignature      : 0
    Size                          : 1
    Guid                          : {23, 232, 50, 17...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry



    PS C:\Users\lemmi_000> Get-SmbServerConfiguration


    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : False
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True

    "ServerHidden" - hmm.

    Tuesday, June 13, 2017 9:53 PM
  • I have DELL Precision 5510 with Windows 10 64-bit Creator's Edition with issues connecting to \\ComputerName\ShareFolder . Below that you request

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. Tutti i diritti sono riservati.

    PS C:\Users\Enzo> Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"


    NullSessionPipes         : {}
    ServiceDll               : C:\WINDOWS\system32\srvsvc.dll
    ServiceDllUnloadOnStop   : 1
    restrictnullsessaccess   : 1
    AdjustedNullSessionPipes : 3
    EnableForcedLogoff       : 1
    EnableSecuritySignature  : 0
    RequireSecuritySignature : 0
    Guid                     : {55, 213, 98, 20...}
    PSPath                   : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lan
                               manServer\Parameters
    PSParentPath             : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lan
                               manServer
    PSChildName              : Parameters
    PSDrive                  : HKLM
    PSProvider               : Microsoft.PowerShell.Core\Registry

    PS C:\Users\Enzo> Get-SmbServerConfigurat


    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : False
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True

    Wednesday, June 14, 2017 7:35 AM
  • My WDTV also cannot see the shares on my 1703 x64 machine.

    Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"

    EnableAuthenticateUserSharing : 0
    NullSessionPipes              : {}
    ServiceDll                    : C:\WINDOWS\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    restrictnullsessaccess        : 1
    AdjustedNullSessionPipes      : 3
    EnableForcedLogoff            : 1
    EnableSecuritySignature       : 0
    RequireSecuritySignature      : 0
    Guid                          : {10, 19, 237, 4...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry

    Get-SmbServerConfiguration

    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : False
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True
    • Edited by Stollencrew Wednesday, June 14, 2017 2:51 PM
    Wednesday, June 14, 2017 2:47 PM
  • Unable to see network devices in explorer if a 1703 machine is the Master Browser.  Using a Samba device and forcing master browser resolves the network discovery.

    EnableAuthenticateUserSharing : 0

    NullSessionPipes              : {}
    ServiceDll                    : C:\Windows\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    autodisconnect                : 15
    enableforcedlogoff            : 1
    enablesecuritysignature       : 0
    requiresecuritysignature      : 0
    restrictnullsessaccess        : 1
    AdjustedNullSessionPipes      : 3
    Guid                          : {189, 23, 239, 86...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry

    Get-SmbServerConfiguration

    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : False
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True



    • Edited by chuckwi11 Wednesday, June 14, 2017 4:10 PM
    Wednesday, June 14, 2017 3:34 PM
  • I have Windows 10 Home 64-bit Creator 1703. The Onkyo receiver does not see a shared folders. Before the update everything worked fine. When you turn on your laptop with Windows 10 32-bit (1703) - shared folders on the network become visible.

    Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"

    NullSessionPipes         : {}

    ServiceDll               : C:\WINDOWS\system32\srvsvc.dll

    ServiceDllUnloadOnStop   : 1

    restrictnullsessaccess   : 1

    AdjustedNullSessionPipes : 3

    Guid                     : {131, 110, 142, 122...}

    PSPath                   : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

    PSParentPath             : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer

    PSChildName              : Parameters

    PSDrive                  : HKLM

    PSProvider               : Microsoft.PowerShell.Core\Registry

    Get-SmbServerConfiguration

    AnnounceComment                 :

    AnnounceServer                  : False

    AsynchronousCredits             : 64

    AuditSmb1Access                 : False

    AutoDisconnectTimeout           : 15

    AutoShareServer                 : True

    AutoShareWorkstation            : True

    CachedOpenLimit                 : 10

    DurableHandleV2TimeoutInSeconds : 180

    EnableAuthenticateUserSharing   : False

    EnableDownlevelTimewarp         : False

    EnableForcedLogoff              : True

    EnableLeasing                   : True

    EnableMultiChannel              : True

    EnableOplocks                   : True

    EnableSecuritySignature         : False

    EnableSMB1Protocol              : True

    EnableSMB2Protocol              : True

    EnableStrictNameChecking        : True

    EncryptData                     : False

    IrpStackSize                    : 15

    KeepAliveTime                   : 2

    MaxChannelPerSession            : 32

    MaxMpxCount                     : 50

    MaxSessionPerConnection         : 16384

    MaxThreadsPerQueue              : 20

    MaxWorkItems                    : 1

    NullSessionPipes                :

    NullSessionShares               :

    OplockBreakWait                 : 35

    PendingClientTimeoutInSeconds   : 120

    RejectUnencryptedAccess         : True

    RequireSecuritySignature        : False

    ServerHidden                    : True

    Smb2CreditsMax                  : 2048

    Smb2CreditsMin                  : 128

    SmbServerNameHardeningLevel     : 0

    TreatHostAsStableStorage        : False

    ValidateAliasNotCircular        : True

    ValidateShareScope              : True

    ValidateShareScopeNotAliased    : True

    ValidateTargetName              : True


    • Edited by Иgor Thursday, June 15, 2017 5:23 AM
    Wednesday, June 14, 2017 6:07 PM
  • I have 3 systems - 2 on 1703 and 1 on 1607. Shares work if 1607 is Master Browser, but does not work if either 1703 is. Using Netgear router as Master Browser to work around issue and it works fine.

    PS C:\WINDOWS\system32> PS C:\WINDOWS\system32>

    NullSessionPipes              : {}
    ServiceDll                    : C:\WINDOWS\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    restrictnullsessaccess        : 1
    AdjustedNullSessionPipes      : 3
    AutoShareWks                  : 1
    CachedOpenLimit               : 0
    EnableForcedLogoff            : 1
    EnableSecuritySignature       : 0
    LmAnnounce                    : 0
    RequireSecuritySignature      : 0
    Size                          : 1
    SrvComment                    : Dell Desktop
    EnableAuthenticateUserSharing : 1
    Guid                          : {104, 169, 153, 163...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry



    PS C:\WINDOWS\system32> PS C:\WINDOWS\system32> PS C:\WINDOWS\system32>

    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 0
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : True
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True


    Wednesday, June 14, 2017 9:32 PM
  • I reported this to MS the day CU was released - including the details about the master browser, the 64 bit info, the fact that if other Windows versions were the master browser it works - I'm so glad MS is quick to listen and act.
    Saturday, June 17, 2017 1:52 PM
  • I did the following to fix my file shares on a 1703 desktop:

    start -> run -> ncpa.cpl

    right click active network adapter -> properties -> uncheck "File and Printer Sharing for Microsoft Networks" -> OK

    right click active network adapter -> properties -> check "File and Printer Sharing for Microsoft Networks" - > OK



    File shares started working again. Also tested with a ios device using Remote File Manager and was able to browse 1703 desktop windows share.

    D



    That solved my sharing problem, but, I have to uninstall and install again “File and printer sharing”.

    After restart computer, I have lost sharing again.

    Monday, June 19, 2017 10:29 AM
  • I was finally able to solve the wins problem. On my network, only one machine was having this issue. None the the suggestion here worked for me. Turns out that almost all references to my network adapter were deleted from the registry. This is what worked for me:

    Under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\, you will see one or more Tcpip entries. To determine which Tcpip entry is referring to your network card, simply click on each one until you see one with DhcpNameServerList on the left with an ip address filled in. The long string of of letters and numbers in the {} by that key is what you are going to need. {your setting} will refer to that key. Basically, I just copied the keys already in the following and added {your setting} to each. 

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Linkage

    Bind -example

    Added:

    \Device\Tcpip_{your settings}
    \Device\Tcpip6_{your settings}
    \Device\NetBT_Tcpip_{your settings}
    \Device\NetBT_Tcpip6_{your settings}
    \Device\Smb_Tcpip_{your settings}
    \Device\Smb_Tcpip6_{your settings}

    Do the same, matching the settings of the key and adding {your setting} to Export and Route. Each key will be different so make sure you match what's already there. Also do this to Bind, Export and Route to the following:

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Linkage

    HKLM\SYSTEM\CurrentControlSet\Services\NetBIOS\Linkage

    HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Linkage

    Reboot the system.


    Chris K


    • Edited by ckoehler45 Tuesday, June 20, 2017 4:33 PM
    • Proposed as answer by ckoehler45 Tuesday, June 20, 2017 4:33 PM
    Tuesday, June 20, 2017 3:26 PM
  • I was finally able to solve the wins problem. On my network, only one machine was having this issue. None the the suggestion here worked for me. Turns out that almost all references to my network adapter were deleted from the registry. This is what worked for me:

    Under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\, you will see one or more Tcpip entries. To determine which Tcpip entry is referring to your network card, simply click on each one until you see one with DhcpNameServerList on the left with an ip address filled in. The long string of of letters and numbers in the {} by that key is what you are going to need. {your setting} will refer to that key. Basically, I just copied the keys already in the following and added {your setting} to each. 

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Linkage

    Bind -example

    Added:

    \Device\Tcpip_{your settings}
    \Device\Tcpip6_{your settings}
    \Device\NetBT_Tcpip_{your settings}
    \Device\NetBT_Tcpip6_{your settings}
    \Device\Smb_Tcpip_{your settings}
    \Device\Smb_Tcpip6_{your settings}

    Do the same, matching the settings of the key and adding {your setting} to Export and Route. Each key will be different so make sure you match what's already there. Also do this to Bind, Export and Route to the following:

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Linkage

    HKLM\SYSTEM\CurrentControlSet\Services\NetBIOS\Linkage

    HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Linkage

    Reboot the system.


    Chris K


    Weird...

    I have 6 Tcpip entries under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\ although NONE has DhcpNameServerList. All 6 have only 3 entries each which are:

    Default (Value not Set)
    NameServerList (No Value inside it. In Blank)
    NetBiosOptions (All with 0 Value)



    • Edited by JohnnyR2D2 Tuesday, June 20, 2017 6:59 PM
    Tuesday, June 20, 2017 6:58 PM
  • I have 6 Tcpip entries under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\ although NONE has DhcpNameServerList.
    Is it possible you don't use DHCP (e.g. Static IP)?
    Tuesday, June 20, 2017 7:12 PM
  • I have 6 Tcpip entries under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\ although NONE has DhcpNameServerList.

    Is it possible you don't use DHCP (e.g. Static IP)?

    You're right. In fact, the DHCP server is my Peplink Balance 20 and each one of my devices has an assigned IP in the DHCP Reservation Table. For example, this one is 192.168.1.2.

    Since I have also another Router (extender) with a USB drive attached I'm going to test the solution someone posted above and try let him be the Master Browser.

    Turned off all 4 computers in my Network, Reboot the Router, Wait. Turn on this computer and guess what? Didn't work. This stupid computer still can't see the others, although as mentioned by several in here I can find all the other computers by just typing their names in Explorer.

    Update: I just downloaded LANscan v1.68 and the Router USB attached drive is now the Master Browser and after reboot all the other computers I can now see them on my network again.






    • Edited by JohnnyR2D2 Tuesday, June 20, 2017 11:28 PM
    Tuesday, June 20, 2017 7:59 PM
  • I have been having an issue with 1 out of 3 Windows 10 pc's with the Creator update where as soon as the problem machine contacts the network my WD My World Book NAS becomes inaccessible, the network light on the router is constantly lit.  I noticed the problem PC was reporting driver errors for the device in Device Manager, no newer drivers are available so I disabled them, that did not appear to work.  I then noticed the BlueTooth & Other Devices had the NAS drive listed with Driver Error, after removing this entry and rebooting the NAS and the PC the issue, for now, has gone away.

    I also tried turning off the Master Browser option in the registry which did not appear to impact the issue, although I have left this turned off.

    Friday, June 23, 2017 6:14 PM
  • Thanks for your suggestion.

    Much grief avoided.

    Installed and working exactly as you describe.

    Fully share your pragmatism.

    Thanks again.

    Tuesday, June 27, 2017 12:58 AM
  • I did the following to fix my file shares on a 1703 desktop:

    start -> run -> ncpa.cpl

    right click active network adapter -> properties -> uncheck "File and Printer Sharing for Microsoft Networks" -> OK

    right click active network adapter -> properties -> check "File and Printer Sharing for Microsoft Networks" - > OK



    File shares started working again. Also tested with a ios device using Remote File Manager and was able to browse 1703 desktop windows share.

    D


    Hi. This one worked for me, thanks. My case might not be totally generic though.

    I have the Hyper-V in use and I removed and re-enabled the mentioned protocol on the virtual NIC called "vEthernet (External Virtual Switch)" which is Hyper-V Virtual Ethernet Adapter. 

    In the previous Windows (before the dreaded 1703 or Creator's Update) there also was a problem with the Hyper-V networking. Disabling and re-enabling the whole virtual adapter helped restoring the connectivity. On Windows 10 1703 this does no longer help restoring the shared folder accessibility. Cocking the "File and Printer Sharing for Microsoft Networks" protocol helped in my case. Thanks again.

    Wednesday, June 28, 2017 12:49 PM
  • I had the same problem and none of the suggestions helped.
    After installing the latest 2017-6 Cumulative Update KB4022716 the problem has gone! I am able to browse the shares on my network and all the workgroups are visible!

    For offline update:


    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4022716 


    • Edited by Varga T. Zsolt Thursday, June 29, 2017 5:53 AM
    • Proposed as answer by john.b_ Thursday, June 29, 2017 8:16 AM
    Thursday, June 29, 2017 5:51 AM
  • To me, the update KB4022716, did not help.
    Thursday, June 29, 2017 9:49 AM
  • To me, the update KB4022716, did not help.

    Can you confirm my understanding from your earlier post?  Do you have two PC's with Win10 1703 (one 64bit and one 32bit) and an Onkyo receiver?

    Are all PC's updated to build 15063.447?

    Thursday, June 29, 2017 11:19 AM
  • Yes. Can the parameters

    HKLM\System\CurrentControlSet\Services\Browser\Parameters

    be incorrectly set?
    Now works paired with a laptop (Win10 1703 32bit) only when on PC (Win10 1703 64bit):

    MaintainServerList - No; IsDomainMaster - No.

    on laptop (Win10 1703 32bit):

    MaintainServerList - Yes

    In other cases, there is no result.

    Thursday, June 29, 2017 1:03 PM
  • Now works paired with a laptop (Win10 1703 32bit) only when on PC (Win10 1703 64bit):

    MaintainServerList - No; IsDomainMaster - No.

    on laptop (Win10 1703 32bit):

    MaintainServerList - Yes

    In other cases, there is no result.

    Those settings are for Computer Browser service and SMB1 protocol which Microsoft will begin to turn off by default in the next version of Windows 10 coming this fall.

    I recommend you turn off SMB1 but, before you do, right-click on each computer/device you see under "Network" and select "Pin to Quick access."  Then, to turn off SMB1, click on "Programs and Features" in the Control Panel.  In the upper left corner of the programs list, click on "Turn Windows features on or off."  Scroll down the resulting list of features and un-check "SMB 1.0/CIFS File Sharing Support."  Follow the prompts including the required re-boot.  Do this for both your laptop and PC.

    Once SMB1 has been turned off you should be able to see both computers under "Network" but if not, you can also use the links you pinned to Quick Access.

    Try out this setup to make sure everything is working OK with SMB1 turned off.  You had previously mentioned an Onkyo receiver which could possibly be impacted if it requires SMB1 to share files with your PC's.  You can always turn SMB1 back on if you absolutely have to but it would be best to leave it off since we may soon have no choice but to live without it.

    Thursday, June 29, 2017 3:32 PM
  • Thank you, John.b_
    Now, after disabling SMB1, shared folders on the network have become available for computers. Now Digital Media Devices (receiver ONKYO) can not access files over the network? Only DLNA. This is bad, because DLNA does not read all the audio and video file formats, or it declines in quality. Or use additional programs - Media Server.

    • Edited by Иgor Friday, June 30, 2017 9:33 AM
    Thursday, June 29, 2017 6:23 PM
  • I am so glad I found this thread. I have been scouring the Internet trying to figure out what the hell was happening to my network. After trying a number obscure suggestions without resolution, after reading this thread I also think the Creators Update is the culprit.

    In my case, I had made a few changes, like changing ISPs (with a new cable modem/router) and adding a new Windows 10 machine to the LAN, but I was really surprised that the network was broken. The Internet works well. In fact I am really happy with the Internet speed as this ISP change is in fact an upgrade.

    I really started thinking it was a Windows problem when I put all the machines on a different router (without using the Internet connection) and I still experienced the problems everybody is talking about.

    I am now going to try update KB4022716 as I did not know about this until now.

    Sunday, July 02, 2017 2:26 AM
  • Update KB4022716 did not change anything. I can see all the computers in File Manager Network, but lose connection intermittently especially with my Mac Mini even though I have it assigned to a static IP address. Now I am having a login problem on my other Windows 10 desktop even though I am using the same Microsoft account on these 2 computers.
    Monday, July 03, 2017 3:05 AM
  • I have simply rolled back the Win 10 Creators update. And now my SMB shares work again. Tried a few of the fixes here and none of them worked. That's 3 hours I am never getting back..lol. 
    Tuesday, July 04, 2017 2:52 PM
  • So what is it going to take to get Microsoft's attention?   I did half the work for them - figured out where the issue was, pointed them in the direction.   Frankly I didn't find anything good about CU so it isn't that big of a deal but I wish they'd actually LISTEN when people tell them there is an issue and even point them to where the issue is.   I informed them of the issue as soon as CU was in pre-release.   Still haven't heard back from them.

    It would be one thing if I said something vague like it seems hinky.   I defined everything for them, I've done this on 3 MS OS releases and never heard back on any of them.


    • Edited by boe_d Tuesday, July 04, 2017 9:24 PM
    • Proposed as answer by trk633 Wednesday, July 05, 2017 12:01 AM
    • Unproposed as answer by trk633 Wednesday, July 05, 2017 12:01 AM
    Tuesday, July 04, 2017 9:23 PM
  • For what it's worth, I had share issues (Windows FTP server accessing a drive) as well as other machines on my network talking to my Creators Updated machine, and it turns out to be a conflict somehow with my Norton 360 firewall and the Creators update.  I disabled the Norton firewall and voila, everything I lost is now working.

    Hope this helps somehow.


    Wednesday, July 05, 2017 12:05 AM
  • I downloaded the 1703 3x by updating my PC, it froze uploading on my pc and I reloaded the previous version of Windows 10 1607.  An agent from Microsoft manually installed and changed a few things remotely on my computer with the same issue of it freezing and I had to unplug the pc so I could restart, but this time it would not reinstall the previous version.  I had to use a bootable usb and that did not work, so I had to use a backup of windows 8.1 and that got windows 10 to reload. There is a major problem with 1703 upgrade.  If I were you, go back to windows 1607 until Microsoft get the bugs out of the 1703 upgrade.
    Thursday, July 06, 2017 1:26 AM
  • To me, the update KB4022716, did not help.

    Running multiple Popcorn Hour media boxes and since Creators update cannot browse my shared folders.

    Very frustrating, latest update KB4022716 I thought had fixed the problem as my shared folders came back but have stopped appearing two days later again.

    Cannot roll back to pre-Creators update as stupidly cleared the old files to free up space.

    Increasingly frustrating!

    Thursday, July 06, 2017 7:56 AM
  •  shared folders came back but have stopped appearing two days later again.

    Any clues from those two PowerShell commands that Warren Williams requested?

    Also, where is your Master Browser?   See if  nbtstat  gives you any clues.



    Robert Aldwinckle
    ---

    Thursday, July 06, 2017 1:45 PM
  • Maybe I found solution.

    I reinstalled Creators update from CD media, said to download updates and to leave programs and data.

    Now I have shared folders.

    That is especially interested for people With Hyper-V adapter.

    Thursday, July 06, 2017 4:39 PM
  • I only have one PC on the network and is always the "master browser" and I check this with lanscan.

    In regards to the powershell commands I got this:

    PS C:\Users\steve> Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"



    NullSessionPipes              : {}
    ServiceDll                    : C:\WINDOWS\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    AdjustedNullSessionPipes      : 3
    EnableAuthenticateUserSharing : 1
    EnableForcedLogoff            : 1
    EnableSecuritySignature       : 0
    RequireSecuritySignature      : 0
    RestrictNullSessAccess        : 0
    srvcomment                    : MEDIA
    Guid                          : {64, 4, 250, 72...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry



    PS C:\Users\steve> Get-SmbServerConfiguration


    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : True
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True



    PS C:\Users\steve>

    Friday, July 07, 2017 7:27 AM
  • !THIS IS THE FIX!

    The Windows 10 1703 Update automatically turned the below setting to off. It just needs to be turned back on regardless of whatever other settings are using the old Windows GUI. This setting takes precedence:

    1. Click the 'Start Menu Button'.

    2. Click the 'Settings' cog/wheel.

    3. Click the 'Network & Internet' button.

    4. Click the 'Ethernet' option.

    5. Click the 'Network #' option that says 'Connected'

    6. On the 'Make this PC discoverable' option slide the option from 'Off' to 'On'.

    That is the reason that there are other methods to resolve this issue like replacing the network adapter. Because when you setup a new network connection you are able to setup sharing from scratch on that new adapter. That ticks this setting for it to be shared.

    Tuesday, July 11, 2017 8:12 PM
  • Mine is already set to make PC discoverable.  I cannot access shares from another machine after I restart the machine with the share.  

    My consistent workaround is on the computer I cannot access, go to network properties and un-check file and print sharing.  Hit ok.  Go back into properties, and check again.

    This has to be done after any reboot of the machine sharing the folder.

    Tuesday, July 11, 2017 11:26 PM
  • Just got an updated from Microsoft which by the way reboot my computer without even asking?

    Anyways, It's KB4025342 July 11, 2017—KB4025342 (OS Build 15063.483)

    I didn't test anything yet because I'm using the solution to have a driver as Master connected to the router meaning that I can see my other computers in the Network right now although regardless, in the list of fixes, there is no mention of this particular issue.

    I went to my Event Viewer just after the update installation and besides the entry about the update, there is another entry saying that a new service was installed at the same hour/minute of the update. Does anyone know what is it?

    A service was installed in the system.

    Service Name:  IOMap
    Service File Name:  C:\WINDOWS\system32\drivers\IOMap64.sys
    Service Type:  kernel mode driver
    Service Start Type:  demand start
    Service Account:   

    There is also a note at the bottom of the list of fixes saying "After installing the security updates for CVE-2017-8563, administrators need to set registry key LdapEnforceChannelBinding to enable the fix for the CVE. For more information about setting the registry key, see Microsoft Knowledge  Base article 4034879."

    Last but not least here is a list of improvements and fixes for the next major update which again doesn't mention anything about the issue in this thread. This update is named Windows 10 Fall Creators Update.

    Announcing Windows 10 Insider Preview Build 16237 for PC

    • Edited by JohnnyR2D2 Wednesday, July 12, 2017 1:27 PM
    Wednesday, July 12, 2017 2:29 AM
  • Back to the issue of the thread.

    I really can't remember so if someone can, will be great. If I'm not mistaken when we share a drive or folder in the Network besides any user that you want to add (I normally add Everyone) you have also SYSTEM, Administrators, User, etc. listed in the Share/Permissions and in the Security Tabs. After the update, all my shared drives/ folders have only Everyone listed.



    • Edited by JohnnyR2D2 Wednesday, July 12, 2017 2:29 PM
    Wednesday, July 12, 2017 2:24 PM
  • I am using the WDTVlive and was experiencing the inability to see my computers on my network after they were all updated to W10 CU 1703.  I installed the July 11 update (KB4025342) this morning and found that now I can see my network computers from the WDTV.  I was able to login and now have access to my shares, all seems back to normal.

    I appreciate Microsoft fixing this problem for me.  Hopefully this corrects the problem for others.

    Wednesday, July 12, 2017 8:13 PM
  • Well, I guess I spoke too soon.  Went to use the WDTV tonight and it's the same old problem of not being able to see the computer on the network.  I guess I'll be rolling 1703 back.

    • Edited by RMR57 Thursday, July 13, 2017 7:53 AM
    Thursday, July 13, 2017 7:51 AM
  • Well, I guess I spoke too soon.  Went to use the WDTV tonight and it's the same old problem of not being able to see the computer on the network.  I guess I'll be rolling 1703 back.

    Can't you have your WDTV as a MASTER? Having a Hard Drive plugged in my router and let him be the Master solved my problem...
    Thursday, July 13, 2017 1:35 PM
  • Well, I guess I spoke too soon.  Went to use the WDTV tonight and it's the same old problem of not being able to see the computer on the network.  I guess I'll be rolling 1703 back.

    Can't you have your WDTV as a MASTER? Having a Hard Drive plugged in my router and let him be the Master solved my problem...

    Right - the obvious solution is to use other products than MS to be the master browser in a windows network since MS can't get it right.   Give MS some time for goodness sake they are new to this whole network concept.
    • Edited by boe_d Thursday, July 13, 2017 2:58 PM
    Thursday, July 13, 2017 2:57 PM
  • Well, I guess I spoke too soon.  Went to use the WDTV tonight and it's the same old problem of not being able to see the computer on the network.  I guess I'll be rolling 1703 back.

    Update:

    I decided to uninstall KB4025342 to see if the WDTV could discover my computer again.  Sure enough, the computer showed up again on the WDTV.  I then reinstalled KB4025342 and the computer continues to show up.  I expect this to expire at some point however.

    Thursday, July 13, 2017 7:44 PM
  • Windows Creator is a SANDBOX VERSION OF WINDOWS NOT A OPERATING SYSTEM

    it is used for creating your OWN version of the WINDOWS OS like a custom programming tool this is why this happens DO NOT TRY AND USE THIS AS A OS



    OR a backdoor tool for trying to worm OK
    Thursday, July 13, 2017 7:53 PM
  • I, too, began to suffer from the Network Discovery / Master Browser bug after the Creator's Update. I searched and tried every remedy and suggestion. I even resurrected an old XP laptop to try to make it the Master Browser on the LAN. Nothing has worked.

    I am thoroughly disgusted with [expletive deleted] Micro$oft and Windoze 10.

    There is one work around by using this application : ipscan25.exe.
    http://www.advanced-ip-scanner.com/help/

    It scans your LAN and lists all computers.
    You can click on an entry and it will open it in the FILE EXPLORER.

    • Proposed as answer by Jetgraphics Friday, July 14, 2017 3:26 AM
    Friday, July 14, 2017 3:20 AM
  • Windows Creator is a SANDBOX VERSION OF WINDOWS NOT A OPERATING SYSTEM

    it is used for creating your OWN version of the WINDOWS OS like a custom programming tool this is why this happens DO NOT TRY AND USE THIS AS A OS



    OR a backdoor tool for trying to worm OK

    I haven't checked lately but about a month ago you had no choice if you downloaded the latest version of Windows to format a computer - it was the CU edition.
    Friday, July 14, 2017 5:09 PM
  • Well, I guess I spoke too soon.  Went to use the WDTV tonight and it's the same old problem of not being able to see the computer on the network.  I guess I'll be rolling 1703 back.

    Update:

    I decided to uninstall KB4025342 to see if the WDTV could discover my computer again.  Sure enough, the computer showed up again on the WDTV.  I then reinstalled KB4025342 and the computer continues to show up.  I expect this to expire at some point however.

    Update 2:  I decided to roll back to 1607 from 1703.  After a little cleanup, all is back to normal.  The WDTV network discovery function has been working correctly for the last day.

    I hope that I won't be forced to upgrade to 1703 before MS fixes this problem...that assumes it ever gets fixed.

    Friday, July 14, 2017 7:24 PM
  • Hi exactly the same problem everyone else is having here. I have a Win7 x64 and Win10x64 PC. About 2 months ago (April) things went Screwball with shared drives. I could see the Win10 drives from Win7, but not the other way around, unless the Win7 PC was COLD booted first and then Win10 booted.

    I posted it on win10forums along with some expletives.

    https://www.tenforums.com/network-sharing/88895-win10-pc-must-booted-before-win7-otherwise-network-drives-missing.html#post1080586

    ive lost 2 weeks worth of nites on this....after getting home from work and putting the kids to bed, researching and trying every damn thing until midnight. M$ this really is POOR POOR POOR.

    Win10 updated today (July15th). Hasnt fixed the prob. Tried everything on this thread (and others)...including the netsh stuff, forcing services lists to Auto, NetCfg –d command, 445 port open in firewall, toggling File Sharing settings in adapter and in Advanced lists, trying to force registry changes to MaintainServerList, etc the list goes on. Nothing fixes.

    Only joy i get is when i boot Win7 PC first, then Win10 second. Unfortunately for me, the Win10 PC normally stays always on in the past and the Win7 PC is only an occasional use. So this problem forces a lot of extra Win10 boots now which is very frustrating.

    THIS MUST BE FIXED ASAP

    • Edited by Blackout- Saturday, July 15, 2017 4:23 PM
    Saturday, July 15, 2017 2:35 PM
  • for what its worth...here ya go M$....

    EnableAuthenticateUserSharing : 0
    ServiceDll                    : C:\WINDOWS\system32\srvsvc.dll
    ServiceDllUnloadOnStop        : 1
    NullSessionPipes              : {}
    restrictnullsessaccess        : 1
    AdjustedNullSessionPipes      : 3
    EnableForcedLogoff            : 1
    EnableSecuritySignature       : 0
    RequireSecuritySignature      : 0
    Guid                          : {118, 166, 66, 105...}
    PSPath                        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer\Parameters
    PSParentPath                  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service
                                    s\LanmanServer
    PSChildName                   : Parameters
    PSDrive                       : HKLM
    PSProvider                    : Microsoft.PowerShell.Core\Registry

    AnnounceComment                 :
    AnnounceServer                  : False
    AsynchronousCredits             : 64
    AuditSmb1Access                 : False
    AutoDisconnectTimeout           : 15
    AutoShareServer                 : True
    AutoShareWorkstation            : True
    CachedOpenLimit                 : 10
    DurableHandleV2TimeoutInSeconds : 180
    EnableAuthenticateUserSharing   : False
    EnableDownlevelTimewarp         : False
    EnableForcedLogoff              : True
    EnableLeasing                   : True
    EnableMultiChannel              : True
    EnableOplocks                   : True
    EnableSecuritySignature         : False
    EnableSMB1Protocol              : True
    EnableSMB2Protocol              : True
    EnableStrictNameChecking        : True
    EncryptData                     : False
    IrpStackSize                    : 15
    KeepAliveTime                   : 2
    MaxChannelPerSession            : 32
    MaxMpxCount                     : 50
    MaxSessionPerConnection         : 16384
    MaxThreadsPerQueue              : 20
    MaxWorkItems                    : 1
    NullSessionPipes                :
    NullSessionShares               :
    OplockBreakWait                 : 35
    PendingClientTimeoutInSeconds   : 120
    RejectUnencryptedAccess         : True
    RequireSecuritySignature        : False
    ServerHidden                    : True
    Smb2CreditsMax                  : 2048
    Smb2CreditsMin                  : 128
    SmbServerNameHardeningLevel     : 0
    TreatHostAsStableStorage        : False
    ValidateAliasNotCircular        : True
    ValidateShareScope              : True
    ValidateShareScopeNotAliased    : True
    ValidateTargetName              : True

    Saturday, July 15, 2017 4:21 PM
  • EnableSMB1Protocol              : True

    I doubt you need to use SMB1 to see W7.



    Robert Aldwinckle
    ---

    Saturday, July 15, 2017 5:53 PM
  • EnableSMB1Protocol              : True

    I doubt you need to use SMB1 to see W7.



    Robert Aldwinckle
    ---


    hi Robert everyone on this thread has SMB1 protocol set as "True" in their reports also. I imagine this is a default setting?
    Saturday, July 15, 2017 10:16 PM
  • hi Robert everyone on this thread has SMB1 protocol set as "True" in their reports also. I imagine this is a default setting?

     
    Probably but the point is I doubt you need it to see your W7.  It is a more advanced OS than some of the ancient devices that people are having trouble supporting.

    Ref:

    https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/ 



    Robert Aldwinckle
    ---

    Sunday, July 16, 2017 12:20 AM
  •  

    Probably but the point is I doubt you need it to see your W7.  It is a more advanced OS than some of the ancient devices that people are having trouble supporting.

    Ref:



    Robert Aldwinckle
    ---

    thanks Robert i read the link...dont see the significance of it in this case but ok, ill play ball...

    SMB1 turned off for both PCs. Problem still stands.

    Sunday, July 16, 2017 4:04 PM
  • SMB1 turned off for both PCs. Problem still stands.

    Just want to re-confirm your original problem - W7 can see W10 shares but not vice versa unless W7 booted first.  Is this still the problem?

    If so, I assume when you say "see", you are not able to browse to the shares from File Explorer.  Can you access them by typing in their path (e.g. \\<IP address>\<share name>)?

    Also, boot W7 first so that you can see the shares from W10 and then pin them to Quick Access or add them to "This PC" (right click - "Add a network location").  Are you now able to access the shares regardless of boot order?

    Are both NIC's wired?  Is the W10 NIC from Intel?
    • Edited by john.b_ Sunday, July 16, 2017 6:11 PM
    Sunday, July 16, 2017 6:08 PM
  •  thanks Robert i read the link...dont see the significance of it in this case but ok, ill play ball... 

    I was thinking that if they didn't have SMB1 to fall back to that perhaps they would try harder with SMB2.   ; )

    So, echoing John's question, what exactly are your symptoms now?  Is there nothing that you can do to show that discovery has occurred?  E.g.  I would agree that  net view  still doesn't work the way we might like but  Win-E  Network  shows me my nodes.   Also, notice that File Explorer's Network node has a Details view which helps us analyze how the node was discovered.  (It would help if they would leave my Details Columns the way I left them! Even better if the Details pane would simply show all details whether the columns were specified or not!)  Anyway, now I see Discovery method WSD more consistently.



    Robert Aldwinckle
    ---

    Sunday, July 16, 2017 7:14 PM
  • Ditto here - tried everything and have wasted 4 full days so far with NO SOLUTION.

    I have three W10 Pro PCs – two on 1703 and one still on 1607 but none of them show anything when I run the LANScan utility… would this be because NetBios over TCPIP now always seems to be disabled in W10? (I have it switched on in each adapter but ipconfig /all shows it as disabled on each PC).

    I am having issues where the two 1703 PCs can access the shares on the 1607 one but not vice-versa. Each PC shows up in Explorer --> Network but only the 1607 one, and it's shares, can be accessed. The 1703 PCs can not be accesses from any of the 3 PCs. They are all in the same workgroup but when I do a network scan with a tool like Advanced IP Scanner it only shows the 1607 PC (and my QNAP NAS)  in the workgroup – the two 1703 PCs show nothing for workgroup even though they are definitely setup to be in the workgroup.

    I am no expert on any of this stuff but it seems that 1703 has completely borked (or disabled) NetBIOS and/or the master browser (not sure if they are related) and none of the fixes (including everything suggested in this thread) has worked.  Unfortunately I do not have a 32bit Win10 PC or a router with a USB port so for me it's either wind back to 1603 or pray MS fix this soon.

    BTW, my results from the PowerShell commands were identical on both 1603 and 1703 as everyone else above except that the 1703 PCs also have "AutoDisconnect: 4294967295" in the results of the first command.

    COME ON MS - WE NEED THIS SOLVED ***NOW!!!!!***

    Edit: I read elsewhere that this issue was not showing up on Reaktek GBE adapters but it was on Marvell Wifi and Killer/Atheros ethernet adapters (not sure about Intel). Now my 1607 PC has a Realtek adapter while my surface pro 4 (on 1703) has the Marvell adapter and my my other PC (a self-built tower also on 1703) has an Atheros AR8151 - and both have this issue, I wonder if there could be anything in this?  i.e: could it be a driver issue?

    • Edited by nzmike Monday, July 17, 2017 12:52 AM More info
    Monday, July 17, 2017 12:46 AM
  • SMB1 turned off for both PCs. Problem still stands.

    Just want to re-confirm your original problem - W7 can see W10 shares but not vice versa unless W7 booted first.  Is this still the problem?

    If so, I assume when you say "see", you are not able to browse to the shares from File Explorer.  Can you access them by typing in their path (e.g. \\<IP address>\<share name>)?

    Also, boot W7 first so that you can see the shares from W10 and then pin them to Quick Access or add them to "This PC" (right click - "Add a network location").  Are you now able to access the shares regardless of boot order?

    Are both NIC's wired?  Is the W10 NIC from Intel?

    Hi John and Robert...i thank you for your questions.

    "see"... i can see the drives listed in File Explorer (or Total Commander) but clicking on them causes lockup of explorer for around a minute and then "An Error Occurred...a network path was not found'.

    Re: Quick access, same problem.

    both NICs are wired. Cable tested. Both NICs from intel. Both PC MBs are under a year old. ive disabled every firewall setting. tried uninstalling Avast Security just in case it was interfering. ive got everybody sharing....Private and Public just to be sure...tried disabling IPv6 in both drivers just in case it was interfering....as i mentioned everything was working perfectly until some time in April

    Monday, July 17, 2017 4:43 AM
  • "see"... i can see the drives listed in File Explorer (or Total Commander) but clicking on them causes lockup of explorer for around a minute and then "An Error Occurred...a network path was not found'.

    This sounds like a credentials or permissions issue.  Is it a problem in both directions (10 to 7 and vice versa)?

    For the Win10 PC, under "Advanced Sharing," what are your file/printer and password protected sharing settings?

    Can you add the share under "This PC" (right click - "Add a network location").  This will automatically prompt for a Windows Credential if necessary.  Or you can manually add a Windows Credential in Control Panel.

    Monday, July 17, 2017 12:11 PM
  • I have similar issues running Windows 10-64 Pro on a Workgroup, where I can't access a NAS when signing in with my finger/Hello, but do have limited access when signing in using my User ID and Password.

    I want biometric security, and have spend hundreds of hours with Windows Home and Azure support.  No joy.

    I have figured out that issue is in Windows Credentials Manager, but have no idea how to correct, nor do local MS IT.  

    Really need help.

    Monday, July 17, 2017 1:34 PM
  • Ditto here - tried everything and have wasted 4 full days so far with NO SOLUTION.

    I have three W10 Pro PCs – two on 1703 and one still on 1607 but none of them show anything when I run the LANScan utility… would this be because NetBios over TCPIP now always seems to be disabled in W10? (I have it switched on in each adapter but ipconfig /all shows it as disabled on each PC).

    I am having issues where the two 1703 PCs can access the shares on the 1607 one but not vice-versa. Each PC shows up in Explorer --> Network but only the 1607 one, and it's shares, can be accessed. The 1703 PCs can not be accesses from any of the 3 PCs. They are all in the same workgroup but when I do a network scan with a tool like Advanced IP Scanner it only shows the 1607 PC (and my QNAP NAS)  in the workgroup – the two 1703 PCs show nothing for workgroup even though they are definitely setup to be in the workgroup.

    I am no expert on any of this stuff but it seems that 1703 has completely borked (or disabled) NetBIOS and/or the master browser (not sure if they are related) and none of the fixes (including everything suggested in this thread) has worked.  Unfortunately I do not have a 32bit Win10 PC or a router with a USB port so for me it's either wind back to 1603 or pray MS fix this soon.

    BTW, my results from the PowerShell commands were identical on both 1603 and 1703 as everyone else above except that the 1703 PCs also have "AutoDisconnect: 4294967295" in the results of the first command.

    COME ON MS - WE NEED THIS SOLVED ***NOW!!!!!***

    Edit: I read elsewhere that this issue was not showing up on Reaktek GBE adapters but it was on Marvell Wifi and Killer/Atheros ethernet adapters (not sure about Intel). Now my 1607 PC has a Realtek adapter while my surface pro 4 (on 1703) has the Marvell adapter and my my other PC (a self-built tower also on 1703) has an Atheros AR8151 - and both have this issue, I wonder if there could be anything in this?  i.e: could it be a driver issue?

    Interesting theory, I am using the Killer adapter and have the issue (my WDTV Live can't see my Win10 PC after Creators update). I have a secondary NIC (Intel), that I might try and see if that solves the issue.

    Can anyone else confirm?

    Monday, July 17, 2017 5:00 PM
  • For what it's worth -

    I have a small home network of four systems connected in a WORKGROUP.

    The four systems are: 1 desktop, 2 laptops, 1 tablet - networked via ethernet or wireless through a TP-Link adsl router.

    All the systems are upgraded to Windows 10, version 1703, build 15063.483, KB4025342.

    Each system has a 64-bit processor, but the tablet alone has a 32-bit OS.

    I can make the network behave as WORKGROUP sharing has always behaved since Windows for Workgroups was announced in the early 1990's, before Windows 95 - if, and only if, the conditions outlined below are fulfilled.

    SMB 1.0/CIFS must be set ON, for all systems, both 64-bit OS and 32-bit OS.

    The tablet, with 32-bit OS, must be powered on first.

    Other systems can be powered on in any sequence.

    Given these conditions, via its Network folder, any active system can see any other active system in the WORKGROUP, and access all shares anywhere.

    This is true even when I follow my usual practice of running a VPN on  each of my systems.

    However, for LANscanner 1.68 to work successfully, the VPN must be temporarily disconnected on each system. Given which, LANscanner runs successfully on any system, identifying each system in the WORKGROUP, with the Tablet further identified as MASTER.

    I realise that my case is not the same as all cases by any means - but it does at least suggest that there is a key difference, accidental or intentional, between the implementation of Creator Update in its 64-bit and 32-bit versions, which might be fruitful to explore.

    Tuesday, July 18, 2017 8:53 PM
  • Very true i spoke up before i did my HOMEWORK hey PEEPS i to had problems with the 1703 update and lost my whole machine Data and all

    and it stems from not having updated hardware that matches the newer 886 and 986 computers

    it has to do with the new BIOS firmware and the TRUST Software

    when you install windows 10 on an older computer you need all the Bios Usb Legacy stuff on hardware I/O Off etc

    with the new chip in the bios and all that trust stuff older PC's will have problems even if it's only a couple of years old

    Tuesday, July 18, 2017 9:12 PM
  • SMB 1.0/CIFS must be set ON, for all systems, both 64-bit OS and 32-bit OS.
    What happens if SMB 1.0/CIFS is turned OFF on all systems?  Granted you won't have NetBIOS based discovery but was curious whether, in its absence, WSD discovery would provide the same results.
    Tuesday, July 18, 2017 9:13 PM
  • SMB 1.0/CIFS must be set ON, for all systems, both 64-bit OS and 32-bit OS.

    What happens if SMB 1.0/CIFS is turned OFF on all systems?  Granted you won't have NetBIOS based discovery but was curious whether, in its absence, WSD discovery would provide the same results.

    First I should say I'm just a user, these days. I usually only use the folder sharing and advanced network settings, so beyond the obvious I've no idea what else they may affect.

    Even when SMB is ON for all systems, sharing only works traditionally if 32-bit OS tablet is Master. If not, sharing appears completely erratic, no pattern of recognition based on power-on sequence that I could discern.

    If 32-bit OS remains Master, other systems can be powered on and off at random, without disrupting comprehensive sharing.

    I saw a reference to SMB being insecure, so I switched it OFF for the 64-bit OS systems. Outcome for sharing was gibberish again, even with 32-bit OS, with SMB ON, as first in power-on sequence and nominal MASTER.

    When I tried to restore SMB ON for 64-bit OS under latest update, I couldn't do it in Control Panel, Programs and Features, Turn Windows Features on or off. The system let me select the box, but didn't register or obey the request.

    I had to use Settings, Network & Internet, Status, Network Reset - which, whatever else it did, restarted the machine with SMB ON. And the system participated perfectly in sharing once again.

    Hope this helps.

    Tuesday, July 18, 2017 10:18 PM
  • Ditto here - tried everything and have wasted 4 full days so far with NO SOLUTION.

    I have three W10 Pro PCs – two on 1703 and one still on 1607 but none of them show anything when I run the LANScan utility… would this be because NetBios over TCPIP now always seems to be disabled in W10? (I have it switched on in each adapter but ipconfig /all shows it as disabled on each PC).

    I am having issues where the two 1703 PCs can access the shares on the 1607 one but not vice-versa. Each PC shows up in Explorer --> Network but only the 1607 one, and it's shares, can be accessed. The 1703 PCs can not be accesses from any of the 3 PCs. They are all in the same workgroup but when I do a network scan with a tool like Advanced IP Scanner it only shows the 1607 PC (and my QNAP NAS)  in the workgroup – the two 1703 PCs show nothing for workgroup even though they are definitely setup to be in the workgroup.

    I am no expert on any of this stuff but it seems that 1703 has completely borked (or disabled) NetBIOS and/or the master browser (not sure if they are related) and none of the fixes (including everything suggested in this thread) has worked.  Unfortunately I do not have a 32bit Win10 PC or a router with a USB port so for me it's either wind back to 1603 or pray MS fix this soon.

    BTW, my results from the PowerShell commands were identical on both 1603 and 1703 as everyone else above except that the 1703 PCs also have "AutoDisconnect: 4294967295" in the results of the first command.

    COME ON MS - WE NEED THIS SOLVED ***NOW!!!!!***

    Edit: I read elsewhere that this issue was not showing up on Reaktek GBE adapters but it was on Marvell Wifi and Killer/Atheros ethernet adapters (not sure about Intel). Now my 1607 PC has a Realtek adapter while my surface pro 4 (on 1703) has the Marvell adapter and my my other PC (a self-built tower also on 1703) has an Atheros AR8151 - and both have this issue, I wonder if there could be anything in this?  i.e: could it be a driver issue?

    Interesting theory, I am using the Killer adapter and have the issue (my WDTV Live can't see my Win10 PC after Creators update). I have a secondary NIC (Intel), that I might try and see if that solves the issue.

    Can anyone else confirm?

    I can confirm Windows CU x64 master browser does not work properly with a realtek or intel nic.  You'll need another computer running a good OS so it can be the master browser.
    Wednesday, July 19, 2017 4:40 AM
  • Thanks for confirming - looks like it has nothing to do with the adapter then.

    So I guess we just have to wait for MS to issue a fix because I give up - have wasted days and days on this bullsh*t.  I actually have a load of updates ready to go now on my main PC (KB4025342) so who knows, maybe this will fix it - but I'm not holding my breath.

    Wednesday, July 19, 2017 8:48 AM
  • "see"... i can see the drives listed in File Explorer (or Total Commander) but clicking on them causes lockup of explorer for around a minute and then "An Error Occurred...a network path was not found'.

    This sounds like a credentials or permissions issue.  Is it a problem in both directions (10 to 7 and vice versa)?

    For the Win10 PC, under "Advanced Sharing," what are your file/printer and password protected sharing settings?

    Can you add the share under "This PC" (right click - "Add a network location").  This will automatically prompt for a Windows Credential if necessary.  Or you can manually add a Windows Credential in Control Panel.

    I thank you for you suggestion. Unfortunately, i am not a moron. As i said, i have spent over 2 weeks worth of nights until 2am after work on this. Obviously this would be the first thing i would look at. Ive toggled every setting just to be sure. Ive listed some of the things ive checked/tried and sharing is one of the first of course. As ive said before, everything was working (sharing) fine, then all hell broke loose around April, exactly the same time as everyone else. And as i stated its a problem in one direction only.

    i actually wish very much it was something as simple as a sharing setting.

    Wednesday, July 19, 2017 9:16 AM
  • for me when i turn of SMB1,  then ALL drive sharing between PCs comes to a crashing halt. Cant share in either direction, regardless of boot order. "Computer Browser" service disappears from the services list, the location "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\" disappears from the registry upon reboot, removing the "PARAMETERS" rung and thus removing the option setting of "MaintainServerList" from it as well.

    basically, things get worse, not better.

    Wednesday, July 19, 2017 9:52 AM
  • "Computer Browser" service disappears from the services list

    Do you have a bowser?  FWIW I just used  Get-Service  *owser   in PowerShell  to check mine, thinking that I might see both Computer Browser and bowser  but only  Computer Browser  is shown that way.  It is running on the W8.1 RT machine which thinks it is the Master Browser (even though SMB1 is off?) and stopped on W10 where I have always had MaintainServerList False.  On both machines  bowser is running.  Both have discovered each other via WSD.  Strangely the RT does not list itself in its Win-E Network display.  But each can see the other's files so that is all that I care about.


    Robert Aldwinckle
    ---

    Wednesday, July 19, 2017 11:12 AM
  • Add me to the list.

    I have an OPPO-203 Player that I used on a daily basis to listen to music through SMB.

    One evening I went to do the same, my PC had updated and it hasn't worked ever since. I'm done trying to fix this. I've tried everything and I just formatted my PC and installed everything thinking it was an issue with my PC but no!.

    Now I read about rolling back to 1607 but I'm not doing that. 

    I just updated to Kb4025342 but it didn't fix anything.

    MICROSOFT PLEASE FIX THIS!!!

    Thursday, July 20, 2017 4:26 AM
  • Thanks for confirming - looks like it has nothing to do with the adapter then.

    So I guess we just have to wait for MS to issue a fix because I give up - have wasted days and days on this bullsh*t.  I actually have a load of updates ready to go now on my main PC (KB4025342) so who knows, maybe this will fix it - but I'm not holding my breath.

    Don't hold your breath.

    It doesn't fix it. I just tried that. Still can't see my files on my OPPO. 

    Thursday, July 20, 2017 4:27 AM
  • I confirm that this bad behaviour is exactly the same as in autumn 2015 with 1511 update, which was repaired in March, 2016
    Thursday, July 20, 2017 2:31 PM
  • I confirm that this bad behaviour is exactly the same as in autumn 2015 with 1511 update, which was repaired in March, 2016.

    In 1703 system the Master Browser NetBios is again not functioning correctly.
    The workaround is to ensure a non-1703 system is Master Browser, but if you have already all systems updated to 1703, no solution until now. Still waiting for Microsoft move.

    Thursday, July 20, 2017 2:41 PM
  • I confirm that this bad behaviour is exactly the same as in autumn 2015 with 1511 update, which was repaired in March, 2016.

    In 1703 system the Master Browser NetBios is again not functioning correctly.
    The workaround is to ensure a non-1703 system is Master Browser, but if you have already all systems updated to 1703, no solution until now. Still waiting for Microsoft move.

    I have an old Win 7 laptop. Can I set that as Master Browser? How would I do that? The PC where I have all the files I want to listen on my OPPO has Win 10 CU.  I don't know if that affects anything. 
    Thursday, July 20, 2017 3:20 PM
  • if you have already all systems updated to 1703

    Try disabling SMB1?  (Leave SMB2 if necessary but who knows maybe it isn't needed either.)


    Robert Aldwinckle
    ---

    Thursday, July 20, 2017 3:49 PM
  • I confirm that this bad behaviour is exactly the same as in autumn 2015 with 1511 update, which was repaired in March, 2016.

    In 1703 system the Master Browser NetBios is again not functioning correctly.
    The workaround is to ensure a non-1703 system is Master Browser, but if you have already all systems updated to 1703, no solution until now. Still waiting for Microsoft move.

    I have an old Win 7 laptop. Can I set that as Master Browser? How would I do that? The PC where I have all the files I want to listen on my OPPO has Win 10 CU.  I don't know if that affects anything. 
    Turn off all the computers and turn the one you want to be the Master Browser first and wait for a bit before turn the others on. The problem is that you will have to do that all the time to keep him as Master. Doesn't your router have a USB port so you can plug a hard drive on it?
    Thursday, July 20, 2017 10:15 PM
  • thanks for sharing, this solved my problem. For testing I disabled File and Printer Sharing in 1703 and after reactivate I couldn access via telnet 445 or admin shares. Now same procedure again, disabling and reactivating it works:). Thanks and best regards, Marcus
    Friday, July 21, 2017 12:56 PM
  • "Computer Browser" service disappears from the services list

    Do you have a bowser?  FWIW I just used  Get-Service  *owser   in PowerShell  to check mine, thinking that I might see both Computer Browser and bowser  but only  Computer Browser  is shown that way.  It is running on the W8.1 RT machine which thinks it is the Master Browser (even though SMB1 is off?) and stopped on W10 where I have always had MaintainServerList False.  On both machines  bowser is running.  Both have discovered each other via WSD.  Strangely the RT does not list itself in its Win-E Network display.  But each can see the other's files so that is all that I care about.


    Robert Aldwinckle
    ---

    hi Robert, interestingly yes, there is a "bowser" in both machines, but there is also a "Browser" in both machines if i leave SMB1 on. If i turn SMB1 off, "Browser" disappears from the registry and only "bowser" remains. However there are no Parameters or "MaintainServerList" setting in "bowser". not a lot of anything interesting except a pointer to "bowser.sys". I dont believe it is directly related. I believe bowser is a reference to the bozo programmer who screwed up the file sharing.

    BTW i dont believe that "FALSE" is the right setting for MaintainBrowserList...it is "No".

    https://technet.microsoft.com/en-us/library/cc959923.aspx

    so your setting of "False" would not have been doing anything....


    • Edited by Blackout- Saturday, July 22, 2017 3:59 AM
    Saturday, July 22, 2017 3:58 AM
  • so your setting of "False" would not have been doing anything....


    It is definitely doing something.   nbtstat  -N  only shows the Master Browser on the other machine.

    Maybe your "No" is doing more than you would like?   <eg>

    BTW I tried turning off SMB2 too and it looks like that one is necessary.  What's strange then though is that discovery still occurs,  e.g.  WSD is still the Discovery method but then I can't get a connection.  However, I also discovered that for some reason W10 created a new Public port for Wireless video after I disabled SMB2 (coincidence?) and that caused me some confusion until I found it and set it to Private, so I'm not considering my results conclusive.

    Windows 10.  Still an Adventure ("Twisty passages, all different.")



    Robert Aldwinckle
    ---

    Saturday, July 22, 2017 7:35 AM
  • This free utility made me no longer care about this absurd problem: http://www.advanced-ip-scanner.com/

    It doesn't "fix" what is broken in Windows network browsing, but it completely replaces the lost functionality with a superior capability, and it is unequivocally free.

    This worked for me. Thanks
    Sunday, July 23, 2017 8:01 PM
  • Wonder if this has something to do with the problem in this thread.

    https://blogs.technet.microsoft.com/askpfeplat/2017/06/13/why-are-we-deprecating-network-performance-features-kb4014193/

    More here

    https://mspoweruser.com/goodbye-outlook-express-farewell-paint-what-windows-10-fall-creators-update-is-killing/


    Monday, July 24, 2017 12:59 AM
  • so your setting of "False" would not have been doing anything....


    It is definitely doing something.   nbtstat  -N  only shows the Master Browser on the other machine.

    Maybe your "No" is doing more than you would like?   <eg>

    BTW I tried turning off SMB2 too and it looks like that one is necessary.  What's strange then though is that discovery still occurs,  e.g.  WSD is still the Discovery method but then I can't get a connection.  However, I also discovered that for some reason W10 created a new Public port for Wireless video after I disabled SMB2 (coincidence?) and that caused me some confusion until I found it and set it to Private, so I'm not considering my results conclusive.

    Windows 10.  Still an Adventure ("Twisty passages, all different.")



    Robert Aldwinckle
    ---

    Robert it was never suggested to turn off SMB2. it was SMB1 that was suggested.
    Monday, July 24, 2017 11:16 AM
  • Wonder if this has something to do with the problem in this thread....

    had a read of both threads....im sure our problem does have something to do with the changes. However id say that it was not a plan to kill network drive sharing in thousands of offices throughout the world. Id say as part of their tinkering here they accidentally did some damage to the Computer Browser service. Or maybe some programmer made the Creator installation with the older damaged Computer Browser service from a year ago. Because its the exact same problem that they made a year ago to the same service that they then subsequently fixed, that is back again.

    Which makes me think, is it possible to grab just the single service (Computer Browser) from the older 1607 installation and replace the faulty Computer Browser service that came with 1703? does anyone know how to do that? might be a solution ?

    • Edited by Blackout- Monday, July 24, 2017 11:28 AM
    Monday, July 24, 2017 11:27 AM
  • This solution works for the WD TV LIVE, except do not restart the PC contrary to steps described as it does not survive a reboot

    It should be done while the orange discovery circle is spinning in WD TV LIVE

    https://community.wd.com/t/finaly-solution-for-wdtv-not-detected-in-windows-sharing/208104



    Monday, July 24, 2017 6:36 PM
  • Presto00 That's very interesting.

    When I did that my PC did show up on my OPPO-203 with the little SMB Icon. However when I try to login it asks me for my Username and Password but it won't logon. I changed the password / removed it, nothing.

    My old Win 7 Laptop can now see this PC but can't connect to it. 


    So this fix only works I guess, on the surface. 

    Tuesday, July 25, 2017 3:54 AM
  • Hey boe_d

    Today I was recommended this by the OPPO team http://www.oppodigital.com/KnowledgeBase.aspx?KBID=4&ProdID=UDP-203

    That oShare software is as close as it gets to the SMB function. It plays everything, grabs any subtitles, plays Remuxes with Atmos (if you need that) and its also super simple.

    Try it and let me know. At least it saved me the money of buying a new portable hard drive. 

    Tuesday, July 25, 2017 5:56 PM
  • Hello,

    I used to use oshare ages ago but stopped and don't recall why.   I know it wasn't bad but something about smb was better - too long ago to recall.   I guess the question is do we all just say - OH WELL MS F'd up again we'll just try to work around the fact they can't get networking right?    Shouldn't we be upset MS isn't listening or at least replying?   I'd be fine if they said we are working on it and made me wait for months but the silence is deafening.

    Wednesday, July 26, 2017 1:55 AM
  • Derek Ziemba wrote:
    "Specifically I can't access the machine using ES File Explorer on Android after the update.  I use this to stream videos between the PC and the Android. ES File Explorer is now asking for login credentials when I tap my PC. No credentials are valid.  Previously no credentials were even required because I have the network shares set to "Everyone". "

    I am having this problem as well, on Solid Explorer, getting authentication errors (where no authentication should be, or was previously, needed) since the creator update, and no way to browse or stream from PC over WLAN on my Android device. Can someone explain to me the 'temporary fix' Derek posted, or suggest another way to resolve this?
    Friday, July 28, 2017 3:42 AM
  • I may have a fix for those having trouble connecting to a W10 1703 PC from a non-windows device.

    I was having an issue whereby I was being told I had an incorrect username/password when trying to connect to a share on my PC from my Nvidia Shield (Andorid TV).

    After hours of trying various things, I found out that the Shield only supports SMB1. Turns out the version of Win10 I'm running on the PC (Win10 1703, Build 16241.1001) not only has SMB1 disabled, but the service isn't even installed.  Installing SMB12 and enabling it fixed the problem immediately.

    If you want to try this fix, here are the steps:

    1. Win+R (Run), type "optionalfeatures" and hit enter to bring up "Turn Windows features on or off".
    2. Scroll down to and expand "SMB 1.0/CIFS File Sharing Support" and check "SMB 1.0/CIFS Server" (Client was already checked for me) and hit OK.
    3. Launch Powershell as administrator.
    4. Type "Set-SmbServerConfiguration -EnableSMB1Protocol $true" and hit enter.
    5. I rebooted at this point, not sure if that's necessary but it can't hurt.

    I Hope this helps someone for now (apparently SMB1 is being removed completely from 1709, I just hope Nvidia/Google update the Shield/Android TV before then). 





    • Edited by RChesterton Sunday, July 30, 2017 10:37 AM
    • Proposed as answer by RChesterton Friday, August 04, 2017 8:45 PM
    Sunday, July 30, 2017 10:31 AM
  • Type "Set-SmbServerConfiguration -EnableSMB1Protocol $true" and hit enter. 

    Have you tested to see if it is not sufficient to have just  SMB2 enabled?

    Otherwise note that your product is not listed in the "still needs SMB1" page



    Robert Aldwinckle
    ---

    Sunday, July 30, 2017 11:23 AM
  • SMB2 was already installed and enabled. The Nvidia shield definitely requires SMB1
    Sunday, July 30, 2017 12:30 PM
  • nbtstat -RR on the offending machines solved it for me.  Granted though - I could reach my NAS devices with \\[IP address] even though I could not resolve to the share name in explorer.  Thanks for the hint that got me to a working solution.
    Wednesday, August 02, 2017 2:26 PM
  • Had same issue. I thought it was something I did but alas it was the Creator's Update. After it updated our Windows 10 Home PC, we could no longer connect to any network shares on it. I tried various solutions in this thread but none worked. Just rolled back and everything is fine again :(

    Eventually that PC will get creator's update and I won't be able to stop it. I hope there's a definitive solution soon.

    Friday, August 04, 2017 11:54 AM
  • Wow! Still no solution yet?
    Saturday, August 05, 2017 5:02 AM
  • this rubbish must have knocked out hundreds (if not thousands) of office network shares around the world...IT must be screaming everywhere how is this not fixed yet?
    Saturday, August 05, 2017 11:11 AM
  • Yet another system struck by the 1703 Network Discovery bug (and this HAS to be a bug, whether MS acknowledge it or not).

    Updated to 1703 (actually did a clean reinstall) and shazam, I can't browse my home network - Win10-64 machine, MacMini running Sierra, 32-bit machine running Linux Mint and a couple of Netgear NAS boxen.

    So quite familiar with SMB/CIFS on various platforms.

    Tried all the tricks in the preceding posts, this and that and the other - no joy.

    Then I remembered that the oldest NAS box could be set to be a WINS server - switched that on and hey presto, Network Browsing is back!  LANscan now shows everything, with the old NAS box as WINS Master.   If I disconnect it from the network everything disappears again.

    Evidently MS did something to bork this in 1703 and isn't telling.  Curiously, nbstat -n and -c shows no names in the Win 10 cache, but nbstat -r tells me that 5 names are Registered by Broadcast and 0 Reolved by Name Server and then

    NetBIOS Names Resolved By Broadcast
    ---------------------------------------------
               䙏乆十䈭ⴸㅄ〭‰䙏乆十䈭ⴸㅄ〭‰
               䙏乆十䈭ⴸㅄ〭‰䙏乆十䈭ⴸㅄ〭0
               OFFNAS-B8-D1-00<00>
               NAS-BE-C9-23   <00>
               LINUX-GAIM     <00>
               䙏乆十䈭ⴸㅄ〭‰乁剄坅ⵓ䥁偒剏T
               ANDREWS-AIRPORT<00>
                       䙏乆十䈭ⴸㅄ〭‰

    Yep, it looks like that, though the Chinese looking characters are replaced mostly by a little "?" in a box.

    So as long as my little NAS stays on the Network I'm OK.   I also installed the full Bonjour suite from Apple (not just the print thing) but I'm not sure whether that is contributing much.

    Time to 'fess up MS, pull your socks up and FIX THIS!

    The Cutter

    Saturday, August 05, 2017 1:23 PM
  • Hmmm. I've rolled the PC in question back from Creator's Update now but I did have a quick look and found that the master browser on our small network was our Windows 7 PC, according to NBTSTAT. Although it's possible I didn't concentrate enough but i did see MSBROWSE in it's list. 
    Saturday, August 05, 2017 5:19 PM
  • Well, if it is down to Master Browser being the chief reason, then it's highly possible that most have not come across the issue yet, especially as most larger organizations are not even on WIndows 10, and if they are they are unlikely to be near Creator's Update yet.
    Saturday, August 05, 2017 5:21 PM
  • I may have a fix for those having trouble connecting to a W10 1703 PC from a non-windows device.

    I was having an issue whereby I was being told I had an incorrect username/password when trying to connect to a share on my PC from my Nvidia Shield (Andorid TV).

    After hours of trying various things, I found out that the Shield only supports SMB1. Turns out the version of Win10 I'm running on the PC (Win10 1703, Build 16241.1001) not only has SMB1 disabled, but the service isn't even installed.  Installing SMB12 and enabling it fixed the problem immediately.

    If you want to try this fix, here are the steps:

    1. Win+R (Run), type "optionalfeatures" and hit enter to bring up "Turn Windows features on or off".
    2. Scroll down to and expand "SMB 1.0/CIFS File Sharing Support" and check "SMB 1.0/CIFS Server" (Client was already checked for me) and hit OK.
    3. Launch Powershell as administrator.
    4. Type "Set-SmbServerConfiguration -EnableSMB1Protocol $true" and hit enter.
    5. I rebooted at this point, not sure if that's necessary but it can't hurt.

    I Hope this helps someone for now (apparently SMB1 is being removed completely from 1709, I just hope Nvidia/Google update the Shield/Android TV before then). 





    YESSSS!!!!!!!! BRAVO RChesterton

    I have been running several non Windows devices thru my home network for several years,WDTV live & ROKU soundbridge's. As stated in this thread the 1703 upgrade disabled the network sharing. I also have spent several hours trying to correct this MS error including several regressions to the 1607 version.

    THIS SOLUTION TOTALLY WORKS FOR THE NON WINDOW DEVICES

    A restart is required

    Come on MS issue this as one of your upgrades


    • Edited by Royallaser Sunday, August 06, 2017 2:56 PM
    Sunday, August 06, 2017 2:53 PM
  • The SMB1 protocol is old & insecure and deprecated by MS themselves.

    Reinstating it may have solved your problem but THE problem - the inability to browse the Network in 1703 remains.

    Doesn't any one in the MS teams read these forums?  It doesn't look like it!

    Mac

    Tuesday, August 08, 2017 7:17 AM
  • Question