[Run] Unable to find apps in other drive

[jyuwono]

Comment by @EdgarVaguencia from #3223

Doesn't find Code

Wox result:

the G drive is a partition, the different thing is that i don't create shortcut on start menu, but i add the path in environment variables

[sungwonida]

I have the same issue. Only files in drive C are showing up, not in drive D.
OS build:19041.329
PowerToys: v0.18.2

[jyuwono]

@sungwonida is your D:/ drive indexed? Getting files in other drive is a little different than getting programs. This issue is to track getting programs in another drive. For issue with files, we have #2041 to track it.

[sungwonida]

Ah, I thought as they were the same. I'm not sure D:/ drive is indexed. I'll follow #2041 and thanks for clarifying that for me.

[crutkas]

closing at dup against #2041

[crutkas]

sorry, got confused

[phileastv]

Hello !

I just installed PowerToys, for me it seems to work fine. I have 2 drives attached to my computer (+ C:), and the search is correctly made in all drives.

Here you see folders contained in drive S, K and C .

Maybe it's because I enabled the "Advanced" option in the newer Windows Search settings, you should try it.

Anyway, this PowerToys features is very promising. Finding files seems to work wayyy better than with the Cortana or Explorer search box (but not quite as fast as Everything does it).

(this is a paste from my reply from issue #4438 as it seems to be the same)

[novahreal]

Unfortunately, it seems that the "Searching Windows" section of Windows 10 settings where you actually index folders, there is no way to enable the indexer to search any network drives.

I have many network drives mapped, but they do not show up for me to even select them to index. Since most files I would want to search are in various network drives, it renders PowerToys Run much less effective than desired.

[crutkas]

@alekhyareddy28 shouldn't enhance search handle this then?

[alekhyareddy28]

@crutkas, the main issue should no longer exist because the user said they add the location to the path environment variable and we search those locations as well now.

However, the enhanced mode only indexes all drives on the PC. This is an article that I found on indexing a network drive https://www.google.ca/amp/s/www.online-tech-tips.com/windows-10/add-network-folder-to-windows-search-index/amp/.

[novahreal]

@alekhyareddy28

However, the enhanced mode only indexes all drives on the PC. This is an article that I found on indexing a network drive https://www.google.ca/amp/s/www.online-tech-tips.com/windows-10/add-network-folder-to-windows-search-index/amp/.

From the above linked article, it states the following:

If you click on Start and type in indexing options, you’ll see that the mapped network drive location is not listed nor can it be added. Basically, it’s performing the search in real-time, which is why it’s going to be slow if you have a huge number of files on your network share.

As @crutkas has previously mentioned in #3694 (which is now closed):

at end of the day, this is issue #2041. If the drive isn't indexed, we can't search it

So with all the above in mind, this unforunately means that it is completely impossible to find apps in mapped network drives. If the mapped network drive isn't indexed, PowerToys Run can't search it, but mapped network drives are not listed in indexing options nor can they be added.

Unfortunately, this completely defeats the purpose of PowerToys Run (for me at least) which was the main draw and most exciting feature of PowerToys IMO. My company deals with many files on a daily basis that all live in network drives.

[novahreal]

@alekhyareddy28 closed?

[alekhyareddy28]

@novahreal, the main issue of apps being added to the path environment variable locations (drives other than C:) has been solved and now apps added say to some location in the E: drive through the path env variable will show up.

We unfortunately still don't support network mapped drives. @crutkas do we want to call that out somewhere?

[novahreal]

@alekhyareddy28 @crutkas

Thanks for the clarification, I thought this issue was for any drives (local or network) - it seems the issue for mapped network drives is open but not being worked on.

@crutkas do we want to call that out somewhere?

it seems this is the issue that relates most to network drives, but it isn't assigned to any projects.
#4544