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-10T05:04:45+00:00

    Hi,

    I changed login script to FQDN path "\myserver.domain.local\Folder" as you provided. Unfortunatelly this does not work at all. After a domain user log into a computer and tries to open the mapped network folder, it gives the very same error and drive is not accessible.

    Additionally, I put the user into local administrators group of the machine, but it also does not help.

    I would say "It never rains, but it pours".... :-( stupid bug!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-09T22:22:12+00:00

    Discovered a couple things today regarding this:

    If the domain user account is just a member of the local users group, you won't be able to browse to the server by it's short-name, but FQDN works fine.

    Make the domain user account a member of the local admin group and everything works as expected. (obviously not how you want to leave it)

    I ended up disconnecting the previous drive mapping via a script and remapping the drive with the FQDN in a login script. This then allowed me to access the share, and if the drive is mapped using the FQDN, you are then able to browse to the share via the short-name.

    So, no clear answer, but a definite work-around.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Neil D 34,280 Reputation points Volunteer Moderator
    2020-07-09T12:31:38+00:00

    Please see my previous reply today.

    Was this answer helpful?

    0 comments