Trouble reconnecting to shares after upgrading from 1909 to 20H2  

Page 1 of 2 12 LastLast

  1. Posts : 51
    Windows 10 Pro

    Trouble reconnecting to shares after upgrading from 1909 to 20H2

    I have a W10 Pro desktop that I just upgraded from 1909 to 20H2 and now I can't connect to my shares from my Lenovo or Dell laptops. The Lenovo already has 20H2. The Dell had 1909 which I just upgraded to 20H2. The desktop with the shares has the netplwiz option "Users must enter a user name and password to use this computer" checked and there is NO password so the pc does not require a logon on boot. The shares were originally connected years ago with the net use command and persistence and I have never had a problem. I don't remember how I did it with no password. Now that I have lost connectivity I can't reconnect because of account restrictions, probably no password.

    I don't want to logon to this pc everytime I boot; just want to boot into W10. If I create a password with the Accounts-Sign-In Options will I have the option to choose NEVER login? That will give me the password for reconnecting to the shares with net use. Is there no way to connect to a share without a password?

    Network is Private and I have Password Protected sharing turned on for all networks.

      My Computer

  2. Posts : 39,316
    Win 10 Pro (22H2) (2nd PC is 22H2)

    Unfortunately MS has messed networking up in 20H2. I've just recently upgraded this PC from 1903, and now it can't 'see' my other PC, still on 1903. The other way round is fine.

    See e.g. post #23
    Network computers not showing after 20H2 update

    Interesting checks and guide:
    Network Computers are not Showing Up in Windows 10 | Windows OS Hub

    Logging on to a particular account automatically with no login is possible- tutorial available.
      My Computers

  3. Posts : 7,605
    windows 10

    The fastest way is to remove the shares and redo them permission and side will have changed. By default windows passes the username password your logged in with so the simple way is to create account on the target pc with same name and password then it's passed by default
      My Computer

  4. Posts : 39,316
    Win 10 Pro (22H2) (2nd PC is 22H2)

    Hi, just got mine working again.. not entirely sure how.

    Problem was-
    a. My 20H2 PC would no longer 'see' my 1903 PC after the upgrade.
    b. Networking - moderately fast green progress bar when opened or refreshed (previously none).

    I tried
    - checking settings various.. nothing found.
    - re-enabling SMB1 on both - no success (should not enable this if all are Win 10).

    From an admin command prompt on the 20H2 PC
    net view
    only showed the 20H2 PC.

    Then I tried simply creating a shortcut to the 1903 PC
    - the PC being from PC Specialist in the UK...hence the name I gave it.

    To my surprise, using that, I could 'see' the shared folders.

    Then the Network view suddenly began to show both PCs again.

    Similar problems have been reported in numerous threads.
      My Computers

  5. Posts : 51
    Windows 10 Pro
    Thread Starter

    Well I got mine solved and the answer was in my original post where I stated that Password Protected Sharing was turned on for all networks. I realized that I had turned it off to make it work when requiring a login but with no password. Apparently 20H2 turned it on. Interestingly I could not get to my shared printer from the Dell but could from the Lenovo and could not get to any folder shares from either laptop. Go figure.

    Someone mentioned that SMB is a security risk, and I have it turned on. I believe I had to do that sometime in the past to make the sharing work. I don't know whether it will work with out it. What's the risk?
      My Computer

  6. Posts : 39,316
    Win 10 Pro (22H2) (2nd PC is 22H2)

    It's reckoned a security risk- you only need it if 1 of the PCs is, say, Win 7, or for certain NAS devices.
    But with this 20H2 problem...

    I found mine only worked that one time.. not after a restart.
      My Computers

  7. Posts : 51
    Windows 10 Pro
    Thread Starter

    I am assuming the SMB vulnerability has been patched in W10. Still, probably better not to use at all if possible.
      My Computer

  8. Posts : 39,316
    Win 10 Pro (22H2) (2nd PC is 22H2)

    No, it's just not meant to be used unless you have to. There's a difference between software vulnerabilities and fundamentally weak protocols.
      My Computers

  9. Posts : 28,458
    10 Home x64 (22H2) (10 Pro on 2nd pc)

    dalchina said:
    .... My 20H2 PC would no longer 'see' my 1903 PC after the upgrade.....

    Odd, I've not had such problems. As a test I've just thrown together the most eclectic collection of machines I could easily put together (Win7, 1809, 1909 and several 20H2). They could all see and connect to each other....

    Trouble reconnecting to shares after upgrading from 1909 to 20H2-image.png
      My Computers

  10. Posts : 39,316
    Win 10 Pro (22H2) (2nd PC is 22H2)

    Quite a few reports of this...
      My Computers


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:03.
Find Us

Windows 10 Forums