windows 10 version 2004 mapped drive issue

Question

windows 10 version 2004 mapped drive issue

Kevin Rampersad 1

I would like to report that all mapped networking drives on all computers fail to connect consistently after this update in our company. The servers are 2003 servers. While we were able to roll back some computers to 1909 and fix the issues, others would not let us roll back and we had to wipe them and put version 1909 back on them. I would like to mention that these updates were pushed to the computers without any input even though MS states that it is optional and you have to manually upgrade to it. Why on earth would they force this on you?

After the format, several computer auto updated again to 2004. right now my only workaround it to set the adapter in metered connection mode to stop the updates.

Anonymous

2020-08-17T07:15:48.763+00:00

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.
Indoman 31 Reputation points

2020-08-17T15:35:43.62+00:00

Mine is also with mapped drives for 2003 Server! Mapped drives for server 2016 is not effected. I also have been able to reverse some updated computers, but others will not roll back. The only fix I have found is:

Computer\HKEY_CURRENT_USER\Network\Z or your drive letter, I deleted Z.

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU and delete the entry, (a, b, etc), for your drive.

Then add the following after remapping your drive or else it will fail to connect after a reboot or shutdown.

[HKEY_CURRENT_USER\Network\Z]

"ProviderFlags"=dword:00000001 (32 bit d-word / hex value 1)
James Patchell 1 Reputation point

2020-09-07T20:08:35.153+00:00

I would like to say that I am also having a very similar problem and I will try to give as much detail as possible.

My network drives are connected to a Linksys Router, described on amazon as "Linksys AC2600 4 x 4 MU-MIMO Dual-Band Gigabit Router" at the following link:
https://www.amazon.com/gp/product/B00UVN21DK/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1

It was purchased in 2016, and as near as I can tell has the latest firmware.

The explanation of the problem had to be shortend due the 1000 character limit.

Using the >Network in file explorer, of my two computers one could the listing for the network name which will show the icons for the drive, if it works. One computer works, the other doesn't. The computer that did not work had the drive mapped. When I unmapped the drive, and rebooted I could then access the drive using the >Network in file explorer. I don't really know if this a problem with the router or windows 10.
Paulo J. F. Martins 1 Reputation point

2020-09-12T00:13:10.863+00:00

This appears to be the same problem as in this one:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/why-is-windows-10-version-2004-preventing-logon/91d2d8e6-1b83-4c51-a14c-d8db452a434c?tm=1591482825235
Jeno 1 Reputation point

2020-09-14T09:18:51.797+00:00
The same applies to my computer. The problem is that the NET USE commands i used to map remote drives to my local W10 do not work any more in 2004. Their output says:

System error 1312 has occurred. A specified logon session does not exist. It may already have been terminated.

The only work-around is to restore the previous version of W10, which is quite cumbersome, takes about two hours, and has to be repeated every week, since the 2004 update is forced to be installed every week.
MEH 1 Reputation point

2020-09-30T09:47:59.683+00:00
Enable SMB1 on Windows workstations:

Search in the start menu for ‘Turn Windows features on or off’ and open it

Search for ‘SMB1.0/CIFS File Sharing Support’ in the list of optional features that appears, and select the checkbox next to it.

Click OK and Windows will add the selected feature. Restart your computer as part of this process.
Kevin Rampersad 1 Reputation point

2020-10-13T16:30:58.737+00:00

Seemed to work for some computers but not others. I just bought a new Dell and it came with 2004 pre-installed. It will not map to any of my 2003 or 2012 servers. I do have a 2016 cloud server and that maps but works intermittently. It will connect then sometime work or lock up Explorer. It is apparent that I am not the only one with this issue and MS has no clue how to fix it yet. The problem is now some new computers are coming with this version of Windows.
Anonymous

2020-10-29T15:08:38.237+00:00

Hello all, I just found the lifesaver ;-) (for Synology NAS but probalby also useful for others)

I had exactly the same issues with build 2004 and our office Synology NAS ; searching 2 days for a solution...

Make sure you have the latest DSM update installed (important).

Controle Panel
File Services
Advanced
Enable WS-Discovery !!

For those using SMB1 : (I was, due to some former incompatibility issues):

Change to min SMB= SMB1 and max SMB = SMB3 (also under file services)
Reboot NAS
Reboot PC + re-map the NAS network drive
Reboot PC to check if the network drive is still intact and here you go...
Stayko Kolev 1 Reputation point

2020-11-27T12:21:04.713+00:00

Thank you sir! I registered here just to say it works.
Kevin Rampersad 1 Reputation point

2020-12-09T19:28:40.357+00:00

I have updated some computers to 20H2, the version after 2004 and simply adding the provider flags to the letter and a reboot has resolved the issues. Not the best solution but at least I don't have to keep rolling back computers anymore.
Bill O'Neill 1 Reputation point

2020-12-12T20:29:40.8+00:00

This is happening with me too. Strange thing is, shares between other Windows 10 and Windows 7 machines are unaffected. In my case, the only issues I have are with shares to a Thecus NAS. I'll try ArtDepartment's solution. However, the fact that Microsoft have not addressed this is disappointing, to say the least. It is probably done on purpose. Done to get people to either upgrade or move away from non-Microsoft products. Just like they are doing with Windows 7.

There are reasons to run older operating systems. We need to run MS-DOS, XP and Win 7 because of software that has unique abilities but has not been updated to run on later operating systems. However MS couldn't give a rat's A$$.
Matija Lah 1 Reputation point

2021-03-03T13:28:14.92+00:00

So far, so good.

What is this flag, and why isn't it on by default?
(Rhetorical...)
Bud 1 Reputation point

2021-06-15T02:43:19.287+00:00

I have a Windows Server 2019 Essentials and 3 Windows-10 workstations. When the workstations upgraded from version 1909 to 2004, I started to have the mapped drive issues as described in this thread. The added symptom was that if I mapped using the server local name, it would work until a reboot and then the mapped drive would be gone, and I could not re-establish the mapped drive (I would get an error message). But, I could establish the mapped drive using the IP address UNTIL I REBOOT, and then the mapped drive was gone (and trying to establish it using IP would error out), BUT THEN I COULD ESTABLISH the mapped drive using the local name --- UNTIL I REBOOT... and then the IP would work..., and back and forth.
So, I reverted back to 1909, I checked the Windows Release notes for 2004, 20H2, and 21H1 but none of them mention this issue, and so MY question is has anyone really found a fix (none of the ones below has fixed my issue) OR has M$ fixed this in one of the new feature releases?
J Allen 1 Reputation point

2021-09-29T10:51:03.817+00:00

After latest Windows 10 update and also with Windows 11, the first time any Windows 10 computer is powered up, the servers are invisible, but by doing a restart they appear, While Restart is not a proper fix it gives users a temporary way around the problem. Start-Login wait until fully up, Restart-Login again. M$ please find the problem and correct it in the next W10 update, also please do not change network settings when applying updates.

9 answers

Your answer

Anonymous

2020-08-17T07:15:48.763+00:00

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.
Indoman 31 Reputation points

2020-08-17T15:35:43.62+00:00

Mine is also with mapped drives for 2003 Server! Mapped drives for server 2016 is not effected. I also have been able to reverse some updated computers, but others will not roll back. The only fix I have found is:

Computer\HKEY_CURRENT_USER\Network\Z or your drive letter, I deleted Z.

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU and delete the entry, (a, b, etc), for your drive.

Then add the following after remapping your drive or else it will fail to connect after a reboot or shutdown.

[HKEY_CURRENT_USER\Network\Z]

"ProviderFlags"=dword:00000001 (32 bit d-word / hex value 1)
James Patchell 1 Reputation point

2020-09-07T20:08:35.153+00:00

I would like to say that I am also having a very similar problem and I will try to give as much detail as possible.

My network drives are connected to a Linksys Router, described on amazon as "Linksys AC2600 4 x 4 MU-MIMO Dual-Band Gigabit Router" at the following link:
https://www.amazon.com/gp/product/B00UVN21DK/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1

It was purchased in 2016, and as near as I can tell has the latest firmware.

The explanation of the problem had to be shortend due the 1000 character limit.

Using the >Network in file explorer, of my two computers one could the listing for the network name which will show the icons for the drive, if it works. One computer works, the other doesn't. The computer that did not work had the drive mapped. When I unmapped the drive, and rebooted I could then access the drive using the >Network in file explorer. I don't really know if this a problem with the router or windows 10.
Paulo J. F. Martins 1 Reputation point

2020-09-12T00:13:10.863+00:00

This appears to be the same problem as in this one:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/why-is-windows-10-version-2004-preventing-logon/91d2d8e6-1b83-4c51-a14c-d8db452a434c?tm=1591482825235
Jeno 1 Reputation point

2020-09-14T09:18:51.797+00:00

The same applies to my computer. The problem is that the NET USE commands i used to map remote drives to my local W10 do not work any more in 2004. Their output says:

System error 1312 has occurred. A specified logon session does not exist. It may already have been terminated.

The only work-around is to restore the previous version of W10, which is quite cumbersome, takes about two hours, and has to be repeated every week, since the 2004 update is forced to be installed every week.
MEH 1 Reputation point

2020-09-30T09:47:59.683+00:00

Enable SMB1 on Windows workstations:

Search in the start menu for ‘Turn Windows features on or off’ and open it

Search for ‘SMB1.0/CIFS File Sharing Support’ in the list of optional features that appears, and select the checkbox next to it.

Click OK and Windows will add the selected feature. Restart your computer as part of this process.
Kevin Rampersad 1 Reputation point

2020-10-13T16:30:58.737+00:00

Seemed to work for some computers but not others. I just bought a new Dell and it came with 2004 pre-installed. It will not map to any of my 2003 or 2012 servers. I do have a 2016 cloud server and that maps but works intermittently. It will connect then sometime work or lock up Explorer. It is apparent that I am not the only one with this issue and MS has no clue how to fix it yet. The problem is now some new computers are coming with this version of Windows.
Anonymous

2020-10-29T15:08:38.237+00:00

Hello all, I just found the lifesaver ;-) (for Synology NAS but probalby also useful for others)

I had exactly the same issues with build 2004 and our office Synology NAS ; searching 2 days for a solution...

Make sure you have the latest DSM update installed (important).

Controle Panel
File Services
Advanced
Enable WS-Discovery !!

For those using SMB1 : (I was, due to some former incompatibility issues):

Change to min SMB= SMB1 and max SMB = SMB3 (also under file services)
Reboot NAS
Reboot PC + re-map the NAS network drive
Reboot PC to check if the network drive is still intact and here you go...
Stayko Kolev 1 Reputation point

2020-11-27T12:21:04.713+00:00

Thank you sir! I registered here just to say it works.
Kevin Rampersad 1 Reputation point

2020-12-09T19:28:40.357+00:00

I have updated some computers to 20H2, the version after 2004 and simply adding the provider flags to the letter and a reboot has resolved the issues. Not the best solution but at least I don't have to keep rolling back computers anymore.
Bill O'Neill 1 Reputation point

2020-12-12T20:29:40.8+00:00

This is happening with me too. Strange thing is, shares between other Windows 10 and Windows 7 machines are unaffected. In my case, the only issues I have are with shares to a Thecus NAS. I'll try ArtDepartment's solution. However, the fact that Microsoft have not addressed this is disappointing, to say the least. It is probably done on purpose. Done to get people to either upgrade or move away from non-Microsoft products. Just like they are doing with Windows 7.

There are reasons to run older operating systems. We need to run MS-DOS, XP and Win 7 because of software that has unique abilities but has not been updated to run on later operating systems. However MS couldn't give a rat's A$$.
Matija Lah 1 Reputation point

2021-03-03T13:28:14.92+00:00

So far, so good.

What is this flag, and why isn't it on by default?
(Rhetorical...)
Bud 1 Reputation point

2021-06-15T02:43:19.287+00:00

I have a Windows Server 2019 Essentials and 3 Windows-10 workstations. When the workstations upgraded from version 1909 to 2004, I started to have the mapped drive issues as described in this thread. The added symptom was that if I mapped using the server local name, it would work until a reboot and then the mapped drive would be gone, and I could not re-establish the mapped drive (I would get an error message). But, I could establish the mapped drive using the IP address UNTIL I REBOOT, and then the mapped drive was gone (and trying to establish it using IP would error out), BUT THEN I COULD ESTABLISH the mapped drive using the local name --- UNTIL I REBOOT... and then the IP would work..., and back and forth.
So, I reverted back to 1909, I checked the Windows Release notes for 2004, 20H2, and 21H1 but none of them mention this issue, and so MY question is has anyone really found a fix (none of the ones below has fixed my issue) OR has M$ fixed this in one of the new feature releases?
J Allen 1 Reputation point

2021-09-29T10:51:03.817+00:00

After latest Windows 10 update and also with Windows 11, the first time any Windows 10 computer is powered up, the servers are invisible, but by doing a restart they appear, While Restart is not a proper fix it gives users a temporary way around the problem. Start-Login wait until fully up, Restart-Login again. M$ please find the problem and correct it in the next W10 update, also please do not change network settings when applying updates.

Answer 1

Hello all, I just found the lifesaver ;-) (for Synology NAS but probalby also useful for others)

I had exactly the same issues with build 2004 and our office Synology NAS ; searching 2 days for a solution...

Make sure you have the latest DSM update installed (important).

Controle Panel
File Services
Advanced
Enable WS-Discovery !!

For those using SMB1 : (I was, due to some former incompatibility issues):

Change to min SMB= SMB1 and max SMB = SMB3 (also under file services)
Reboot NAS
Reboot PC + re-map the NAS network drive
Reboot PC to check if the network drive is still intact and here you go...

Answer 2

I want to give more information to help @Anonymous reproduce the problem in her lab.

Background Information
My PC has mapped drive to 2 file servers.
a) NAS IP 192.168.1.171 with drive Q.
b) Windows 2000 Server IP 192.168.1.203 with network drive S, W, X, Y

The problem happen to only windows 2000 server not NAS. My network drive Q has no problem at all.

Every day after logon to my PC and try to connect to my network drive at Windows 2000 Server. Two type of error message.
a) The error message on drive S shown "S:\ is not accessible. The specified network name is no longer available.
b) The error message on drive W shown "An error occurred while reconnecting W: to \192.168.1.203\working$ Microsoft Windows Network: The local drive name is already in use. This connection has not been restored."
c) The error message on drive X and Y are similar to W.
1. I disconnect only drive S: while drive W, X, Y stilled mapped but inaccessible.
2. I map network drive S: again and the error shown "The mapped network drive could not be created because the following error has occurred: The specific network name is no longer available."
3. I have to disconnect all network drive that connect to 192.168.1.203. Then I can reconnect network drive S, W, X, Y.

MotoX80 37,346 Reputation points

2020-10-06T13:10:30.447+00:00

You should not be running Windows 2000. That is so far out of support you are putting your organization and data at risk.

Answer 3

MEH 1

Enable SMB1 on Windows workstations:

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

Answer 4

Anonymous

I am experiencing the same issue posted by JuergenFleck-6603.

All systems are on 2004 and have verified connection to the mapped drive's UNC path.

Mapped drives show as connected with Get-PSDrive, but do not appear in File Explorer at all. No red X's, just gone.

When File Explorer is reset through Task Manager the drives appear as expected.

Anonymous

2020-09-04T05:49:05.587+00:00
I have tested in my windows 10 2004 and I did not occur such problem. I mapped drive and restart the PC, it still exists here.

Before we go further, I would like to confirm the following questions:

When did this issue start to occur? Before the issue happened, did you do any modifications?

The machine is domain joined or work group environment? Did you configure any group policy?

How did you map the drive? Manually or via GPO?

Please provide more details and then I can reproduce this issue in my lab.
Diesel 1 Reputation point

2020-09-30T06:10:49.13+00:00
In my case this is happening with the following setup:

Domain Joined PC

DC is Windows server 2003

Network Drives are Mapped through AD

Drives appears in Windows Explorer but when clicked it locks up explorer.exe

Confirmed PCs with 1909 is not experiencing problems

All Version 2004 are affected
Anonymous

2020-09-30T06:28:42.347+00:00

Have you manually mapped the drive? Did the issue still occur? If this issue is only occurred when you mapped drive through AD, you could open a new thread and add AD tags.
Kevin Rampersad 1 Reputation point

2020-10-13T16:53:47.167+00:00

Hi Candy,
The servers are 2003. The clients are all Windows 10 machines with manually mapped drives to the server shares. With Client Version 1909 and earlier, all mapped drives work fine. SMBv1 has been enabled on the clients running Win 10 2004 but this did not help the issue. As Diesel-9909 stated, it will either disappear or lock up explorer. Another note is that trying to access the servers via UNC path also fails intermittently with the same lockup results or an error stating the server is inaccessible.

Hopefully in your lab you can setup such an environment and get the same results.

Answer 5

Anonymous

Hi ,

Based on my understanding, the mapped network drives are not automatically reconnected at Windows startup. After logging you will see the following scenes:

In Windows Explorer, a red X appears on the mapped network drives.
Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.
In the notification area, a notification displays the following message: Could not reconnect all network drives.

Is it right? Please feel free to correct me if my understanding is wrong. If yes, you can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device.

For more details about scripts, you could refer to the following article:

https://support.microsoft.com/en-us/help/4471218/mapped-network-drive-may-fail-to-reconnect-in-windows-10-version-1809

Here is a similar thread discussed before, you could have a look:

https://learn.microsoft.com/en-us/answers/questions/56488/why-wont-windows-10-pro-2004-reconnect-my-network.html

---Please Accept as answer if the reply is helpful---

Best Regards,
Candy

Indoman 31 Reputation points

2020-08-17T15:51:51.533+00:00

Mine is also with mapped drives for 2003 Server! Mapped drives for server 2016 is not effected. I also have been able to reverse some updated computers, but others will not roll back. The only fix I have found is:

Computer\HKEY_CURRENT_USER\Network\Z or your drive letter, I deleted Z.

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU and delete the entry, (a, b, etc), for your drive.

Then add the following after remapping your drive or else it will fail to connect after a reboot or shutdown.

[HKEY_CURRENT_USER\Network\Z]

"ProviderFlags" (32 bit d-word / hex value 1)
Juergen Fleck 6 Reputation points

2020-08-27T09:31:18.523+00:00

In my case, there is no red X.

net use shows the mapped drives and there is no notification that the network drives could not be reconnected. The drives just do not show up in the windows explorer.

the two links you posted @Anonymous do not help to solve the issue. I replied to the post in the second link and explained what I tried to solve the problem.
Anonymous

2020-08-27T10:02:42.553+00:00

Based on my understanding, the network drives disappear in GUI (windows explorer) but you can check the drives are mapped with "net use" command. Is that right? Please feel free to let me know if my understanding is wrong.

If yes, I will try to reproduce this phenomenon in my windows 10 2004 and will get back to you as soon as possible. I appreciate your patience.

If you have any updates during this process, please feel free to let me know.
Rusty 1 Reputation point

2020-10-26T19:11:42.443+00:00

Thanks ARTDEPARTMENT-8791

That got me fixed. I had to add SMB1 for an old DROBO device but it kept failing after boot. This fixed it.

Share via

windows 10 version 2004 mapped drive issue

9 answers

Your answer