A few days ago, the Windows team released the preview as part of the Windows Insider program. Now KB5022360 is already starting for all users who have Windows 11 version 2022 installed.
So if you want, you can get the update now and benefit from the changes before patch day. This non-security update includes quality improvements. It’s not a real feature update. There is only one innovation for the previews of the .NET Framework updates. The change now reflects future optional .NET Framework preview updates on the Settings > Windows Update > Advanced Options > Optional Updates page. More on this at the end of this post in the release notes.
Bug fixes and improvements
Microsoft also provides a number of important bug fixes. Among other things, a problem has been fixed that could lead to login errors. In addition, the Windows team addresses problems with Edge WebView2. The optional update KB5022360 is a so-called preview update or optional update. Microsoft used to group these updates under the term C updates. The new version has the build number 22621.1194. Unlike the Patch Day updates, the optional updates will only be released gradually. It is therefore possible that you will not be offered it via Windows Update after the start of publication. Then a restart often helps to be able to obtain the new version via Windows Update.
highlights
This non-security update includes quality improvements. If you install this KB:
- New! We’ve changed the experience with Preview .NET Framework updates. After you install this update, all future (optional) .NET Framework preview updates will appear on the Settings > Windows Update > Advanced Options > Optional Updates page. On this page you can control which optional updates you want to install.
- We fixed an issue affecting searchindexer.exe. It randomly prevented you from logging in or out.
- Fixed an issue that prevented searching for a file based on file content.
- We fixed an issue with resource contention between two or more threads (known as deadlock). This deadlock affected COM+ applications.
- We fixed an issue affecting conhost.exe. She stopped responding.
- We fixed an issue that may have affected the Domain Name System (DNS) suffix search list. The configuration may have been missing the parent domain.
- We fixed an issue that might occur when the Input Method Editor (IME) was active. Applications may have stopped responding when using the mouse and keyboard at the same time.
- We fixed an issue that may have affected FindWindow() or FindWindowEx(). You may have returned the wrong window handle.
- We fixed an issue that could occur when converting or reconverting Japanese Kanji using an MBCS (Multibyte Character Set) application. The cursor might move to the wrong place when you typed.
- We fixed an issue that may have affected applications that used Microsoft Edge WebView2 to display content. Applications using WebView2 included Microsoft Office and the Widgets app. The content may have appeared blank or grayed out.
- We fixed an issue causing certain systems with Firmware Trusted Platform Modules. (TPM). This issue prevented you from using AutoPilot to set up these systems.
- We fixed an issue affecting image files found by searching the taskbar. This problem prevented you from opening these images.
- We fixed an issue affecting mstsc.exe. It stopped responding while connecting to a RemoteApp and a desktop connection.
- We fixed an issue that caused Windows Server 2022 domain controllers (DC) to stop responding. This problem occurred when they were processing Lightweight Directory Access Protocol (LDAP) requests.
- We fixed an issue affecting the Resilient File System (ReFS) MSba tag. The problem caused a leak in the non-paged pool.
- We fixed an issue affecting the ReFS. The issue was causing high non-paged pool usage that was exhausting system memory.
- We fixed an issue affecting devices subject to Microsoft Exploit Protection Export Address Filtering (EAF). Some applications stopped responding or could no longer be opened. These included Microsoft Office and Adobe Reader.
- We fixed an issue affecting some game controllers. When the game controller was connected to the computer, the computer might not go to sleep.
Thank you for submitting this news tip!
Windows 11 22H2: The most exciting new features at a glance
See also:
