Wow... So i'll hold v1903 until that.
Thank you.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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.
Wow... So i'll hold v1903 until that.
Thank you.
Good afternoon. Any updates regarding this issue in build 1909?
Yes, scroll the thread above to see comments regarding the fix, which will be released in the spring update (probably in May).
Chris
Good afternoon. Any updates regarding this issue in build 1909?
I had installed this version by the official ISO (clean install) but due to this problem that, for me, is very annoying, I had to reinstall build 1903.
Does the problem persist or has Microsoft fixed it?
The issue (for me at least) appears to be with the Microsoft Co-Editor Executable which is part of OneDrive, the file is called FileCoAuth.exe. I installed the Windows 10 2004 preview to try to fix this issue and when I went to search again in Explorer it was still blocked, but as soon as I tried to click in the search field my firewall notified me that FileCoAuth.exe wanted to access the network and as soon as I allowed it the Explorer search started working. (I have my firewall setup to ask me anytime something wants to access the internet).
So maybe there is a solution to this bug without having to install the 2004 preview. First thing I would try is creating a firewall rule to give FileCoAuth.exe full internet access privelages and make sure a rule wasnt accidentally created to block it from the internet.
Sighman1975 of course the issue is if the code quality for RTM builds is so poor that file explorer search doesn't work what other tragedies await the user in preview builds?!
rant/ Sadly, if they can't get their <removed> together for gold releases the chances of hitting a data loss bug are far too high for my risk tolerance. Remember how long it took them to fix the showstopper bug in 1808? It was so long, the build should have been renamed 1811! <g> Once they embraced Agile development which entailed firing all the SDETs whose sole job was to break the builds and file bugs the quality of Windows client plummeted. /rant