mapped drive not visible in Windows Explorer (in the beginning)

Question

mapped drive not visible in Windows Explorer (in the beginning)

Kurt Stichelmans 661

Windows 10. When starting the pc it runs a script for creating some drives which points to a netgear nas.
The script works.
In command prompt it can connect to the added drives. e.g. m: shows content of that folder on the nas.
When opening Windows Explorer the m: is not shown and when I typ m: in the address bar it does not find the m:

After 5 minutes I look back at Windows Explorer and the m: is visible and accessible.

Extra: played with host file for the names, but using ip addresses the hostfile is not used. Played with SMB1 but not successful for the visibility in windows explorer, ....

What could be the reason?

Best regards
Kurt

Anonymous

2020-11-27T02:28:29.573+00:00

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

1.What's the OS version of your windows 10? 2004 or 20H2?

2.If you manually map the drive not via script, will the issue still occurs? Just narrow down if the issue is related with script.
Kurt Stichelmans 661 Reputation points

2020-11-27T15:10:06.767+00:00

1/ it is a W10 with the latest updates. So updates 'till half November.
2/ I said script, but it was in fact created in Windows Explorer. When the mapped drive M: becomes visible in Windows Explorer it wasn't accessible. Restarting the pc more than once showed the M: but it was not always accessible.

So we created the M: via command prompt with a simple "net use..../p". After that there is that issue of not seeing the M: in Windows Explorer for a long time (5 minutes). Waiting and waiting and.... and after a while it becomes visible and usable.
While the M: is created we can enter it via the command prompt without problems.

When we enter M: in the address bar of Windows Explorer we get an error; Cannot connect to M: (because it thinks there is no M:)
Anonymous

2020-11-30T07:16:21.693+00:00

Did you run the command using cmd with Admin rights?

Please also run sfc /scannow to repair any corrupted system files.
Derek Souter 1 Reputation point

2020-12-31T19:48:13.347+00:00

I have the exact same issue - I have three NAS storage devices (2 Linkstation LS-QVL, and 1 Netgear EasyNAS), with a script mapping drives to all of them at login.

two of them (1 Linkstation and the Netgear) work perfectly every time - the drive to the other Linkstation shows as mapped in command prompt (and is fully accessible from command line), but is not visible or accessible in Windows Explorer.

has only recently started happening, with no changes to the config on the NAS devices, or the script.

strangely, it doesn't happen on all my computers (I have 5 that logon and use the same script to map the drives), or all the time.

would love to know if there is any explanation for it.

Should also point out - that if I browse the network, and go to the NAS itself, I can see and access the shared folder without any issue - but mapping it from there to another drive letter also doesn't work.

1 answer

Your answer

Anonymous

2020-11-27T02:28:29.573+00:00

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

1.What's the OS version of your windows 10? 2004 or 20H2?

2.If you manually map the drive not via script, will the issue still occurs? Just narrow down if the issue is related with script.
Kurt Stichelmans 661 Reputation points

2020-11-27T15:10:06.767+00:00

1/ it is a W10 with the latest updates. So updates 'till half November.
2/ I said script, but it was in fact created in Windows Explorer. When the mapped drive M: becomes visible in Windows Explorer it wasn't accessible. Restarting the pc more than once showed the M: but it was not always accessible.

So we created the M: via command prompt with a simple "net use..../p". After that there is that issue of not seeing the M: in Windows Explorer for a long time (5 minutes). Waiting and waiting and.... and after a while it becomes visible and usable.
While the M: is created we can enter it via the command prompt without problems.

When we enter M: in the address bar of Windows Explorer we get an error; Cannot connect to M: (because it thinks there is no M:)
Anonymous

2020-11-30T07:16:21.693+00:00

Did you run the command using cmd with Admin rights?

Please also run sfc /scannow to repair any corrupted system files.
Derek Souter 1 Reputation point

2020-12-31T19:48:13.347+00:00

I have the exact same issue - I have three NAS storage devices (2 Linkstation LS-QVL, and 1 Netgear EasyNAS), with a script mapping drives to all of them at login.

two of them (1 Linkstation and the Netgear) work perfectly every time - the drive to the other Linkstation shows as mapped in command prompt (and is fully accessible from command line), but is not visible or accessible in Windows Explorer.

has only recently started happening, with no changes to the config on the NAS devices, or the script.

strangely, it doesn't happen on all my computers (I have 5 that logon and use the same script to map the drives), or all the time.

would love to know if there is any explanation for it.

Should also point out - that if I browse the network, and go to the NAS itself, I can see and access the shared folder without any issue - but mapping it from there to another drive letter also doesn't work.

Answer 1

SQx 101

Hello,

1) Could you please clarify if the power saving features of your NIC (network card) is disabled?

2) Please also clarify if you are using a third-party antivirus solution?

Kurt Stichelmans 661 Reputation points

2020-11-27T07:14:39.257+00:00
nic power: not enabled. So the system cannot turn the nic off.

the antivirus is: Trendmicro. But is also used on 10 other different desktops without an issue. But I know, not all pc installation are exact the same.
SQx 101 Reputation points

2020-11-28T01:39:35.057+00:00

Could you please clarify if the problem is stably reproduced in clean boot mode?

Share via

mapped drive not visible in Windows Explorer (in the beginning)

1 answer

Your answer