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: Newest
  1. Anonymous
    2021-05-09T21:38:24+00:00

    As of now I have not come to a solution which would fix my SMBv1 drives

    The drives are mounting sucesfully however after restart they are not accessible and while I am trying to access them from another explorer window using IP or Name it says the resource is already mounted under different credentials.

    I was desperatelly looking for a solution quite a while. Recently I decided to fix it with workaround - something in the Windows 10 is corrupted what relates to SMBv1.

    So I have wrote and application which does the mounting instead of Windows. I call it NAS Mounter - available here

    Feel free to downlaod and use. In case of any question do not hesitate to drop me a note.

    Step by Step:

    1. Install the NAS Mounter

    2) Start the NAS Mounter from Windows Start Menu

    1. Add your drives (as per screenshots)- Your drives will be imediatelly mounted and optionaly you can rename them and change icons
    2. Enjoy !

    ImageImage

    Image

    Hope this helps !

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-04-12T19:02:45+00:00

    Any help is  appreciated

    SMB1 mapped drive issue solved.

    [...]

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Network\p]

    "ProviderFlags"=dword:00000001

    Note: In the above registry entry "P" is the drive letter I use.

    I think this helped me: after entering registry setting as above everything works well even only one mapped share has this modification.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-04-07T15:36:13+00:00

    Got all of the settings you suggest and still no joy.

    Was this answer helpful?

    0 comments No comments
  4. 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 No comments