Windows 10 users get search highlights via KB5011543


by Alexandre Poloboc

news editor

With an irresistible desire to always get to the bottom of things and find out the truth, Alex has spent most of his time working as a journalist, presenter, as well as on television and radio… Read more

research highlights

Just ten days ago we were talking about the release of Microsoft’s new Insider build 22572 for the Dev Channel.

Of the many changes made, users seemed to be most excited about the Search Highlights feature for the Start menu.

Search Highlights will feature notable and interesting moments such as holidays, birthdays, and other educational moments in time, both around the world and in your area.

Now, you will surely be pleased to know that this feature has arrived to Windows 10 users via the tech giant’s latest optional update (KB5011543).

Research highlights will be rolled out gradually

This update contains the same features announced last week for the release preview, but it slightly increases the supported version number of Windows 10 to 19044.1620 (21H2), 19043.1620 (21H1) and 19042.1620 (20H2) .

Enterprise users will have a slightly different experience, as search highlights will display contacts, files, and updates from their organization, instead of fetching results from the web.

Click on the search bar in the taskbar and you should see the new interface with search highlights. You can click on a result to open the corresponding result in your web browser.

The official announcement mentions that it is gradually rolling out to users in phases over the coming weeks and it could take months for it to be available to all users.

While some people may find search highlights useful, users who don’t care about web results in the first place may be more annoyed by the feature.


Just in case you’re wondering what else Microsoft has tinkered with, you’ll get a better understanding by reading the patch’s changelog:

  • Fixed an issue that caused search indexer.EXE to stop responding during an unmount operation in the Remote Desktop configuration environment.
  • Fixed an issue that affected search indexer.EXE and prevents Microsoft Outlook offline search from returning recent emails.
  • Fixed an issue that could disable Windows when changing the National Language Support (NLS) version from 6.3 to 6.2.
  • Fixed an issue where modern browsers failed to correctly render HTML generated by result/h.
  • Fixed an issue that caused an “Access Denied” exception for a file during a PowerShell test for AppLocker.
  • Fixed an issue that could cause the Group Policy service to stop processing telemetry information for Group Policy registry preferences.
  • Fixed an issue that could prevent a DNS server query resolution policy from working as expected when specifying fully qualified domain name (FQDN) and subnet conditions.
  • Fixed a heap leak in PacRequestorEnforcement which degrades the performance of a domain controller.
  • Fixed an issue affecting the Key Distribution Center (KDC) proxy. The KDC proxy cannot successfully obtain Kerberos tickets to connect to Key Trust Windows Hello for Business.
  • Added support for Microsoft Account (MSA) transfer scenarios in Azure Active Directory (AAD) Web Account Manager (WAM).
  • Fixed an issue that logged Event ID 37 during certain password change scenarios, including Failover Cluster Name Object (CNO) or virtual machine object (VCO).
  • Fixed an issue that could unintentionally add a Trusted Platform Module (TPM) protector when using the Silent BitLocker enable policy.
  • Fixed an issue that prevented the User Account Control (UAC) dialog from correctly displaying the application requesting elevated privileges.
  • Fixed an issue that caused the Move-ADObject the command fails when you move computer accounts between domains. The error message is “Multiple values ​​were specified for an attribute that can only have one value”.
  • Fixed an issue that prevented event 4739 from displaying new values ​​for some attributes after a policy change.
  • Fixed an issue that prevented Android device users from signing in to certain Microsoft apps, such as Microsoft Outlook or Microsoft Teams. This issue occurs after replacing token signing and decrypting certificates, resetting a user’s password, or when an administrator has revoked refresh tokens.
  • Fixed an issue that could cause domain join to fail in environments using disjoint DNS hostnames.
  • Fixed an issue that prevented the Back credential window button, where you log in, to be visible in high contrast dark mode.
  • Fixed an issue that prevented you from accessing Server Message Block (SMB) shares using an IP address when SMB hardening is enabled.
  • Fixed an issue that occurred when Best Practices Analyzer (BPA) values ​​for SMB were not updated for newer platforms.
  • Fixed an issue that caused Stop Error 0x1E in SMB Server (srv2.sys).
  • Fixed an issue that caused incompatibility between NetBIOS and Active Directory DNS domain names when creating a cluster.
  • Fixed an issue that caused the Network File System (NFS) redirector to not work (error 0x50) when converting a text file to PDF.

Known issues

  • Devices with Windows installations created from custom offline media or a custom ISO image may have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue only occurs when custom offline media or ISO images are created by embedding this update in the image without first installing the Standalone Servicing Stack (SSU) update released on March 29 2021 or later.
  • After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, PSFX_E_MATCHING_BINARY_MISSING.
  • After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections may fail to authenticate when using card authentication smart. You might receive the prompt “Your credentials did not work. The credentials that were used to log in to [device name] didn’t work. Please enter new credentials. and “Connection attempt failed” in red.

Have you received your new Search Highlights feature yet? Let us know in the comment section below.


Comments are closed.