Why is Windows 10 Version 2004 preventing logon scripts from mapping NAS drives at first logon attempt?

Anonymous
2020-06-06T22:33:25+00:00

Since we updated Windows 10 to Version 2004 that all the machines in our domain stopped mapping NAS drives at first logon.

When the users start the machines and logon the logon script maps correctly the drives in several servers but not in the NAS.

If they logoff and logon again then the mapping is done correctly.

The problem occurs sistematically and started only after Version 2004 was installed.

It has nothing to do with SMB 1.0 being enabled - it was already enabled before Version 2004 as it was needed because we are talking about an old NAS.

Direct SMB appeared enabled and we disabled it, but it didn't solve the problem.

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

42 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-12-10T14:22:47+00:00

    Well, guys it's been (not) fun working with you all on this issue.  I have to bid you all adieu.  After me fussing and fuming about this issue to management, my company finally allocated the resources to build us a new Windows 2016 64 bit server and we migrated the data to it.  So this is no longer an issue for me as we no longer have any SMB1 servers left.  

    MS has clearly stated in it's complete silence on this and a few other forums that it will NEVER address this issue and the only route we have to a real fix is to update the servers.  For non MS SMB1 devices this is still an ongoing issue.  

    The bit of script I describe above works well to remove the registry keys for all drive letters.  So even if your users map their own drives to these old servers, the script will remove the key and prevent it from stalling the logon process and make the shares immediately accessible.  When I was using it I put this at the head of the script before the map commands and again afterwards so that the registry key was gone no matter what. 

    So, good luck all.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-01-06T10:00:12+00:00

    I have a similar problem with two venerable Dlink NAS boxes using SMB1 (SMB1 is enabled).

    The devices have worked for over a decade and there are no signs of hardware or network failure.

    (A new Synology NAS works perfectly).

    From months of testing and fiddling with settings, I confirm that these devices always fail to connect after a cold boot, with (wrong) message "The local device name is already in use".

    They always reconnect and work correctly after a restart (or logout/login).

    Changing from devices name \dlink-...\volume_1 to IP address \192.168.0.99\ makes no reliable difference.

    The 2004 (and 20H2) updates has created some deadlock that causes this very annoying behaviour.  Microsoft - please fix it.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments