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
    2021-08-25T06:10:43+00:00

    Adding the . to the end of the FQDN worked for me.... thank you for this solution. Only found it after hours of troubleshooting.

    **** Microsoft???

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-07-28T15:00:32+00:00

    Which apps do you need that only run on WinDose?

    New Ubuntu seems to have quite an impressive software list. I just installed Ubuntu v 20.nn on an old iMac. Very impressive.

    kaw

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-07-28T09:17:50+00:00

    It sounds great, but my laptop is disabled for 6 hours as it tries to upgrade, fails, and backs out, only to try again a week later. This is despite sending numerous complaints to the feedback hub.
    If it weren't for the few applications that I need to run on windows I'd be fully Linux by now.
    Windows Update breaks my Laptop every time it runs.

    If you know any way to get past, what has been at least a 2-year battle to get updates to work my sanity might start to return.

    Was this answer helpful?

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