No wonder it’s so buggy … that’s way too much unnecessary technology to render a drop-down list. JavaScript is used to render the filtered search results.
Which sure looks like a JavaScript smoking gun to me.
Only the UI is different.Īs he pushed on his system, he triggered a compilation error (screenshot). The search box on the Task Bar, and in Windows Explorer, both load C:_(version)SearchApp.exe when you click on them. This of course means that some kind of web rendering engine is required … it’s probably Edge.įurther exploration put the pieces together: I did a little digging around I think I figured out why … the entire search box is now a web application built with JavaScript & React. Click on the Search box and it immediately consumes 120+ MB of memory on my machine. What really sticks out for me with some of these newer Search versions, is that they use a ton of memory. It just broke, all by itself.įor a more detailed explanation, specifically for Win10 version 1909, I’ll refer to on AskWoody :
You didn’t give Microsoft permission to break Search. Microsoft reached into your Win10 PC overnight and screwed up its search function. The top-level answer is pretty simple: You didn’t do anything wrong.
