Windows 11 22621.754 KB5018496 update to enhance backup experience

KB5018496 Windows 11 22621.754 22H2 changes, bug fixes, improvements, and direct download links.

Windows 11 22621.754 KB5018496

Only after 2 days, a new update is again available in the release preview ring of Windows 11 insider (but for 22H2). This release is  KB5018496 which brings some important improvements and a good enough number of bug fixes. The cumulative update changes the version to Windows 11 22H2 22621.754.

Full name of this release is “2022-10 Cumulative Update for Windows 11 for x64-based Systems (KB5018496)” where x64 can be ARM64 when the system is compatible. Let’s see what is new in this 22H2 update –

KB5018496 Windows 11 22621.754 22H2 features, changes, and bug fixes

Here is the changelog –

New Improvements

  1. KB5018496 LCU added a new consent form for those who enrolled in Windows Hello Fingerprint and Face. You have new options for your biometric data. You can keep saving your biometric data or launch Settings to delete the data if you haven’t used your fingerprint or face for authentication in more than 365 days. You have these choices too if you upgraded to Windows 11 and have not yet come across the new Hello Learn More Privacy text.
  2. The experts in the team added improvements to Microsoft Account experience in Settings. For example, you can handle your One Drive subscription and related storage alerts.
  3. Windows 11 Build 22621.754 RP Channel enhanced the search visual treatments on taskbar in order to improve discoverability. This is rolled out to a little number of audience initially and will be deployed more broadly in the months that follow. Because of this rollout some devices might notice dissimilar visual treatments as we gather feedback. To learn more regarding seeing these changes, read Search for anything, anywhere.
  4. The new version improved the backup experience when using your Microsoft Account. Some devices might come across visual treatments for this enhancement. This is rolled out to a little number of audience initially and deployed more broadly in the months that follow.
  5. The LCU in Release Preview channel added Task Manager to the right-click menu of the taskbar. You will receive this feature in the forthcoming weeks.

Changes and improvements

  1. Experts in the RP channel team enabled ms-appinstaller Uniform Resource Identifier aka URI to work for DesktopAppInstaller.
  2. They will not start daylight saving time means DST in Jordan at the end of October 2022.
  3. CU KB5018496 fixed a problem with Distributed Component Object Model (DCOM) authentication hardening. The cumulative update of RP channel will automatically increase the authentication level for entire non-anonymous activation requests from DCOM clients to “RPC_C_AUTHN_LEVEL_PKT_INTEGRITY”. This problem happens if the authentication level is lower than Packet Integrity.
  4. The experts have fixed a problem with Windows Search service. When you use this service, the Indexing progress is slow.
  5. They solved a problem with cached credentials for security keys and Fast Identity Online 2.0 (FIDO2) authentications in Windows 11 Build 22621.754. The system deletes these “cached credentials” on “hybrid domain-joined devices”.
  6. The new rollout fixed an issue that might affect some types  TLS and SSL. These connections might have handshake failure. For developers, the affected connections are likely to send multiple frames followed by a partial frame with a size of fewer than 5 bytes within a single input buffer. If the connection fails, your app will receive an error, “SEC_E_ILLEGAL_MESSAGE”.
  7. The experts fixed a problem with Microsoft Azure Active Directory aka AAD Application Proxy connector. This connector is unable to get back a Kerberos ticket on behalf of the user. The error message thrown is – The handle specified is invalid (0x80090301).
  8. KB5018496 for 22H2 fixed an issue that affects certificate mapping. When the mapping fails, lsass.exe might stop working in schannel.dll.
  9. The new LCU fixed a problem with Microsoft Edge when it is in IE Mode. Titles of pop-up windows and tabs are not correct.
  10. The rollout fixed a problem with Microsoft Edge IE mode. It prevents you from opening web pages. This happens when you turn on Windows Defender Application Guard means WDAG and you do not configure Network Isolation policies.
  11. Experts solved a problem with title bars that occurs when you use third-party tools to customize them. Due to this issue, the title bars didn’t render. This LCU makes sure that title bars render; although, the version cannot guarantee all text customizations will remain the same as before.
  12. KB5018496 fixed an issue that might cause horizontal and vertical line artifacts to show up on the screen.
  13. The CU fixed a problem with input method editors aka IME from third parties and the tech giant itself. As you close IME window they stop working. This happens if the IME uses Text Services Framework 1.0 or TSF 1.0.
  14.  Windows 11 22H2 22621.754 RP channel update solved a problem that might fail to sync the audio when you record gameplay with the help of Xbox Game Bar.
  15. The new update KB5018496 updated DriverSiPolicy.p7b for the vulnerable driver blocklist of Windows kernel. This patch comprises drivers that are vulnerable to Bring Your Own Vulnerable Driver aka BYOVD attacks.
  16. The LCU extended OEM control of Hypervisor-protected Code Integrity aka HVCI enforcement for targeted hardware configurations.
  17. They solved a problem with File Explorer. Its dependency is less when you browse for OneDrive folders.
  18. This cumulative update solved a problem with the button style BS_PUSHLIKE. Buttons that have this style are burdensome to detect against a dark background.
  19. New version solved a problem that stops credential User Interface from showing in IE mode when you use Edge browser.
  20. Windows 11 22621.754 fixed a problem with Server Manager. It might reset the incorrect disk when multiple disks have the same UniqueId.
  21. The new version addresses an issue that affects the CopyFile function. KB5018496 returns “ERROR_INVALID_HANDLE” in place of “ERROR_FILE_NOT_FOUND” when it is called with an invalid source file.
  22. They solved a problem with the Start menu. It stops functioning when you use keyboard commands to move pinned items to a folder at the end of a list.

Known issues

Applies to Symptom Workaround
IT admins On Windows 11 v22H2, Provisioning packages might not work as expected, as a result, Windows might not be fully configured, and the OOBE might not finish or might restart in the middle. The packages are in for form of .PPKG files which are used to help configure devices for use on school or business networks. This problem impacts the Provisioning packages during initial setup.

Important: This issue will not affect during the process of Provisioning when using Windows Autopilot.

Similarly, this problem does not affect the consumers in their small offices or homes.

Provisioning a device before upgrading to Windows 11 v22H2 will prevent the problem from occurring.

The Windows team’s experts are currently investigating and will provide an update in an upcoming release.

IT admins Copying Multi GB File in Windows 11 22H2 might consume more time than expected. This problem most likely to occur when copying from a network share. However, Server Message Block but local file copy might also be affected. This issue will not affect the small offices and homes consumers. In order to mitigate this, file copy tools are useful that don’t use cache manager (buffered I/O). The following commands can do this:

robocopy \\someserver\someshare c:\somefolder somefile.img /J


xcopy \\someserver\someshare c:\somefolder /J

The team is working on a resolution and will offer an update in an upcoming release.

Windows 11 22621.754 KB5018496 download links –

  2. x64.psf
  5. ARM64.psf

Sources –

Release note

Official download link

That’s all!!

Sharing is caring    Share Whatsapp

Topics:  Windows Insider
About Sunita
Love to play with Windows 11 and 10. Suggestion - Going for Registry change or system files edit then remember to take a backup or create a restore point before Starting.