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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-27T07:13:05+00:00

    You're right, they force users to migrate by using small "annoying annoyance" ...

    In a way they are right, but it might be better to give a positive incentive to migrate rather than push back like this.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-27T07:07:11+00:00

    Sorry to hear that, unfortunately we don't have any more servers 2003/2008 servers with file shares for me to be able to troubleshoot and help with a solution. It must be something to do with the security vulnerabilities of SMBv1, MS is forcing everyone to upgrade. How i came across my fix was to disable SMBv1 on the client side and when trying to open the mapped drive i received the below error: ![](https://learn-attachment.microsoft.com/api/attachments/a93df548-d7c8-4d20-8d42-6e44b26cefe8?platform=QnA

    • This is what led me to enabling SMBv2 on server side. So id suggest upgrading to server 2012 r2 or higher and enabling SMBv2/3.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-27T06:28:41+00:00

    Any help is  appreciated

    I have resolved this case as below instruction 

    1. Window+ R -> services.msc

    Enable " Function Discovery Resource  Publication" & " Function Discovery Provider Host" 

    1. Control Panel / Program / Turn Windows features on off / Window Features

    Enable SMB 1.0/CIS File Sharing Support

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-25T18:46:39+00:00

    I had this issue as well, and was driving me crazy, where my mapped drives to my Synology NAS could not be accessed.  The disk free space was not displaying, and it was coming up with Incorrect username or password when trying to access them.  The only option would be to disconnect and reconnect in every logon session.  Deleting the entry in Credential Manager made no difference, leading me to believe it was not Windows causing the issue.

    I know it won't help everyone, but for those with a Synology NAS, I eventually fixed it by going into Synology DSM and turning on SMB2 in the Control Panel > File Services > (under SMB) Advanced Settings > set Maximum SMB protocol to SMB2 and Minimum SMB protocol to SMB1.

    For the record, SMB 1.0/CIFS File Sharing Support was enabled in the Windows 10 features.

    Was this answer helpful?

    0 comments