Page 1 of 1

mapped Network drive only appears if open File Explorer

Posted: 20.11.2017, 18:44
by coyote
My mapped Network drive now only appears if I first open File Explorer.

This is a new issue after months when all was well.

FreeCommander XE 2017 Build 740 32-bit
Windows 8.1 Pro32bit

Re: mapped Network drive only appears if open File Explorer

Posted: 11.12.2017, 21:18
by coyote
Oh!
I see that FC can see the mapped Network drive immediately IF the mapped Network drive is connectible when I first start Windows 8.1

My Win 7 machine doesn't have this issue (nor did this PC until last month).

Image

Re: mapped Network drive only appears if open File Explorer

Posted: 20.02.2018, 16:35
by coyote
Bump please?

p.s. same behavior with FreeCommander XE 2018 Build 771 32-bit donor

Re: mapped Network drive only appears if open File Explorer

Posted: 20.02.2018, 18:54
by m-a-r-k
Are you running FreeCommander with Administrative privileges? Is it Elevated?
If so I have a probable fix.
Run RegEdit and go to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System and create a new DWORD entry with the name EnableLinkedConnections and value 1:
After you’ve added the EnableLinkedConnections value to the Registry, restart the computer, and after that the network drives you create should become available to the elevated applications, as well.
Worked for me in Windows 10.

Re: mapped Network drive only appears if open File Explorer

Posted: 10.06.2019, 07:36
by CrocNZ
"Are you running FreeCommander with Administrative privileges? Is it Elevated?
If so I have a probable fix.
Run RegEdit and go to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System and create a new DWORD entry with the name EnableLinkedConnections and value 1:
After you’ve added the EnableLinkedConnections value to the Registry, restart the computer, and after that the network drives you create should become available to the elevated applications, as well.
Worked for me in Windows 10."

I'm sure I could do that if I had any idea what any of it meant. I got on very well with DOS, but less and less with each version of Windows until Windows 10 has become by a country mile the least reliable and slowest operating system I have ever had the misfortune to use. Sometimes it is even slower than the punchcards I used to laboriously type out on the old University IBM machine, which was installed in a room the size of a house...

In particular could you please explain Elevated and DWORD. I know how to get into RegEdit, I think. I'd like a very much more detailed version of the rest, please. I learned 45 years ago just how easy it was to bring a whole operating system to a halt with just one misplaced keystroke!
And why would the passage of time have anything to do with FreeCommander being unable to see the other computer on the network? It always used to work fine. Now even the horrible File Explorer can't see it most of the time.

Re: mapped Network drive only appears if open File Explorer

Posted: 15.06.2019, 08:59
by CrocNZ
I've tried to post an update to this several times now, over several days, and failed totally. Even failed to save the update as a draft - so here goes again…

I’ve found a workaround. By chance a couple of days ago, Windows Explorer could find the network computer, although FreeCommander could not. I was able to copy the address, the path, from Windows Explorer and paste it into the FreeCommander path line. (In this case it is \\OEM-7F16980A779, which must have been the name of that refurbished ex-lease computer when I bought it some years ago.) Then I could synchronise files and folders between the two computers. I have recorded this address path and I’m hoping that I can use this technique to find that computer again...