Sharing not working correctly after fall creators update


  1. Posts : 42
    Windows 10 Pro x64
       #1

    Sharing not working correctly after fall creators update


    I have three Win10 machines in the same workgroup, all with shared folders that the other machines can access. Previously this has been working fine. Two of the machines have just been updated with the fall creators update. What I now find is:


    1. From Network in Windows Explorer on either of the updated machines, I can still see the machine that hasn't been updated and and see the folders on that machine.
    2. Neither of the updated machines can see the other updated machine when I click on Network in Windows Explorer. Only the machine that hasn't been updated appears there. On the machine that hasn't been updated, all I see under Network in Windows Explorer is that machine - neither of the updated machines appear.
    3. If, in Windows Explorer on either updated machine I enter \\<other-updated-machine> in the current path field, then all the shares on the other machine are now visible and can be accessed. If I go one level back up to Network, the machine and shared folders disappear again.


    Anyone else seen this sort of behaviour, or have an idea on how to fix it?
      My Computer


  2. Posts : 147
    Dual boot windows 10 Pro 22H2 & Win 11 Pro 23H2
       #2

    Nick,
    My network settings had been changed by the update too.
    Control Panel > Network & Sharing Centre > Change Advanced Sharing Settings > Turn on Network Discovery (in Private & Public) and turn off password protected sharing under All Networks.
    Also, in Windows Media Player, in the stream section, I had to turn on sharing.
      My Computer


  3. Posts : 7
    Windows 10 Pro
       #3

    I have the same issue after Creators Fall update install. My PC is not accessible if I try to browse it from another PC by like this \\<PC Name>, but I can access it by browsing by IP. Before update browsing by name worked perfectly.
      My Computer


  4. Posts : 40
    Win 10
       #4

    I have the same issue after Creators Fall update install. Back to version 1703 Build 15063.674 all network issue's are gone.
      My Computer


  5. Posts : 42
    Windows 10 Pro x64
    Thread Starter
       #5

    Found a long thread about this problem at https://social.technet.microsoft.com...eators-edition which has a couple of posts from MSFT employees acknowledging that there's a problem.
    I had a poke around in the registry, and found that the Browser service key name in the registry is misspelled as bowser, and browser.sys in C:\Windows\System32\drivers is also misspelled as bowser.sys. Mind you, when I check in C:\Windows.old\WINDOWS\System32\drivers for the previous version, it's also bowser.sys there. Will wait to see what MSFT come back with.
    Sharing not working correctly after fall creators update-bowser.jpg
      My Computer


  6. Posts : 856
    Windows 10 Pro 21H2 build 19045.2193 Dual Boot Linux Mint
       #6

    Only lost one PC out of three, however Network Reset and a reboot sorted it here.
      My Computers


  7. Posts : 1
    Windows 10
       #7

    Having the same trouble. Some computers on our network can be seen but every day another connection disappears with no way to get them back. I've tried Network Reset, changing settings, and every other trick people are posting with no results.
      My Computer


  8. Posts : 1,471
    Win10 Home x64 - 1809
       #8

    Hey NickJP,
    In the reg key you reference, bowser is NOT mis-spelled ... bowser and browser are NOT the same thing. In FCU (1709), SMBv1 is not installed on a clean install of FCU and MS also added a scheduled task to remove SMBv1 (server and client) and since Computer Browser (browser) is tied to SMBv1 it would be removed as well.

    https://support.microsoft.com/en-us/...r-version-1709
      My Computers


  9. Posts : 323
    Windows 10 (2), Win 8.1 (1), Win 7 (1)
       #9

    This has been a known issue since the original Creators Update in the Spring as the link to a TechNet thread by NickJP above has indicated. There is no reliable fix for this. Some have been able to set up their router as the "master browser" thus correcting the problem for them. This problem popped up originally in v1511, but was fixed a few months later. Now it has been resurrected in v1703 and continues in v1709. It is part of the SMBv1 sharing protocol as Eagle51 has indicated. This protocol will be going away in the future. I have been able to access other PCs using their UNC name (\\<computer_name>) in File Explorer's Network address bar. I removed SMBv1 from my systems but that caused me to lose access to my NAS. I was able to change the sharing protocol on the NAS to SMBv2.1, which apparently defaulted to SMBv1, and I was again able to see it. Whether Microsoft will address this problem is unknown. They are aware of it.

    JohnD
      My Computer


  10. Posts : 40
    Win 10
       #10

    Adriaan Jansens said:
    I have the same issue after Creators Fall update install. Back to version 1703 Build 15063.674 all network issue's are gone.

    Very strange my network computers are now accessible,sharing is now working, the problems are solved, i don't know how thats possible, this issue of not accessible network computers has gone into thin air.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:49.
Find Us




Windows 10 Forums