Even though Microsoft has released Windows 11 version 22H2, they still rolled out an optional “type C” update for Windows 11 21H2 alongside it for the people that do not want to upgrade their OS version yet. This update is KB5017383, installing which will upgrade your operating system’s build to 22000.1042.
This update does not bring any new features to the operating system but does include a plethora of fixes and improvements. Let us see what is update brings and then decide whether it is worth installing right now.
New in KB5017383 (Build 22000.1042)
The following list of improvements has been included with this release:
- Microsoft has introduced WebAuthn redirection in this flight. It lets you authenticate in apps and on websites without a password when you use Remote Desktop. Then, you can use Windows Hello or security devices, such as Fast Identity Online 2.0 (FIDO2) keys.
- More dynamic Widgets have been added to the taskbar with notification badging. When you open the Widgets board, a banner appears at the top of the board. It provides more information about what triggered the notification badge.
- An issue that requires you to reinstall an app if the Microsoft Store has not signed that app is now fixed.
- An issue that stops codecs from being updated from the Microsoft Store is fixed.
- A race condition in framework autorepair registration has been fixed. This issue occurs because a registration key is missing.
- An issue that affects the Network Policy Server Management (NPSM) service has been addressed. This issue causes major delays when you sign out.
- An issue that affects the Windows Search service has been fixed. Indexing progress is slow when you use the service.
- An issue that affects cached credentials for security keys and FIDO2 authentications has been fixed. On hybrid domain-joined devices, the system removes these cached credentials.
- An issue that affects a network’s static IP has been taken care of. The issue causes the configuration of the static IP to be inconsistent. Because of this, NetworkAdapterConfiguration() fails sporadically.
- A rare stop error that happens after you change the display mode and more than one display are in use has been fixed.
- An issue that affects rendering in Desktop Window Manager (DWM) has been addressed. This issue might cause your device to stop responding in a virtual machine setting when you use certain video graphics drivers.
- An issue that affects graphics drivers that use d3d9on12.dll is addressed.
- An issue that forces the IE mode tabs in a session to reload has been fixed.
- An issue that successfully opens a browser window in IE mode to display a PDF file is addressed.
- An issue that affects window.open in IE mode is now fixed.
- Microsoft introduced a Group Policy that enables and disables Microsoft HTML Application (MSHTA) files.
- An issue that affects the Microsoft Japanese input method editor (IME) has been addressed. Text reconversion fails when you use some third-party virtual desktops.
- An issue that occurs when the input queue overflows is now fixed. This might cause an application to stop responding.
- An issue that might cause a black screen to appear on your display has been addressed. This might occur when you use a pen to turn on high dynamic range (HDR).
- An issue that affects the App-V client service is addressed. The service leaks memory when you delete App-V registry nodes.
- An issue that might change the default printer if the printer is a network printer is fixed.
- An issue that affects WDAC policies has been addressed. If you enable SecureLaunch on a device, WDAC policies will not apply to that device.
- An issue that affects Windows Defender Application Control (WDAC) path rules is fixed. This issue stops .msi and PowerShell scripts from running.
- An issue that might bypass MSHTML and ActiveX rules for WDAC is fixed.
- An issue that causes WDAC to log 3091 and 3092 events in audit mode is fixed.
- An issue that affects Windows Defender Application Control (WDAC) has been taken care of. It stops WDAC from logging .NET Dynamic Code trust verification failures.
- An issue that occurs when a WDAC policy fails to load is fixed. The system logs that failure as an error, but the system should log the failure as a warning.
- An issue that affects Code Integrity logging is fixed. It logs issues as errors instead of warnings. Because of this, automatic repair is triggered.
- An issue that affects the touch keyboard has been addressed. The touch keyboard immediately closes when you tap to switch apps.
- An issue that causes LogonUI.exe to stop working is fixed. Because of this, you cannot dismiss the lock screen to view the credentials screen.
- An issue that affects the FindNextFileNameW() to leak memory is now addressed.
- An issue that affects robocopy is fixed. Robocopy fails to set a file to the right modified time when using the /IS.
- An issue that affects cldflt.sys has been fixed. A stop error occurs when it is used with Microsoft OneDrive.
- An issue that affects the LanmanWorkstation service has been addressed. When you mount a network drive, the service leaks memory.
- An issue that affects the Get-SmbServerNetworkInterface has been fixed. It only retrieves a subset of the available network interfaces.
- An issue that affects the Get-SmbServerConfiguration is fixed. It only allows you to run it if you are an administrator.
- An issue that affects Roaming User Profiles is fixed. After you sign in or sign out, some of your settings are not restored.
- A known issue that affects XML Paper Specification (XPS) viewers has been addressed. This might stop you from opening XPS files in some non-English languages. These include some Japanese and Chinese character encodings. This issue affects XPS and Open XPS (OXPS) files.
- An issue that affects daylight saving time in Chile has been addressed. This issue might affect the time and dates used for meetings, apps, tasks, services, transactions, and more.
- An issue that affects the Hyperlink.Click event has been fixed. This affects apps, like Phone Link and Feedback Hub, which embed hyperlinks in TextBlocks and RichTextBlocks.
With these improvements, Microsoft has not disclosed any known issues and claims that there are none:
Microsoft is not currently aware of any issues with this update.Microsoft
Download and Install KB5017383
This update is currently only available through Windows Update. Perform the following steps to download and install KB5017383 on your Windows 11 computer:
Navigate to the following:
Settings app >> Windows Update
Here, click Check for updates.
You will now see the following update available:
2022-09 Cumulative Update for Windows 11 for x64-based Systems (KB5017383) is available.
Click Download and install below it.
When it is installed, click Restart Now to reboot your PC and finalize the installation.
When the computer reboots, the update will have been successfully installed. To confirm this, check the updated build number by typing in winver in the Run Command box.
Rollback/Remove Windows 11 Cumulative Update
If you do not wish to keep the installed update for some reason, you can always roll back to the previous build of the OS. However, this can only be performed within the next 10 days after installing the new update.
To roll back after 10 days, you will need to apply this trick.
Cleanup After Installing Windows Update
If you want to save space after installing Windows updates, you can run the following commands one after the other in Command Prompt with administrative privileges:
dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
dism.exe /Online /Cleanup-Image /StartComponentCleanup
Since the new feature update for Windows 11 has already been launched, we believe that next month’s Patch Tuesday update will include these fixes and improvements for Windows 11 version 22H2 as well.
Having the latest Windows 11 OS and these fixes implemented will give you the most stable Microsoft operating system yet. Moreover, since there are no discovered known issues, it is safe to install KB5017383 even now.