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-08-27T13:47:47+00:00

    I have the same issue. I would love to upgrade the server but its not going to happen anytime soon. We are in the process of building a new IT room and I will have to wait until that is finished. My fear is we will have more users with the problem before we can upgrade the server. I have three right now but with the potential to have up to 100.

    The REG delete in the logon scripts seems to be working for now.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-27T16:31:00+00:00

    We ran into this same problem and going from notes here we hacked a different band aid into the logon script (this is hokey at best and I've got far worse ways to describe this...)

    We added a sleep statement at the top of the logon script which delayed the drive mapping, this (so far in testing) appears to work for all of the workstations we tested on.  Simply add the timeout command to the top and see what you get.  Your experience may vary...

    timeout /t 60

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-09-23T00:33:41+00:00

    Map the drive over on the ADDC and push the map over to each computer when they log in to the domain. Also delete the mapping on the W10 computer and remove all mapping from the registry.

    Worked for me.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-30T09:53:42+00:00

    Enable SMB1 on Windows workstations:

    1. Search in the start menu for ‘Turn Windows features on or off’ and open it.
    2. Search for ‘SMB1.0/CIFS File Sharing Support’ in the list of optional features that appears, and select the checkbox next to it.
    3. Click OK and Windows will add the selected feature. Restart your computer as part of this process.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-09-30T10:32:15+00:00

    Wow MEH-2666, you are a few months late to the game.  Everyone here that is experiencing the this problem already has SMB 1.0/CIFS installed already.  The issue is that when a PC is updated to Win 10 2004 and has SMB 1 installed to be able to attach a drive mapping to an old server (or old NAS that uses SMB1) that the logon scripts stall because of some odd new registry entry that is not writing an invalid key type for SMB 1 devices.  

    We've discussed deleting this key type in a logon script for about a 95%+ success rate in 'fixing' the issue earlier in this thread.  However this will NOT help if a user has mapped drives to a Windows 2003 server on their own. It also seemingly randomly stalls anyway maybe once ever 20 times or so. 

    I monitor this very subject on a few forums and MS seems mute on the subject and has not offered a fix or proper work around besides insisting to update the old servers to a new OS. 

    Thanks friend but this is not a fix for this.

    Was this answer helpful?

    0 comments