Why must I index Network drives in order to include them in Libraries?


  1. Posts : 81
    Windows 10 Pro x64 (Version 22H2, Build 19045.2965)
       #1

    Why must I index Network drives in order to include them in Libraries?


    Please excuse this rant, but I need to let off some steam. I have just run into the error message, "this network location can't be included because it is not indexed" while trying to add a mapped network drive to a library. My use case is quite similar to that described in Brink's (as usual) excellent tutorial, except that I have offloaded my public folders to my NAS. It is very convenient to access these folders via libraries, as described in the tutorial, but they take a lot of space and I don't need them on my laptop. Because of their size, it would likely cause problems to index them. IAC, I don't want or need them indexed. I am quite satisfied with the search speed in these volumes as it is. Why does Windows want me to index them? Is there no way to include unindexed directories in libraries?
      My Computer


  2. kit
    Posts : 14
    win10.1809
       #2

    Last time I checked when looking at Libraries, you cant even index mapped network drives in win10 except maybe with sym links. :)
      My Computer


  3. Posts : 14,029
    Win10 Pro and Home, Win11 Pro and Home, Win7, Linux Mint
       #3

    The only issue I have with my NAS drives is first access after booting a computer, File Explorer has to 'read' the drives folders and files. Using MultiCommander is faster.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:13.
Find Us




Windows 10 Forums