Win10 version 1909 File Explorer search box still buggy — but less so

[Karlston]

Win10 version 1909 File Explorer search box still buggy — but less so

So you thought the latest “optional, non-security, C/D Week” patch for Win10 version 1909, KB 4532695, fixed the long-standing File Explorer Search bugs?

 

Think again.

 

As mentioned earlier, Rafael Rivera picked up more anomalies:

• You can left or right click inside the File Explorer Search box. But if you want to right-click, you must first left-click.
• It takes two clicks at times to reset the caret position
• You can’t delete items in the “remembered” list

Mayank Parmar, over on Windows Latest, has a GIF of the clicking caret bug. Here’s what he says:

File Explorer’s unified search experience is still a mess and it looks like things won’t get better until Windows 10’s 20H1 update is out. Microsoft has yet to acknowledge the new problems with Explorer and there don’t appear to be any workarounds. If you have installed Windows 10 November 2019 Update, you have to accept the possibility of experiencing issues with File Explorer and Control Panel.

A note from the peanut gallery: Microsoft never did acknowledge the problem, except to explain that they fixed “an issue that prevents File Explorer’s Search Bar from pasting clipboard content using the right mouse button (right-click)” and “an issue that prevents File Explorer’s Search Bar from receiving user input.”

 

The Release Status Information page still stays exactly squat about the bug.

 

 

Source: Win10 version 1909 File Explorer search box still buggy — but less so (AskWoody - Woody Leonhard)

[Guest]

yeah, that issue still not fixed even after the new optional update.
 

13 hours ago, Karlston said:

File Explorer’s unified search experience is still a mess and it looks like things won’t get better until Windows 10’s 20H1 update is out. Microsoft has yet to acknowledge the new problems with Explorer and there don’t appear to be any workarounds.

I guess Microsoft will force them to upgrade to the 20H1 when it's released, to fix that bug.