question

KevinRampersad-2171 avatar image
0 Votes"
KevinRampersad-2171 asked ·

windows 10 version 2004 mapped drive issue

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.

windows-10-general
· 12
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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)

4 Votes 4 ·

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.

0 Votes 0 ·

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.

0 Votes 0 ·

Thank you sir! I registered here just to say it works.

0 Votes 0 ·

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$$.

0 Votes 0 ·
MatijaLah-3173 avatar image MatijaLah-3173 ArtDepartment-8791 ·

So far, so good.

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

0 Votes 0 ·

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.

0 Votes 0 ·

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.

0 Votes 0 ·

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.

0 Votes 0 ·
Show more comments
CandyLuo-MSFT avatar image
0 Votes"
CandyLuo-MSFT answered ·

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://docs.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




· 4 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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)

2 Votes 2 ·

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.

0 Votes 0 ·

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 @CandyLuo-MSFT 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.

0 Votes 0 ·

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.

0 Votes 0 ·
itworker4545 avatar image
0 Votes"
itworker4545 answered ·

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.

· 4 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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:

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

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

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

Please provide more details and then I can reproduce this issue in my lab.





0 Votes 0 ·

In my case this is happening with the following setup:

  1. Domain Joined PC

  2. DC is Windows server 2003

  3. Network Drives are Mapped through AD

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

  5. Confirmed PCs with 1909 is not experiencing problems

  6. All Version 2004 are affected


0 Votes 0 ·

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.

0 Votes 0 ·
Show more comments
MEH-2666 avatar image
0 Votes"
MEH-2666 answered ·

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


·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AungkanaK-6122 avatar image
0 Votes"
AungkanaK-6122 answered ·

I want to give more information to help @CandyLuo-MSFT reproduce the problem in her lab.
1. 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.

  1. 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.

  2. I disconnect only drive S: while drive W, X, Y stilled mapped but inaccessible.

  3. 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."

  4. I have to disconnect all network drive that connect to 192.168.1.203. Then I can reconnect network drive S, W, X, Y.

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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

0 Votes 0 ·
RafGNB-8157 avatar image
0 Votes"
RafGNB-8157 answered ·

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...

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Ihate2004Build-8222 avatar image
0 Votes"
Ihate2004Build-8222 answered ·

Anyone figure this out yet?

Having the same issue with 2004 build. Drive mapping from windows 2003 server crashes explorer, but it works on builds before 2004 with no problem .

People are using this drive mapping for clocking in. Anyone found a solution yet?

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This is what worked for me for the drives that were having the issue (connecting to an older netapp appliance):

HKEY_CURRENT_USER\Network\

You should see a list of mapped drive letters under Network. Click on the mapped drive letter having the issue. Add a new DWORD (32 bit) value called ProviderFlags with a value of 1

Reboot. The drive(s) should connect after that.

0 Votes 0 ·
PeterGreene-6698 avatar image
0 Votes"
PeterGreene-6698 answered ·

I hope this helps others.

I have a small 10-user Windows-10 network with workgroups, mapped drives and shares.

Microsoft (M$) in its infinite wisdom decided with the upgrade to build 2004 - to change network operating features along with other items.
"M$ - it is my network, my servers, my workstations, my devices - leave my settings ALONE !!! It is my data - not yours!"

I have attached 2 screenshots where settings were changed by M$ during the upgrade process. Network discovery for a private network needs to be turned ON; M$ turned it OFF. And, if you use password protection - then M$ probably left it alone; if you do not use password protection then M$ also probably turned it ON ---> so you will need to turn it OFF - you decide which one is right for your use.

Also, worth noting it that M$ also turned of using "restore points"; so you may want to check if you have this enabled because most likely M$ disabled this setting for your too!39390-ms-turn-this-off-build-2004-11-12-2020.jpg39511-ms-turn-this-on-build-2004-11-12-2020.jpg



Microsoft should be fined mucho deniro $$$$ for messing with peoples' settings - it is not theirs, it is not their choices - it is mine - it is your choice - they should not be allowed to do this. It sucks because it is a HUGE WASTE OF MY TIME [and your time] when they do crap like this!!!

You may need to reboot your systems in order to make sure the permissions got reset to your new settings.

Hope this helps others!


·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KoenVerelstCORNER3ICT-5694 avatar image
0 Votes"
KoenVerelstCORNER3ICT-5694 answered ·

HI,

my problem on Windows 10, 1909
I alwasy used this script to map my share on a Synology. (Synology is already configured for SMB3.)

net use z: \\Nas ip\sharename /user:.\user Password

but this does not work.

neither in a command prompt

but when i do :
net use z: \\Nas ip\sharename
then the command prompt asks for a user and password and this maps my z-drive ????

i tested it on my machine (windows 10 enterprise 20H2) and it works fine just fine.

regards,

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.