Windows 10 KB5020030 update brings significant change to Taskbar search, fixes printer issue

Microsoft has released the latest Windows 10 update (KB5020030), which includes builds 19042.2311, 19043.2311, 19044.2311, 19045.2311, 19044.2311, 19045.2311, 19045.2311, 19045.2311, 19045.2311, and 19045.2311. The update addresses several issues, including DST and Microsoft Store update failures. The Taskbar search has also been significantly updated.

The highlights of the new KB5020030 updates are listed below.

Highlights

• New! When the taskbar is at top of your screen, or when you enable small taskbar buttons mode, the search box will now appear by default on the taskbar. The search box can be used to search your computer and the internet directly from your taskbar. Click on the taskbar in your primary monitor to adjust how search displays. Find out more about search.
• It fixes persistent updates failures in the Microsoft Store.
• This addresses an issue that is affecting certain printers. The alignment of print outputs is not correct.
• It addresses an issue affecting daylight saving time in Fiji. It will cancel DST in 2022.

Here are some solutions to the problems:

Symptoms	You can work around it
This update may remove Microsoft Edge Legacy from devices with Windows installed using custom offline media or an ISO image. However, it will not replace the old Microsoft Edge. This problem is only experienced when custom offline media and ISO images are created without first installing the standalone servicing stack upgrade (SSU), released March 29, 2021. Notification Devices that are connected directly to Windows Update to get updates aren’t affected. This applies to devices that connect directly to Windows Update for Business. All devices that connect to Windows Update must always have the most current versions of the SSU as well as the latest cumulative updates (LCU) and should not be required to take additional steps.	You can avoid this problem by first slipstreaming the SSU released March 29, 2021 or earlier into the custom offline media/ISO image, before slipstreaming LCU. You will need to extract SSU from the combined SSU/LCU package for Windows 10 version 20H2 or Windows 10 version 2004. The following steps will extract the SSU. Use this command line to extract the cab (using the package for KB5000842 in an example) from the msu expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab This command line will extract the SSU from the cab that was previously extracted. expand Windows10.0-KB5000842-x64.cab /f:* The SSU Cab, as shown in the example below, will be yours. SSU-19041.903-x64.cab. This file can be slipstreamed into an offline image, and then the LCU. This issue can be avoided if the OS was installed using the affected media. You can download and deploy Microsoft Edge to your business to deploy the new Microsoft Edge.
Kerberos authentication might be affected by the Windows Servers that have been updated since November 8, 2022. This issue could impact Kerberos authentication within your environment. Here are some scenarios that might be affected by this issue: When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Not all affected events will be marked “The missing key has an ID number of 1“: While processing an AS Request for Target Service, the account didn't have a key suitable for generating Kerberos tickets (the ID of the missing key is 1). The requested etypes were: 18 The available account etypes are: 23 18 17. The proper key can be generated by changing the password or resetting it. Notification This issue is not part of the security enhancements for Netlogon or Kerberos beginning with November 2022 security updates. Even after the issue has been resolved, you will need to continue following these guidelines. This issue is not applicable to Windows devices at home that consumers use or devices that aren’t part of an on-premises domain. Azure Active Directory environments which aren’t hybrid and don’t have any on-premise Active Directory servers aren’t affected.	We are still working on a solution. A solution should be available within the next weeks. We will update this issue with additional information as soon as it becomes available.
After installing this update or any subsequent updates, Direct Access may not be available after you have lost network connectivity temporarily or switched access points. Notification This issue shouldn’t affect any other remote access solutions, such as VPN (sometimes called Remote Access Server (RAS) or Always On VPN (AOVPN). Windows devices at home for consumers and devices in companies that don’t use Direct Access to remote access the network resources of the company. They are not affected.	You can also try the following solutions. This issue is solved using Known Issue Rollback. Please be aware that the resolution may take up 24 hours to propagate automatically on consumer devices and business devices. It is possible to speed up the resolution by restarting your Windows device. This issue can be fixed for enterprise-managed devices that have received an affected update. This special Group Policy is available in Configuration of Computers -> Administrative Templates -> . See this article for more information on configuring and deploying special Group Policy. How to use Group Policy for a Known Issue Rollback Download Group Policy with Group Policy Name: Important This is what you will need Install And Configure To resolve the issue, you can use the Group Policy of your Windows version.

You can download the update by going to Settings. There you’ll find the option of downloading the latest Optional Update. Or, you can manually install it using the Update Catalog website. The official support article can be viewed here.