Release of Windows 11 KB5017389 (22H2) – a rundown of recent developments and existing problems.
Rolling out to all users now is KB5017389, the first optional preview update for Windows 11 that brings with it several changes and improvements in preparation for the release of 22H2. While Microsoft has distributed the offline installer for Windows 11 KB5017389 through WU, it has also made it available for direct download from the Update Catalog.
The KB5017389 update is the first optional patch for Windows 11 22H2 Update, and it includes numerous problem fixes. Only Windows 11 version 22H2 (not Windows 11 version 21H2 or the original Windows 11) is compatible with this update.
Windows 11 Build 22621.608 is the result of the update labeled “2022-09 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5017389)”. To get it, go to Windows Update and look for the download link next to the optional updates.
Once you have made your modifications, you must restart the system. A system reboot will be required after installing this significant preview update. It could take more than five minutes to complete the installation, but only one reboot is needed to fully apply all of the modifications.
The October 2022 cycle of Patch Tuesdays is when the aforementioned set of updates will first become available to the general public.
Windows 11 KB5017389 Downloads
Follow the above link to access the Microsoft Update Catalog, where you can download previous versions of Windows Update. The.msu files can be installed by clicking the ‘Download’ button next to the OS version currently installed on your machine and then running the files.
Changes in Windows 11 KB5017389 (Version 22621.608)
In Windows 11 Version 22621.608, a new feature known as “notification badging” allows for more dynamic Widget material to be displayed on the taskbar. Users will not forget that they have unread notifications in their widgets thanks to the notification badging.
To find out more about the update or piece of news that prompted the notification badge, click on it. This will take you to a banner at the top of the board.
A problem where Microsoft Store updates would suddenly stop downloading has also been fixed in Windows 11 Build 22621.608. The issue where switching to IE mode would force all open tabs to reload during a session was also fixed. Apps that were not signed by the Microsoft Store no longer had to be installed, according to a patch released by Microsoft.
The list of improvements and bug fixes is as follows:
- The problem that caused a second print queue to appear has been resolved by Microsoft. If this occurs, the printer will stop working since the original print queue will stop responding.
- Windows Defender Application Control now prevents users from bypassing MSHTML and ActiveX rules.
- An issue affecting Miracast’s user interface has been resolved.
- The issue where LogonUI.exe would stop responding, preventing users from dismissing the lock screen to access the credentials screen, has been resolved.
- Resolved an issue wherein making calls on both SIM cards was unsuccessful. For instance, the Dual SIM feature will not function if a call is placed from the device without first selecting a SIM card.
- Memory leak correction for the FindNextFileNameW() method.
- The problem that was affecting robocopy has been fixed.
- OneDrive no longer crashes with a Blue Screen of Death error.
- An issue that was affecting Roaming User Profiles has been fixed. If this occurs, not all of your preferences will be restored.
- Mounting a network drive no longer causes a memory leak.
Is the first optional update for Windows 11 22H2 free of any known bugs, as far as Microsoft is aware? The organization claims it has not received any reports detailing severe OS issues at this time.
In the current version of the release notes, Microsoft states that they are unaware of any problems caused by the update.
Unfortunately, there have been instances of unsuccessful installations. For instance, one user reported that Windows Update lists KB5017389 “together with the 2022-09 cumulative version for.NET,” but that installing either update results in failure.
I installed version.601 and was anticipating the version.607 through Windows Update; but, version.607 was never made available to me. To ensure the integrity of the repository, I used DISM. There’s absolutely no sign of wrongdoing here. In addition, an sfc /scannow that I conducted revealed no corruption. One of the affected customers said on the Feedback Hub, “I tried the indicated reset script again.”
You can try running the .msu offline installer you got from the Microsoft Update Catalog if the installation doesn’t go smoothly.