If you read one person's reply, you will see that they talked to Microsoft and according to them they could not duplicate this problem and there is not plan to fix it that I can see. [...]
That's one person's reply after that one person supposedly talked to one MS support person, who apparently said "not repro here". Sorry, I know for a fact that MS is aware of this issue, so that report you're talking about is something I immediately dismissed.
Low-level support techs will sometimes give disinformation (without their organization knowing).
When you compare that to the now multiple reports that the issue HAS been recognized and even fixed by MS (albeit not coming until the spring update), I can tell you which I'm hanging my hat on (the latter).
The work-around (killing/re-starting File Manager) is a PITA, but it means that this isn't a show stopper (total productivity killer). It just slows us down.
It's also TOTALLY annoying that they're just not RUSHING out a fix for us, but that's not how the MS Windows business model works these days (unlike older versions of the OS). Security updates (this not being one of those) happen more often in patches.
The quarterly updates (such as this) are something that we have to wait for because they have to test it with a whole lot of configurations, in conjunction with an ENTIRE WORLD of invested partners (all the hardware, all the drivers, all of the app suites,
all of the government and large corporate contracts, etc.).
Go ahead and change to another OS. I'm peeved about this issue, but I'm sticking around. This is just an annoying search bug in File Explorer with a fix on its way.
Chris
PS: threatening to change OS here is not going to be effective, even in the least bit.