
With the release of Windows 10 1909, users have noticed a annoying bugs related to the new search experience in File Explorer that was not present in the previous version of Windows 10.
For the most part, when the November 2019 Update, or Windows 10 1909, was released there have not been too many reports of new bugs compared to previous feature updates. This is because this feature update is more like a service pack that only adds a few improvement to existing features and resolves other bugs.
One of the new features added to Windows 10 1909 is the integration of Windows Search into File Explorer. This allows users to enter a keyword in the search field and Windows 10 will automatically populate it with suggested files based on your search keyword.

Unfortunately, users have started experiencing bugs [1, 2, 3, 4] in this new search experience that briefly hangs File Explorer, does not allow you to right-click and paste into the search field, and causes the search field to become unresponsive so that you cannot type anything.
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".
When the search field become unresponsive, users can shut down File Explorer and it will work again. After a while the issue may occur again, requiring another restart of File Explorer.
While BleepingComputer has not been able to reproduce these issues, those who are experiencing them say that they can fix the issues by uninstalling KB4517245 and reverting back to Windows 10 1903.
H/T Borncity.com

Comments
gmeades - 2 years ago
You only have 10 days to roll back to build 1903 after updating to 1909. If you dont notice problems within those 10 days, such as when updating a customers, a friends, or a family members PC, you may not be able to roll back to build 1903 should a problem be noticed as the Winows.old folder is deleted automatically after 10 days.
It would be nice if someone could update this article to notify us when a fix is available for this bug or if a fix is included within an update.to address this problem.