KB5011543 provides Search Highlights to Windows 10 users.

• We have some exciting news for you if you were wondering what KB5011543 brought to the table.
  
• The long-awaited Search Highlights feature has now arrived for Windows 10 users.
• However, this new feature will be sent out gradually, so don't get too excited if you don't have it yet.
• See what other changes have been made to Windows 10 as a result of this new version.

It was just 10 days ago that we discussed the introduction of Microsoft's latest Dev Channel Insider build 22572.

The Search Highlights option for the Start menu seems to be the most popular among the many modifications it provided.

Holidays, anniversaries, and other instructional points in time will be highlighted in Search Highlights both worldwide and in your region.

You'll be happy to learn that this functionality is now available to Windows 10 users as part of the company's latest optional update (KB5011543).

The Search Highlights feature will be gradually implemented.

This update brings the same features to the Release Preview as were revealed last week, but it bumps the supported Windows 10 build numbers to 19044.1620 (21H2), 19043.1620 (21H1), and 19042.1620. (20H2).

Instead of obtaining results from the web, the Search Highlights will display contacts, files, and updates inside their business, giving enterprise users a somewhat different experience.

When you click the Search bar in the taskbar, the new interface with the Search Highlights should appear. You can open the related result in your web browser by clicking on a result.

According to the official statement, it will be gradually given out to customers in phases over the coming weeks, and it could take months for it to be available to all users.

While some users may find Search Highlights useful, it's probable that those who aren't interested in site results in the first place will be irritated by the feature.

Fixes

• If you're curious about what else Microsoft has been working on, the following fix changelog can help you figure it out:
• In the Remote Desktop setup environment, a problem caused searchindexer.exe to stop responding during a dismount procedure.
• A bug in searchindexer.exe was fixed, which prevented Microsoft Outlook's offline search from retrieving recent emails.
• When changing the National Language Support (NLS) version from 6.3 to 6.2, there was an issue that might cause Windows to deactivate.
• Fixed an issue where current browsers failed to render HTML created by gpresult/h appropriately.
• During a PowerShell test for AppLocker, a "Access denied" exception was thrown for a file.
• The Group Policy Service may no longer process telemetry information for Group Policy Registry Preferences due to a bug.
• When you specify a fully qualified domain name (FQDN) and subnet criteria in a DNS Server query resolution policy, it might not perform as planned.
• A heap leak in PacRequestorEnforcement was fixed, which caused a domain controller's performance to suffer.
• A problem with the Key Distribution Center (KDC) Proxy has been resolved. For logging in to Key Trust Windows Hello for Business, the KDC Proxy is unable to receive Kerberos tickets successfully.
• In Azure Active Directory (AAD) Web Account Manager, support for Microsoft Account (MSA) Pass-through situations has been included (WAM).
• During specific password change scenarios, such as failover cluster name object (CNO) or virtual computer object (VCO) password changes, Event ID 37 was logged.
• When you employ the Silent BitLocker enabling policy, you may mistakenly include a Trusted Platform Module (TPM) protector.
• Fixed an issue where the User Account Control (UAC) window didn't list the application that was requesting elevated access correctly.
• When moving computer accounts between domains, an issue caused the Move-ADObject command to fail. "Multiple values were supplied for a property that can only have one value," says the error message.
• After a policy update, Event 4739 no longer fails to display the new values of specific characteristics.
• Fixed an issue that prevented Android users from signing in to Microsoft applications like Outlook and Teams. After rolling over token signing and decrypting certificates, resetting a user's password, or revocation of refresh tokens by an administrator, this issue arises.
• In environments with discontinuous DNS hostnames, a bug was fixed that might cause domain joining to fail.
• In high contrast black mode, the Back button of the credentials window, where you sign in, was not visible. This was fixed.
• Fixed an issue that prevents you from accessing Server Message Block (SMB) shares using an IP Address when SMB hardening is enabled.
• Fixed an issue that occurs when the Best Practices Analyzer (BPA) values for SMB have not been updated for more recent platforms.
• Fixed an issue that causes stop error 0x1E in the SMB Server (srv2.sys).
• Fixed an issue that causes a mismatch between NetBIOS and DNS Active Directory domain names when you create a cluster.
• Fixed an issue that causes the Network File System (NFS) redirector to stop working (error 0x50) when you convert a text file to a PDF.

Known Issues

• This update may remove Microsoft Edge Legacy from devices with Windows installations built from custom offline media or custom ISO image, but it will not immediately replace it with the new Microsoft Edge. When custom offline media or ISO images are built by slipstreaming this upgrade into the image without first installing the standalone servicing stack update (SSU) published March 29, 2021 or later, this issue occurs.
• Some devices are unable to install new updates after installing the June 21, 2021 (KB5003690) update, such as the July 6, 2021 (KB5004945) or subsequent updates. The error message PSFX E MATCHING BINARY MISSING will appear.
• When using Remote Desktop to connect to devices in an untrusted domain after installing this update, connections may fail to authenticate when utilizing smart card authentication. "Your credentials did not work," you might get a message. The credentials used to connect to [device name] were invalid. Please create a new account." "The login attempt failed" is highlighted in red.

Have you gotten your hands on the new Search Highlights feature? Please share your thoughts in the comments box below.