# Mapped Network Drives Refuse to Index? **URL:** \ **Category:** Help\ **Created:** [July 20, 2023, 5:55pm UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469 "2023-07-20T17:55:16Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![tomgiorgio](https://discussion.listary.com/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomgiorgio](https://discussion.listary.com/u/tomgiorgio)\ **Post date:** [July 20, 2023, 5:55pm UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/1 "2023-07-20T17:55:17Z")
I have a mapped network drive and it doesn’t seem to want to index. I added it to the index list but it always says last index was Never. When I tell it to manually index by hitting Update Now it _says_ it’s indexing but it says it’s finished within 30 seconds which I’m skeptical of because there is a _ton_ of stuff in that drive. ![image](https://discussion.listary.com/uploads/default/original/2X/7/74ed355f321c5dac5c7b5f21e2df09e16bfe6b08.png) No matter how many times I have it update or what I set the interval to, it always says Last Updated is never. I saved this as a draft because after writing it I realized that the network drive _did_ seem to be indexed, but after rebooting my PC it seems to no longer by indexed anymore. So it seems like I lose the index whenever I reboot and I have to manually re-index? ---
**Author:** ![tomgiorgio](https://discussion.listary.com/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomgiorgio](https://discussion.listary.com/u/tomgiorgio)\ **Post date:** [February 19, 2024, 3:51pm UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/2 "2024-02-19T15:51:55Z")
Update on this, I have a network drive that says the index was rebuilt 1 minute ago but I get zero search results for it. I can type folder:foo and it finds nothing except things on my C drive. ---
**Author:** ![Nuno\_Marques](https://discussion.listary.com/user_avatar/discussion.listary.com/nuno_marques/32/2894_2.png) [@Nuno\_Marques](https://discussion.listary.com/u/Nuno_Marques)\ **Post date:** [March 29, 2024, 12:57am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/3 "2024-03-29T00:57:30Z")
I purchased pro specifically for this and have found that it doesn’t work. There are other threads in here complaining about the same and so far, no word from the dev. I have emailed support asking for a refund. Not a word in response. Seems like I spent 20 bucks for nothing. ---
**Author:** ![109468](https://discussion.listary.com/letter_avatar_proxy/v4/letter/1/b487fb/32.png) [@109468](https://discussion.listary.com/u/109468)\ **Post date:** [March 29, 2024, 6:07am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/4 "2024-03-29T06:07:00Z")
教你个办法，先删除现在索引的保存好，然后重装当前版本的软件，在添加需要索引的，在保存就好了 ---
**Author:** ![Cede](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/b487fb/32.png) [@Cede](https://discussion.listary.com/u/Cede)\ **Post date:** [November 19, 2024, 8:45am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/5 "2024-11-19T08:45:26Z")
Ok, i am experiencing the same issue. I have been using the latest Listary v6 as well as the Beta and external network drives i mapped do not get index. i have the same issue as described above. It shows up as “indexed never”. There is one thing i noticed though, its not ideal, and i hope to find a solution for the actual issue, but it seems you can make it work if you index not the mapped drive letter, but the network path instead. So i have a drive, P:, this is mapped to //nas-server/projects If i add P:\ to listary, it does not index it. If i add //nas-server/projects, it does. The only issue i have is that, if i use it to open files, it also opens it following the //nas-server/projects/ file path, which is actually a problem because i mapped it to P:/ for a reason because i do the same for other PCs, where P is mapped to another folder. So while it works on one PC, this workflow is causing problems for me and my specific workflow when i open edited files on another computer where P: is mapped to another drive location. So i would still love to have a solution for that if possible. Maybe with this hint, its easier to find the issue and fix it. Very much appreciated! ---
**Author:** ![horst](https://discussion.listary.com/letter_avatar_proxy/v4/letter/h/edb3f5/32.png) [@horst](https://discussion.listary.com/u/horst)\ **Post date:** [November 19, 2024, 10:59am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/6 "2024-11-19T10:59:30Z")
Windows Drive mappings are user related. So Listary may not see your drive P: There is a registry setting which makes them global. ---
**Author:** ![Cede](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/b487fb/32.png) [@Cede](https://discussion.listary.com/u/Cede)\ **Post date:** [November 19, 2024, 11:15am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/7 "2024-11-19T11:15:25Z")
Well it was previously working on the same machine using Listary V5 so i would assume its possible. But if you know by any chance what these registry settings are i would give it a try. ---
**Author:** ![horst](https://discussion.listary.com/letter_avatar_proxy/v4/letter/h/edb3f5/32.png) [@horst](https://discussion.listary.com/u/horst)\ **Post date:** [November 19, 2024, 11:55am UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/8 "2024-11-19T11:55:59Z")
Read this Microsoft page [https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command](https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command) ---
**Author:** ![xinyi](https://discussion.listary.com/user_avatar/discussion.listary.com/xinyi/32/4673_2.png) [@xinyi](https://discussion.listary.com/u/xinyi)\ **Post date:** [November 19, 2024, 3:48pm UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/9 "2024-11-19T15:48:59Z")
Please try the latest V6.3.1.83 beta version. This update should resolve all bugs related to network drives and mapped network drives. [https://discussion.listary.com/t/v6-3-1-83-beta-released-major-custom-index-and-stability-enhancements/9405](https://discussion.listary.com/t/v6-3-1-83-beta-released-major-custom-index-and-stability-enhancements/9405) ---
**Author:** ![Cede](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/b487fb/32.png) [@Cede](https://discussion.listary.com/u/Cede)\ **Post date:** [November 19, 2024, 5:15pm UTC](https://discussion.listary.com/t/mapped-network-drives-refuse-to-index/8469/10 "2024-11-19T17:15:17Z")
Thanks for the info. I was actually under the impression i am using the latest beta as i was auto updating and just updated this morning via the auto update, but the latest beta that got installed was V6.3.1.81 So i manually installed it, now it seems to work and actually scan my network drive as usual. Thanks!