This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
i just installed Windows 10 20H2 (October update).
It has the exact same issue, so no fix there either.
MS is silent on this issue. In ONE forum they closed the thread stating 'Update your server's OS' as the solution.
I'm harping to my companies powers that be about this, and it looks like there is no money to replace our server. And it WILL require replacement as it is so old that it will not support anything newer. It's 32 bit so no upgrade is possible.
Same issue here, took over a client that has a 2003 server and purchased a bunch of Win 10 machines, all machines were on a workgroup before but I wanted to fix that and put them on a domain. Well much to my surprise when I set a logon script it connects fine the first time by name and maps but then you reboot it it cant connect by name but can by IP, so as a test I mapped the drives by IP then reboot and wouldn't you know the next time it wont connect by IP but it will connect by name. Reboot again and the opposite happens. Went over this post and tried everything and yes I do have SMB v1 enabled.
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.
Enable SMB1 on Windows workstations:
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.
