Every time it starts feeling a bit quiet after Microsoft releases a cumulative update, something random breaks. Like every month, Microsoft rolled out its Patch Tuesday updates for Windows 10 and Windows 11 on the second Tuesday of July, just a couple of days ago.

And while Windows 11 users got a few exciting new additions, Windows 10 users only received a handful of bug fixes. Of course, it simply wouldn't be a Microsoft update if something didn't break. This time around, the victim was something relatively small in Windows 10, but something you likely use on a daily basis.

Patch KB5062554 breaks the emoji search panel on Windows 10

As first spotted by Neowin, several Windows 10 users have been seen complaining about the Patch Tuesday update KB5062554, which breaks the emoji search panel. For instance, the user of this post on the r/Windows10 subreddit mentions that though the emoji picker still "mostly works," the functionality to search for an emoji by typing is completely broken.

Every time a user attempts to search for an emoji, they're greeted with a "We couldn't find this one." message. They provided an example image too (which we've attached below), where they typed "smile" and got the same error.

The author of the Reddit post confirms that bringing up the emoji picker panel by hitting the Win + . keys still works, and clicking an emoji pastes it like intended. They also mentioned that this issue only began after they installed the July 2025 cumulative update. To ensure it was the update causing the issue, they reverted to a restore point from the "previous evening," which managed to fix the bug. Then, they decided to install the KB5062554 patch again, which broke the emoji search panel again.

All the comments under the post are mostly other Windows 10 users confirming the issue and mentioning how reverting to a previous restore point fixes the problem. Similarly, there's another post in the r/WindowsHelp subreddit mentioning the same issue, and also a thread on Microsoft's own community forum.

Interestingly, Microsoft is yet to acknowledge the bug. Given that Windows 10's end-of-life date isn't too far off now, it's also a question of whether Microsoft will even bother addressing small bugs like this, or if they'll quietly let them slide as the OS nears retirement. Nonetheless, the only fix there seems to be for now is to roll back the update using a restore point.