Windows 10: Drive missing in "This PC" but still works fine in command prompt

This problem is usually fixed by slow solutions such as restarting my PC. But I run into this every day, so I need a better solution. I have a Buffalo NAS (network hard drive). I have to keep that at Auto-on mode because it's noisy. So everytime I want to turn the drive on, I need to wake it up with a network wake-on-lan command. That works fine.

The problem is, sometimes, due to sleep/resume etc. the drive just disappears from "This PC" (or My computer). If this happens, my drive x: still works perfectly in a command prompt. I connect to the drive with net use x: \\LS-WSXL64F\share /persistent:yes and that works usually. But sometimes only command prompt sees the drive and Explorer says "Windows can't find X:". At the same time "This PC" does show "LS-WSXL64F: LinkStation" which is a server version of the drive. It has some funny folders in it and is useless, I need the real x: drive which has my own folder structure. So Explorer does have connection to the drive, but X: is dead and I can't revive it even with "net use x: /delete" and then the previous net use x: \\LS.. For command prompt the net use commands work perfectly but not for Explorer. Explorer has "Map network drive". As a slow solution, I can remap successfully, but I just want to force and refresh the same mapping always, regardless of if the drive is physically off sometimes (which adds to the problem).

How do I force Explorer to recognize the same drive as command prompt recognizes?

Why is "net use" disconnected from "Map network drive"?

Is there a possibility for a shortcut for the "Map network drive" with all parameters included?

:)

 

my phone " keys in " some numbers while talking

As I said in my first post you can either try to update it's software to see if it cures it.

If it doesn't then your phone is faulty and you will need to get it repaired.

 

" Nokia Simple " theme - where it this theme?

hi,

Some days ago on page
http://ea.mobile.nokia.com/content/spin/ea/6120c/en/theme/index.xhtml or in phone (nokia 6120c) themes/general/download themes/ was very cool theme (light cream white, black fonts) " Nokia Simple ", now its dissapear from this site. Where i can get it?
or maybe somebody has it and could send to me.

thx

 

This does seem a common problem with drive mapped to a network share, particularly for business networks where the server may drop the connection if idle for too long. The connection is re-established if you access it from the command prompt, but in Win10 File Explorer doesn't seem to be able to recognise that the drive has returned. In Win7 apparently it did.

I don't have a permanently mapped drive letter to my network drive, preferring to access it without the need for a drive letter in File Explorer through Network > Device_name > Share_name. In fact, for ease of access I have that pinned to my Quick Access in File Explorer.

If, while your File Explorer can still see your X: drive, you pinned it to your Quick Access, then a click on the pinned X: drive may well 'remind' File Explorer that, yes, it does have X: mapped after all.

 

You should be able to see this drive by going to Start/Search or by pressing the Windows Key+R and typing \\ComputerName

 

Thanks alot! This helped me to get this far:

It seems that indeed in Windows 10 "Map network drive" (explorer and network drive recognition) and command prompt (net use) are not in complete sync with eachother. I can partially refresh the drive in explorer by going to \\LS-WSXL64F\share – then explorer recognizes X:. For "This PC", I have to press F5 to refresh and see a functional X: there. However, F5 does not refresh the left side (Quick access). It still looks like it's disconnected. But by clicking, it works and changes to connected icon.

For the command prompt side, first I have to make sure drive is connected by navigating explorer to \\LS-WSXL64F\share . That is probably the same as Run or I can also do the same with AutoHotkey's "DriveGet, oVar, Status, \\LS-WSXL64F\share" and "If oVar <> Ready" will then tell whether it connected. Then I can do "net use x: /delete" and "net use x: \\LS-WSXL64F\share /persistent:yes" and finally I have to do something like "%comspec% /c x:" to refresh x: so that it's also ready without a delay later on.

So, it almost works for me now, however I can't fully get the explorer icons automatically refreshed. They may have the red crosses at the left side even the drive is already connected and F5 is pressed to refresh.