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
    2020-08-13T10:04:56+00:00

    Same issues here, awaiting for a fix. it's not like the first time where SMB1 was taken off - as been all through those issues again.

    Works fine accessing NAS on mobile and other laptops in house that are not the latest windows version.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-12T08:26:40+00:00

    I have been using SMB v1 so that I can navigate the drive attached to my NVidia Shield. Having just found out that NVidia have implemented SMB v3 (https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/340245/20152017-shield-experience-upgrade-802-hotfix-imag/), I deactivated SMB v1 in windows 10 (2004) and have found that this does not work, can't access nvidia host at all. So seeing this issue and the problems with W10 2004, I guess I'll have to go back to SMB v1, that is so widely castigated these days.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-11T21:36:19+00:00

    Experiencing the same issue.

    I have tried practically everything - mounting using GUI, using command prompt.

    After mouunting the drive (SMBv1) and asking the credential store to remember credentials (or using persistent) the access is working fine.

    But once the PC gets restarted is is kind of random behaviour.

    1. No way to access - getting error message that the drive is unaccessible
    2. Before accessing the drive it has a red cross but it actually shows the folders and files after opening
    3. It asks for Username and Password even when I ensure that credential store actually knows the credentials and they are correct.

    Was this answer helpful?

    0 comments
  4. Sumit 44,306 Reputation points Volunteer Moderator
    2020-08-11T06:37:51+00:00

    I have sent this thread to the appropriate people. Appreciate your patience.

    Was this answer helpful?

    0 comments