I have no idea why or how the build changed. You can see the build number on your own Win10 machine by clicking once inside the Search box, then clicking the three dots in the upper right corner. After rebooting, the build number for the Search box increased from 2020.928 to 2020.943 (screenshot). I saw the behavior on my main machine this morning. Apparently Microsoft updates the Search bar without asking for permission. That sparked a discussion that culminated in a revelation that’s news to me. The search bar is still finding my local files, etc., the behavior is the same (as far as I can tell), but the text has changed and it’s bugging me. I’ve compared the search and Cortana settings on both systems for any differences, and I can find none. On the other computer, the search bar now has the text “Start a web search” On one computer, the search bar has the text, “Type here to search,” which I believe has always been the default text in the box. Running two systems side by side, both Win 18363.628 (all patches, including the ones released this week). One is a Precision T3500, the other is a Latitude E6530.Over the weekend, Howard Goldberg reported a startling change in his Win10 Search bar: I would think there's some common hardware between the two, but aside from being older Dell machines, I've not found any. And the other PC just launches a browser for my PRTG dashboard (map) I keep running in my office - and all of that works fine. The laptop is just a test machine, we can easily reimage. In fact, the laptop ended up with the same text rendering problem. I also tried mounting the ISO and installing again (I had to simultaneously do the same thing on a laptop since I couldn't read the prompt) - to no avail. I tried the "fresh start" option under the same menu (which opens Windows Defender). I found this post, and tried sfc /scannow in Safe Mode, as well as all variations of dism they suggested, all to no avail. Powershell, of the right-click Start menu.Right-clicking the Start button (left click is fine).It boots up and everything looks fine at first, but once I start trying to do anything, things aren't quite right. I've installed it with no issues on two machines, but on the only other two I've installed it on we have a problem with text rendering. We've started testing the 1703 build on a number of computers in our office - just a back burner kind of project.
0 kommentar(er)
