Flow-Launcher / Flow.Launcher

:mag: Quick file search & app launcher for Windows with community-made plugins
https://flowlauncher.com
MIT License
8.28k stars 317 forks source link

Flow stopped working with Windows 11 Home (64 bit) #1767

Closed raindropsfromsky closed 1 year ago

raindropsfromsky commented 1 year ago

Checks

Problem Description

Till last week, I was using Flow and Everything on my laptop that ran on Windows 10 Home.

Last week my laptop OS crashed. My Acer Authorized service center upgraded Windows to Win 11 Home, 64 bits. I had to re-install all the apps afresh.

But after the upgrade, now I am having problem with Flow: It simply does not show ANY results!

My internal hard disk has a non-Windows partition. In addition, I have connected four external HDDs. But Flow is unable to find anything from any of these drives.

In the same set up, Everything works fine: It shows results from all my drives. Therefore I am concluding that file indexing is working fine in Windows 11.

I tried the Portable version of Flow, but that does not work, either!

What could be wrong?

To Reproduce

  1. Install Flow and run.
  2. Check out existing files in the drives and search word(s) from their names
  3. Expect Flow to discover these files
  4. Actual result: Flow fails to "discover" even these known test cases.

Screenshots

No response

Flow Launcher Version

v1.11.0

Windows Build Number

Version 10.0.22621 Build 22621

Error Log

```shell Replace this line with the important log contents. ```
taooceros commented 1 year ago

Please upload some log. I am using win11 as well and cannot reproduce what you are experiencing.

Is flow showing 0 result or only programs are not showing? (for example do 1+1 works? )

raindropsfromsky commented 1 year ago

Formula works fine.

Error log is attached. 2023-01-08.txt

raindropsfromsky commented 1 year ago

image This is just an example: I have tons of files that have the "dataviz" word in their name. But Flow fails to discover any of them.

z1nc0r3 commented 1 year ago

Make sure you have selected Everything as the search engine is the Explorer plugin.

image

And also, please try searching by considering the case of the word. I have experienced that sometimes Everything is case-sensitive (no idea why).

raindropsfromsky commented 1 year ago

I changed all three options to "Everything", but that has not restored the performance.

BTW I suspect that there are two separate installations of Everything on my laptop: A plugin within Flow, and a stand-alone version that I installed separately (I downloaded Everything and installed it manually).

z1nc0r3 commented 1 year ago

Everything plugin is now part of Explorer plugin (remember to remove the existing standalone Everything plugin if installed)

From FL v1.10.0, Everything is integrated into FL. So no need to install the plugin. Please uninstall the Everything plugin and try.

raindropsfromsky commented 1 year ago

I uninstalled the stand-alone version of Everything, and launched Flow once again. To my surprise, Flow reported that Everything service is not running, and then offered to install it automatically.

image (Which proves your point that it is not a "plugin" within Flow, but a "service".)

But even after installing the Everything service, the same error message continues to appear.

taooceros commented 1 year ago

You need to run everything to use the plug-in.

z1nc0r3 commented 1 year ago

You have to install the Everything desktop application and uninstall the plugin that was installed through FL. You can find it in FL Settings > Plugin

taooceros commented 1 year ago

Oh I guess I misunderstood your issue. So now the everything plug-in is not working but the program plug-in is still working?

raindropsfromsky commented 1 year ago

Oh I guess I misunderstood your issue. So now the everything plug-in is not working but the program plug-in is still working?

No I was tinkering with Flow while waiting for response here. I may have found an issue during such random experiments: In my old installation, I had increased the max results to 15. After my OS crashed, my fresh installation had a max results of 5. This limit is reached even before Flow starts showing files and folders! (For example, the first few entries are about Google search, etc. See the screenshot I have posted above!)

So while tinkering with the settings, I increased the max results to 15, and now I am able to see the results.

taooceros commented 1 year ago

I think there's consistency issue with the settings when system crash. We are trying to fix it in #1763. Just to let you know, you can scroll the result down and see further results.

raindropsfromsky commented 1 year ago

...you can scroll the result down and see further results.

Actually, this did NOT happen!

I was actually expecting FL to display x entries at a time (where x is a selectable number in the range 5-15). That means I should be able to see the rest of the results by scrolling down. But that did NOT happen when the default count was 5 in my fresh installation. (You can see that in both my screenshots in this thread, there is no scrollable list at all.)

So there is some issue with the display. When I changed the count to 15 (the max allowable in the settings), FL started showing more results. That's not normal.

Although this behavior has a bug, I am not able to catch a pattern.

jjw24 commented 1 year ago

@raindropsfromsky it sounds like the original issue is Explorer not the everything service that's why you are seeing the warning. Is this still an issue?

I have been using max results displayed at 5, not able to reproduce what you mentioned in the above comment. When you increase to 15 and see the results, can you then decrease to 10 and see if you can still scroll through all the results, then try 5.

raindropsfromsky commented 1 year ago

I changed the settings to 10 and then again to 5. But now FL works fine consistently. AFAIK nothing has changed!

But if you see my screenshots above, you will clearly see that the problem did exist. (The scroll bar is large or non-existent, which means that there are very few results, or no results at all.)

But since there is no consistency, we should probably close this bug...