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
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

246 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-11-04T00:25:38+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'?

    Hello Monkey57, thanks for the reply.

    After removing the SMB1 Client feature, rebooting, enabling the SMB1 client feature and rebooting a second time, volumes mapped to ReadyNAS via CIFS (SMB1) still indicated the network location was not available or the local name was already in use after a reboot, same as before the 20H2 update.  Confirmed I have Windows 10 Version 20H2. 

    The Auto Remove SMB1 feature was not and had not been enabled.

    Cheers,

    TL

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-11-04T05:39:00+00:00

    What actually worked for me on a long term basis was a combination of the registry hack:

    HKCU\Network(drive letter), add String Value of "ProviderFlags=1"

    plus updating to Windows 10 Version 20H2.

    Drives that were mapped to NAS devices using SMB1 are now reliably accessible across reboots.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-11-04T17:47:41+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)?

    I followed your steps and procedure. Result is the same. Still can't access the map drive after reboot. I'm trying to map a shared folder from network storage drive.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-04T18:46:17+00:00

    Was this answer helpful?

    0 comments