Have you ever used the "Search" feature in the Windows 11 Start menu?
When you enter text in the search box, apps, settings, etc. on your PC that match the text you entered will be displayed, and you can launch them by clicking them.
In addition, "Web Search" displays the entered text and "- Show more search results," and clicking it will open a browser and display the search results.
Once you have searched for a character, it will remain in your search history, and when you place the cursor over the character, an x mark will appear on the right side, and you can delete the history by clicking it.
However, there is a bug in the web search history, and characters displayed in the history may not be deleted within a certain period of time even if you click the × mark.
Also, if there are multiple histories, when you try to delete one of them, the order may change and you may not be able to delete it.
Even if you are able to delete it, the last one in the history may not be deleted no matter how many times you click the X mark.
When this happens, you cannot delete it even by clicking Settings > Privacy & Security > Search Permissions > "Clear device search history."
Another thing that can happen is that after you've cleared your entire history, you search for something again, and when you open Search again, your previous search history will appear.
Also, even though I'd deleted everything, my previous search history would still appear when I opened Search.
I don't know when this bug started occurring.
I tested this bug in my environment and confirmed that it could be removed after a few minutes.
*OS: Windows 11 Home 23H2 64-bit (22631.4037) KB5041585 released on August 13, 2024 has been installed.
However, as mentioned earlier, even if you delete everything, your previous search history may still appear when you open Search.
We have confirmed that whether the Windows Search service is enabled or disabled has no effect.
No information about this bug has been released by Microsoft, and no information was found online.
I think the cause is probably the recent update KB5040527 (July 25, 2024) or KB5041585 (August 13, 2024).
Comment: