question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error Typing ANYTHING When Explorer Plugin Enabled- error due to windows index

See original GitHub issue

Checks

  • I have checked that this issue has not already been reported.

Problem Description

Trying to type any characters at all into Flow Launcher results in the error below after updating to 1.10.0, had no issues on previous versions. Re-opening with my hotkey Ctrl+Space opens it with that character still typed, and typing another character results in the same error again. Disabling the Explorer Plugin let’s my WebSearch and other things work as expected.

Flow Launcher version: 1.10.0 OS Version: Microsoft Windows NT 10.0.19045.0 IntPtr Length: 8 x64: True

Python Path: Date: 12/13/2022 01:36:35 Exception: Explorer Exception: Websites: https://github.com/Flow-Launcher/Flow.Launcher Author: Jeremy Wu Version: 2.0.0 Flow.Launcher.Core.ExternalPlugins.FlowPluginException: Invalid URI: The Authority/Host could not be parsed. —> System.UriFormatException: Invalid URI: The Authority/Host could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind, UriCreationOptions& creationOptions) at System.Uri…ctor(String uriString) at Flow.Launcher.Plugin.Explorer.Search.WindowsIndex.WindowsIndex.ExecuteWindowsIndexSearchAsync(String indexQueryString, String connectionString, CancellationToken token)+MoveNext() in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\WindowsIndex\WindowsIndex.cs:line 56 at Flow.Launcher.Plugin.Explorer.Search.WindowsIndex.WindowsIndex.ExecuteWindowsIndexSearchAsync(String indexQueryString, String connectionString, CancellationToken token)+MoveNext() in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\WindowsIndex\WindowsIndex.cs:line 48 at Flow.Launcher.Plugin.Explorer.Search.WindowsIndex.WindowsIndex.ExecuteWindowsIndexSearchAsync(String indexQueryString, String connectionString, CancellationToken token)+MoveNext() in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\WindowsIndex\WindowsIndex.cs:line 48 at Flow.Launcher.Plugin.Explorer.Search.WindowsIndex.WindowsIndex.ExecuteWindowsIndexSearchAsync(String indexQueryString, String connectionString, CancellationToken token)+MoveNext() in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\WindowsIndex\WindowsIndex.cs:line 48 at Flow.Launcher.Plugin.Explorer.Search.WindowsIndex.WindowsIndex.ExecuteWindowsIndexSearchAsync(String indexQueryString, String connectionString, CancellationToken token)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult() at Flow.Launcher.Plugin.Explorer.Search.SearchManager.SearchAsync(Query query, CancellationToken token) in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\SearchManager.cs:line 102 at Flow.Launcher.Plugin.Explorer.Search.SearchManager.SearchAsync(Query query, CancellationToken token) in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Search\SearchManager.cs:line 102 at Flow.Launcher.Plugin.Explorer.Main.QueryAsync(Query query, CancellationToken token) in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\Main.cs:line 62 at Flow.Launcher.Core.Plugin.PluginManager.<>c__DisplayClass22_0.<<QueryForPluginAsync>b__0>d.MoveNext() in C:\projects\flow-launcher\Flow.Launcher.Core\Plugin\PluginManager.cs:line 191 — End of stack trace from previous location — at Flow.Launcher.Infrastructure.Stopwatch.DebugAsync(String message, Func`1 action) in C:\projects\flow-launcher\Flow.Launcher.Infrastructure\Stopwatch.cs:line 40 at Flow.Launcher.Core.Plugin.PluginManager.QueryForPluginAsync(PluginPair pair, Query query, CancellationToken token) in C:\projects\flow-launcher\Flow.Launcher.Core\Plugin\PluginManager.cs:line 213 — End of inner exception stack trace — at Flow.Launcher.Core.Plugin.PluginManager.QueryForPluginAsync(PluginPair pair, Query query, CancellationToken token) in C:\projects\flow-launcher\Flow.Launcher.Core\Plugin\PluginManager.cs:line 213 at Flow.Launcher.ViewModel.MainViewModel.<>c__DisplayClass120_0.<<QueryResults>g__QueryTask|2>d.MoveNext() in C:\projects\flow-launcher\Flow.Launcher\ViewModel\MainViewModel.cs:line 740 — End of stack trace from previous location — at Flow.Launcher.ViewModel.MainViewModel.QueryResults() in C:\projects\flow-launcher\Flow.Launcher\ViewModel\MainViewModel.cs:line 741 at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

To Reproduce

  1. Launch Flow Launcher
  2. Enable Explorer Plugin
  3. Open Flow Launcher with hotkey
  4. Try to type anything…

Screenshots

No response

Flow Launcher Version

v1.10.0

Windows Build Number

10.0.19045.2311

Error Log

2022-12-13.txt

Issue Analytics

  • State:closed
  • Created 9 months ago
  • Comments:15 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
VictoriousRaptorcommented, Dec 14, 2022

Hi there,

I found the same behaviour with Explorer plugin enabled (just the stacktrace is different) when I tryed to type anything (error happened on first letter). See the stacktrace and log attached.

But, enabling the Explorer plugin and changing options “Index Search Engine”, “Content Search Engine” and “Directory Recursive Search Engine” from value “Windows Index” to “Everything” (another search tool), Flow Launcher it is working fine.

image

I have turned off Windows Search services a month and everything related a month ago (was using too much CPU and wasn’t so good to justify that). So, based on observed behavior, looks like that issue is related to Windows Search service being down, off or something like this.

Cheers!

Flow Launcher 1.10.0

Windows 11 Home Version 22H2 Installed on ‎11/‎05/‎2022 OS build 22623.1028

stacktrace.txt

2022-12-13 - Copy.txt

Seems like your issue is related to #1628 , which is a bit different.

0reactions
taooceroscommented, Dec 17, 2022

Hi, In 1.10.0 search typing enviroments variables does reply nothing usefull. Sample

%appdata%
%tmp%

etc. 1.9.5 works great.

It will be addressed soon

Read more comments on GitHub >

github_iconTop Results From Across the Web

Can't Type in Windows Search Bar? Try These 15 Fixes
1. Restart Windows Explorer · 2. End Windows Search and Cortana Processes · 3. Restart the Windows Search Service · 4. Restart Your...
Read more >
Troubleshoot Windows Search performance
This article discusses common performance issues that affect Windows Search and Search indexing. If you observe general poor performance ...
Read more >
How To Fix File Explorer Search Box Not Working
If you are using Windows and the search box in File Explorer doesn't seem to be working, follow these steps to fix it!...
Read more >
Windows 10 Indexing Is Not Running? Useful Ways for You
You can fix the Windows indexing issue by enabling LocalState folder permissions. Do the following steps to make sure the folder permissions ...
Read more >
[Solved] File Explorer Search Not Working in Windows 10
Fix 1: Restart File Explorer; Fix 2: Make Sure Windows Search Service Is Enabled; Fix 3: Change the Search Options; Fix 4: Allow...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found