Windows 10 Fall Creators Update – Cannot access network shares fix

3 3

You may also like...

10 Responses

  1. Sher Miller says:

    I can’t think you enough for this quick fix! I had several TB of data I couldn’t access due to the last update. After hours of trying a variety of fixes, this is the one that worked! I’ll be tracking to see if you hear back from WD regarding updating the protocol on their devices.

  2. Anonymous says:

    Thanks so much for this! I got all my network storage back. It’s the only thing that worked after hours of experimenting with mapping, changing share settings, and a host of other things. Have you heard back from WD about changing protocols yet?

  3. This mostly worked. For my version for some reason i had 3 boxes. One said to disable v1 when not needed. second was enable v1 and third was server. i unchecked the box for disable and checked server. also added linux support and telnet (grumbles……) and now my linuix devices can see windows 10 again!!!!

  4. Thanks for the feedback!

  5. Anonymous says:

    Ingenious. It works! Thank you very much!

  6. TomasF says:

    This is most likely caused by this:

    I don’t know how a MyBook Live works, but adding a local user with the same username as your logged in user on Windows should fix your problem

  7. Oz says:

    I’ve found a Powershell command that enables SMB1, see below. What I really want is to only enable the client feature only and not the server. Any ideas?

    Enable-WindowsOptionalFeature -Online -FeatureName “SMB1Protocol” -All -norestart

  8. Anonymous says:

    Same for me 🙁 Doesn’t work.
    Any other ideas?

  9. Anonymous says:

    Same for me 🙁 Doesn’t work.
    Any other ideas?

  10. Anonymous says:

    i have the same problem and after following these instructions it fails to reach mybooklive.
    Please, for a fix

Leave us a message...