I assume the issue is poor decision making about rule conflicts. E.g., what's higher priority: Consistency, or exact-match? E.g. if "photo" auto-completes to "Photoshop", should "photos" auto-complete to "Photoshop" or "Photos"? I think it's "obvious" that consistency is more important here. If the user wants "Photos" despite opening "Photoshop" more often, let them configure the search explicitly to prioritize it, or allow them to select from a list of multiple matches.
And that's just a comparison against a single conflicting rule. Now imagine all the obscure rules they've implemented, for reasons varying from a misguided drive for "features" to nefariously pushing the user to click on what they want them to.
Regardless of what you want the behaviour to be, the behaviour shouldn't be, as it is on my system:
"pho" = Photos
"photo" = Photoshop
"photos" = Photos
And as I type this to confirm what happens after, now "photos" completed to photoshop, despite not selecting anything since the last time I typed it...
There is a good reason why I use either the Powertoys Run or Launchy on every system I touch.
I suspect it's even worse than this. It seems to be something along the lines of "oh you typed pho, and got photoshop, but then typed t, so clearly photoshop wasn't what you wanted, since we already suggested that"
That's the only way I can explain windows "flip between several app suggestions every time a new letter is typed" behavior
"Would you like to make edge your default browser ?" No !!
"3 results for termi - bing"
It doesn't sound annoying, but it means you often hit enter mid-typing, only for the top suggestion to change right as you are hitting enter.