just a quick question..... how many of you that are having explorer search bar issues, also have Office 365 Personal (or any version that includes outlook)? I noticed that windows 10 no longer includes the old style indexing service like was used in win 7 an older OS versions. but if you install outlook, it gets installed. and setup. 1909 does not appear to use it by default. it uses windows search instead. at least this was the case on my pc. I did not get indexing until i got office 365. also, I am using the version of Office 365 that is installed and updated via the windows store. though, i don't know if that would make any difference in this case.
File Explorer search not working in Windows 10 1909
Ever since I updated to Windows 10 1909 the Search Box in the File Explorer is completely unuseable. It shows a text cursor but I cannot click inside the box or type any text into it. Essentially it's a text box with no "wiring".
Any ideas how to resolve this issue? I'm having to resort to using a third-party search app just to find files in my projects.
Kind regards
Byron
Windows for home | Windows 10 | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
369 answers
Sort by: Newest
-
Anonymous
2020-01-24T18:45:44+00:00 -
Anonymous
2020-01-24T15:14:41+00:00 version 2004 build 19041.21 it's fine, for real - everything was fixed with File Explorer
-
Anonymous
2020-01-24T14:47:06+00:00 Captain Vilmer Potts: Next time the search tab is open, right click on the Kind icon and Add it to the Quick Access Toolbar. This does not, unfortunately, solve the frozen search box problem.
-
Anonymous
2020-01-24T14:20:00+00:00 You can use an alternative 3rd party program.
I use Explorer++, it has an interface similar
to that of File Explorer's.
You can google the web to find more alternatives.
-
Anonymous
2020-01-24T13:36:57+00:00 If the fix is not available to the user, it is NOT FIXED. In other words it will not be fixed until May - and that is far too long, as this string of posts suggests. I personally am not prepared to install an "insider" preview and become a guinea pig any more than I already am. None of the "workarounds" are acceptable. As far as the Microsoft programmers are concerned, the issue may be fixed - but as far as the rest of us are concerned it is not. If it really is fixed, MS should put it on the update server immediately.