Listary Pro 4 don't work with mapped Network Drive

Listary Pro 4 don’t work with mapped Network Drive

Sorry that Listary can’t support mapped network drives :frowning:

Channing, that is really disappointing, as version 3 had no such limitation. Most files accessed by our small office (3 licences) are on a shared NAS, mapped as Drive ‘Z:’ on all PCs. I note that if we access the same files via the network, (eg \SERVER01\DriveZ\folders…), Listary does work OK and allows instant access to folders. However, that’s not a lot of use, as access is regularly via the mapped drive.

Effectively we can’t use Listary version 4 unless this capability is returned. Perhaps you could explain whether this can be fixed, before we decide to revert to version 3…

It turns out this problem has nothing to do with Listary. Please check this link for a fix:

Hmmm, thanks Microsoft!
You are quite right Channing, that seems to have fixed the issue. Windows Administrator mode is a constant source of confusion, and MS’s unsupported workarounds don’t improve the situation!
Even so, thanks for pointing this out, Channing, Listary now works as it should.

BillB said:
Listary now works as it should.

@BillB, can you explain what you did to resolve the issue? I am having the same problem and running the “net use” command as explained in the MS article hasn’t changed anything. I’m probably missing a step somewhere.


Well, first of all, I couldn’t remember what I did, and looking at the link to didn’t help - I don’t remember doing anything with the ‘net use’ command.
Then I found some notes I made at the time, which I think I copied from that same webpage - but which do not appear to be there any more (thanks again, MS).

So, this is what I think I may have done. Obviously this is at your own risk and not guaranteed.

After you turn on User Account Control in Windows Vista or in Windows 7, programs may be unable to access some network locations. This problem may also occur when you use the command prompt to access a network location.

Unsupported registry hack:

To configure the EnableLinkedConnections registry value, follow these steps:

Click Start, type regedit in the Start Search box, and then press Enter.
Locate and then right-click the following registry subkey:
Point to New, and then click DWORD Value.
Type EnableLinkedConnections, and then press Enter.
Right-click EnableLinkedConnections, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor, and then restart the computer.

Hope that helps. UAC is closer to voodoo than computing to me!


Because this issue is caused by UAC, if you’re using the latest version of Listary, you can try to go to Listary Options - General, uncheck “Run as administrator”, and then reboot your computer.

Thanks @BillB and @Channing. Since I’m running Listary Pro on a work computer, I didn’t want to disable UAC or make any registry changes. So I followed Channing’s advice and it works! I still have to click “Yes” to the UAC prompt when Listary starts; but that is something I can live with now that my mapped network drives are back!


If you’re using the latest installer version of Listary, there should be no UAC prompt. I suggest you to try to reinstall Listary.


Perfect! I had been using the portable version.


Unfortunately when I run Listary 4.02.1360 search and projects do not work on mapped network nor on UNC paths. Running as admin seems to have no effect, no difference.

OS is Win7. UAC is on.

Any help? Thx in advance.

Regards, Stephan


Sorry that currently search and projects don’t support mapped network drives.

Thx for ansering Channing,
Will it be possible in the near future (with Listary) or do I have to keep my eyes open for another solution?
Regards, Stephan


I already have it on my to-do list, but it’s very complex to implement and will really take some time.

I hope for this because in commercial usage you mostly have network drives.

I have a good news: this feature will be available next week.