SMB sharing not working after windows 10 update Build 2004 update

Anonymous
2020-06-20T02:30:38+00:00

Any help is  appreciated

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Monkey57 3,535 Reputation points
2020-11-03T02:21:51+00:00

Win10 20H2 fixes the issue.

Previously when 2004 broke smb1, I rolled back.

There was no registry change or any other modification made to the system.  After Win10 20H2 upgrade was installed via Windows Updates;  SMB1 worked as it did before the upgrade.

Thank you Microsoft.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

246 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-11-04T00:20:07+00:00

    Updating to 2H04 did not fix the SMB issue for me - still needing to disconnect/remap drives from a ReadyNAS using SMB 1.0 on each reboot. 

    I also followed Monkey57's guidance in terms of removing and re-enabling the SMB1 client feature and restarting.  The only things that actually work after a restart are:

    1.  Restarting the Workstation service, or 

    2.  Disconnecting and re-mapping the drives in question.

    Was this answer helpful?

    0 comments No comments
  2. Monkey57 3,535 Reputation points
    2020-11-03T23:02:00+00:00

    "still needing to disconnect/remap drives from a ReadyNAS using SMB 1.0 on each reboot. "->

    after the first removal and readd- you had to do it again?

    Did you remove the check in front of SMB1 Auto Remove in 'Windows Features'?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-11-03T22:48:39+00:00

    Updating to 2H04 did not fix the SMB issue for me - still needing to disconnect/remap drives from a ReadyNAS using SMB 1.0 on each reboot.

    Was this answer helpful?

    0 comments No comments
  4. Monkey57 3,535 Reputation points
    2020-11-03T22:07:09+00:00

    "Still can't access after reboot"

    1. in the 'Type here to search' box next to the start menu search for "Windows Features' click 'turn windows features on or off' go down to 'SMB 1.0/CIFS...' click the plus in front, uncheck any checked box in front of the 3 sub item

    reboot when prompted.

    1. go back into 'Windows Features' and put a check in front of 'SMB 1.0/CIFS Client' (only)

    reboot when prompted

    1. after reboot remove(disconnect) all mappings see:

    https://support.microsoft.com/en-us/help/890413/you-may-receive-the-the-local-device-name-is-already-in-use-error-mess

    "To resolve this issue, remove the existing network mapping. Then create a new network mapping for the share."

    That article is regarding connecting to shares on xp or before computers.

    1. Remap your shares.
    2. Reboot-test, Reboot-test  (it stayed working for me on various systems)

    NO registry editing or other settings where changed.

    What are you trying to map to (a linix box, windows box, network storage device, etc)?

    Was this answer helpful?

    0 comments No comments