When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

Microsoft releases Windows 10 21H2 Build 19044.1618 (KB5011543) with new Search highlights

Build 190441618 screenshots

Microsoft has announced the release of Windows 10 21H2 Build 19044.1618 (KB5011543) to the Release Preview Channel for Insiders on Windows 10.

With the latest update, the company is adding search highlights to Windows 10. This feature will allow the taskbar search box and search home to periodically update with content that will allow you to "discover more, be connected, and stay productive" and will include illustrations as well.

Build 190441618 screenshots

The latest update includes the following improvements and fixes:

  • New! We provided the ability to change the color of toast buttons to identify success and critical scenarios more easily for apps that send notifications using Windows notifications in the OS. This feature also makes notifications more visually compact.
  • New! We added a new policy that expands an app’s top three notifications by default in the Action Center for apps that send notifications using Windows notifications in the OS. This feature displays multiple notifications that you can interact with simultaneously.
  • We fixed an issue that causes searchindexer.exe to stop responding during a dismount operation in the Remote Desktop setup environment.
  • We fixed an issue that affects searchindexer.exe and prevents Microsoft Outlook’s offline search from returning recent emails.
  • We fixed an issue that might deactivate Windows when you change the National Language Support (NLS) version from 6.3 to 6.2.
  • We fixed an issue in which modern browsers fail to correctly render HTML that is generated by gpresult/h.
  • We fixed an issue that causes an “Access denied” exception for a file during a PowerShell test for AppLocker.
  • We fixed an issue that might cause the Group Policy Service to stop processing telemetry information for Group Policy Registry Preferences.
  • We fixed an issue that might prevent a DNS Server query resolution policy from working as expected when you specify a fully qualified domain name (FQDN) and subnet conditions.
  • We fixed a heap leak in PacRequestorEnforcement that degrades the performance of a domain controller.
  • We fixed an issue that affects the Key Distribution Center (KDC) Proxy. The KDC Proxy cannot properly obtain Kerberos tickets for signing in to Key Trust Windows Hello for Business.
  • We added support for Microsoft Account (MSA) Pass-through scenarios in Azure Active Directory (AAD) Web Account Manager (WAM).
  • We fixed an issue that logs Event ID 37 during certain password change scenarios, including failover cluster name object (CNO) or virtual computer object (VCO) password changes.
  • We fixed an issue that might unintentionally add a Trusted Platform Module (TPM) protector when you use the Silent BitLocker enablement policy.
  • We fixed an issue that prevents the User Account Control (UAC) dialog from correctly showing the application that is requesting elevated privileges.
  • We fixed an issue that causes the Move-ADObject command to fail when you move computer accounts across domains. The error message is, “Multiple values were specified for an attribute that can have only one value”.
  • We fixed an issue that prevents Event 4739 from displaying the new values of certain attributes after a policy change.
  • We fixed an issue that prevents Android device users from signing in to some Microsoft applications, such as Microsoft Outlook or Microsoft Teams. This issue occurs after rolling over token signing and decrypting certificates, resetting a user’s password, or when an administrator has revoked refresh tokens.
  • We fixed an issue that might cause domain joining to fail in environments that use disjoint DNS hostnames.
  • We fixed an issue that prevents the Back button of the credentials window, where you sign in, from being visible in high contrast black mode.
  • We fixed an issue that prevents you from accessing Server Message Block (SMB) shares using an IP Address when SMB hardening is enabled.
  • We fixed an issue that occurs when the Best Practices Analyzer (BPA) values for SMB have not been updated for more recent platforms.
  • We fixed an issue that causes stop error 0x1E in the SMB Server (srv2.sys).
  • We fixed an issue that causes a mismatch between NetBIOS and DNS Active Directory domain names when you create a cluster.
  • We 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.

To find the original press release, head over to the dedicated webpage here.

Report a problem with article
The EU flag next to a bitcoin
Next Article

EU Parliament committee decides not to ban proof-of-work cryptos

Previous Article

Get a lifetime subscription to eLearnOffice Microsoft Office for only $29

Join the conversation!

Login or Sign Up to read and post a comment.

4 Comments - Add comment