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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-06-21T18:52:50+00:00

    This resolved my issue.

    Apparently 20H2 is appending our FQDN to the end of the Folder path.

    so when we try to map \fs30.domain.ca\usr-home\userid, 20h2 is trying to map [fs30.domain.ca](https://fs30.domain.ca/)\usr-home[userid.domain.ca](https://userid.domain.ca/)

    We can prevent this with a period at the end of the FQDN, before the path.

    \fs30.domain.ca.\usr-home\userid

    Reference:

    https://amp.reddit.com/r/sysadmin/comments/m8m3zy/20h2_update_and_constantly_failing_mapped_drives/

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-06T15:49:03+00:00

    Thanks so much!  After a recent update to Windows 10, the supposed last version and best OS ever (actually a steaming pile of ****, reminds me of windows 98), my trusty WD TV Live Hub mapped drive would no longer connect.  I could remap it and it would work until I restarted, then it was gone again.  I would get the message "the local device name is already in use. This connection has not been restored".

    Adding that registry key to the drive name fixed it.  I am forever grateful.

    As for MS, I am betting at some point in the not-too-distant future they will realize they cannot continue down this path and start over, again - at least I hope they will.  Otherwise I will be forced to move to another OS, or build my own.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-02-03T17:59:06+00:00

    Any help is  appreciated

    I attempted to remove smb1 via Programs & Features, reboot, then re-add.  I was able to re-add it but it still didn't work.

    Then I used Powershell commands I found on link below.  It worked for me on 2 of my workstations.

    https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3

    Perhaps the "on-line" featureset is newer than the local feature set.

    Here are the commands.  Run Powershell as administrator.

    Get-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-03T23:00:59+00:00

    I am running an (old but functional) Iomega ix4-200d.  Shares worked fine up till update 2004.  I was able to remap the shares every time i restarted (but first has to put the NAS IP in the run box). Now i cant connect at all.

    PS.  Running two laptops with Windows 10 Home (single language) 1909 and one laptop Windows 10 Pro 1903.  All connect perfectly

    Thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments